1.8 KiB
Section Cut Container Continuation
Latest update: 2026-09-17 14:41 UTC, batch fb092720014c5359c9d7ef9b.
See part-section-cut-recovery-checkpoint.md, 14:41 entry. Generated links now
use native ancestor placement expressions: translation and nested rotation
recompute without Sources refresh, including after FCStd reopen. Six focused
native/browser groups completed in 24.391 s, with history, isolation and
desktop/mobile orbit/pixel proof. Evidence:
business-evidence/f1d7d44e1f891399048bb542-20260917T144015540570.json.
Overall command remains incomplete. Appearance/transparency, reparenting,
finite cutter extents and unexpected failure history remain outstanding.
The earlier refresh-only boundary below is superseded for the tested movements.
Updated 2026-09-17 14:20 UTC. The active checkpoint is
part-section-cut-recovery-checkpoint.md, latest 14:20 UTC entry.
This increment fixes nested App::Part placement and origin-helper collection
in PartSectionCutDocument.h. Four focused browser/native groups completed
in 17.425 s; evidence:
business-evidence/f1d7d44e1f891399048bb542-20260917T141928273081.json.
The complete Section Cut requirement remains unfinished.
It also resolves the repeated missing-owner source-packet rejection, without
changing source-reader permissions or budget: prepare_module_implementation_packet.py
now includes the Section Cut document owner and explicit current case re-exports.
Thirteen focused tests pass. The broader existing delivery-planning suite still
has three historical phase-order/handoff failures, outside this change.
Next functional work remains automatic face-color mapping and independent cut-face/fragment transparency. Container movement requires Sources refresh; automatic ancestor-change propagation remains open. Preserve all historical cases/evidence and continue with relevant new behavior only.