25 lines
1.4 KiB
Markdown
25 lines
1.4 KiB
Markdown
# Dependency Graph Export
|
|
|
|
2026-09-16. `Web:desktop:Std_ExportDependencyGraph` passed its first formal
|
|
acceptance on the production preview at port 5181. Nineteen scenario records
|
|
completed in 9.126 seconds. Evidence:
|
|
`business-evidence/1791423fb877bddabae2d92a-20260916T102657679724.json`.
|
|
|
|
The existing native Graphviz export and download service now have a mounted
|
|
task with document, document source, filename, result and error controls.
|
|
The form supports both existing native Part owners, uses the document name for
|
|
the default .gv filename, and preserves custom Unicode filenames. Native
|
|
filename validation rejects path separators and wrong extensions.
|
|
|
|
Cases download real files through Chromium and compare every byte with the
|
|
native document's DependencyGraph. They cover both owners, changed links,
|
|
FCStd save/close/reopen, recovery after invalid inputs, unchanged BREP hashes,
|
|
labels, object state and undo/redo counters. Downloaded .gv artifacts and
|
|
desktop/mobile screenshots have retained hashes. One WASM is loaded per owner
|
|
for all its operations. Native generation is reused, not reimplemented in JS.
|
|
|
|
TypeScript and the production build passed. Only this new requirement was
|
|
formally executed. Existing requirement revalidation remains paused; stale
|
|
evidence is retained without promotion to current proof. Graph rendering and
|
|
other export formats remain separate requirements. All 1508 remain in scope.
|