Files
FreeCADWasmDev/docs/current/web-commanddoc-remaining-boundaries.md
wangdequan 9a7c4f0335 Save FreeCAD Web workspace sources and user validation evidence
IFC native binding remains incomplete; preserve accurate test results.
2026-09-15 22:01:58 +08:00

37 lines
1.9 KiB
Markdown

# Web CommandDoc Remaining Boundaries
Batch: `4f782173ccfb11e46ceb2750`
Removed Recompute, Std_Alignment, Std_Copy, and Std_Cut from the
PartBoxProbe tier-1 metadata-only command branch. That branch returns an
operation label without executing these document operations. It must not
serve as their native implementation.
This batch remains incomplete. No builds, tests, business acceptance,
browser validation, benchmarks, or historical reconciliation were run.
## Next Source Anchors
- `WebViewCommands.h:46`: `core_recompute_command` already calls the requested
document's native recompute with cycle checking and optional transactions.
Inspect its standard dispatch at line 234 and its document-view bridge
before changing registration. The legacy `WebRuntimeProbe.cpp:97`
documentRecompute branch still recomputes a fixed WebDocument.
- `WebViewCommands.h:369`: Copy and Cut explicitly reject execution pending
a view clipboard handler that preserves native object data. Connect native
serialization and clipboard ownership before allowing Cut to delete data.
Desktop delegation is at `CommandDoc.cpp:1189` and `CommandDoc.cpp:1217`.
- `WebViewCommands.h:373`: Alignment explicitly rejects execution pending
the manual alignment task and native placement application. Desktop task
setup is at `CommandDoc.cpp:1841`; follow its existing native alignment
implementation rather than substituting a fixed placement.
- `web/src/web-desktop-adapter.ts:122`: the existing Std workflow branch
routes to the document-view endpoint; the recompute branch follows at
line 134. Inspect their imported handlers and the native endpoint in
`NativeDocumentView.h` before adding another route.
The four supplemental source windows permitted for this turn were used.
Remaining source ownership and UI connections are unresolved, not absent.
The outer pipeline owns incremental build, sync, and route receipts;
receipts must not mark these remaining business boundaries complete.