[SaiFlyBy]

Same-repository reconciliation now has an explicit lineage-preservation path, including independent candidate-bound source/rights reviews and protected committed lineage, harvest, policy and validator objects. This completes the original #7 scope on accepted #9 main.

New missions can compose lineage with target coordination using sealed execution-state v20 and an explicit effective-schema composition contract; standalone v18/v19 and existing frozen missions remain unchanged. Settlement reconciliation, reports and handoffs retain the exact lineage-review ref/hash plus generation, scope and fence custody. A renewed review keeps its original policy/profile pin and names the descendant publication base examined for the candidate and no-new-obligations finding. Git proves policy-base → reviewed-base → candidate and unchanged protected objects at all three commits. Direct publication after main advances before settlement remains supported. Both publication success paths recheck lineage and writer custody after forge verification.

The first target profile remains SaiFlyBy/flybymaestro and accepted main. Review records do not authenticate reviewers, and the four-file proof does not establish target-validator success or its other inputs. External contributions retain normal lineage materialization.

Candidate: 0da5e23; tree 5c19e84a7c837ca6046d98d638d8ae87ea1c5ef4; accepted base 90ab422. Original source d707c4d is retained in merge history.

Validation:

• Final clean-source combined lifecycle passed locally: main advances before settlement, direct publication eligibility, subsequent handoff retaining provenance, renewed successor review, explicit fence/release, final qualification and CLOSED.
• Final clean-source effective-schema consumer/adoption regression passed. Focused Git/review, locking, malformed-input and publication tests passed; the older local full bridge run retains two Windows Git fixture failures and is not counted as a passing run.
• Exact-candidate hosted bridge passed Linux and Windows: https://github.com/SaiFlyBy/worktrunk/actions/runs/42249521836 .
• Normal pre-merge lint, feature checks, lockfile/doctest/rustdoc and full Linux/Windows suites passed: https://github.com/SaiFlyBy/worktrunk/actions/runs/42249521694 . Coverage and release planning passed.
• Independent final review reported no remaining material issue in this scope.
• macOS Rust test/advisory jobs never acquired a hosted runner and were cancelled by GitHub capacity constraints. Only the normal macOS test job is being retried; no macOS pass is claimed. The repository has no branch protection/ruleset requiring it, and the requested feature acceptance platforms reuse the established Linux/Windows boundary. All configured tests remain present.

Dependency-aware delivery and the distinct reservation bindings are following coherent scopes; merging this PR does not complete those requirements.