[noderaven]

Release 1.6.3: review carry-over. What earlier agents decided or found now reaches the agents who come after them, once and correctly.

Built directly (no parallel-lanes run). Design: revision 3, checked by a builder review and an adversarial claim check; the build then had a whole-branch code review and an adversarial end-to-end review on copies of three real run archives, with one fix pass.

Changes

• Ledger: ruling roles, ids, scope, overrides and permitted files; ledger rulings, carry-launch, minors, owners, undeclared, write-owners; status gains minors and overrides, and undeclared becomes owner-annotated.
• carry-launch records a launch's pre-flight rulings and the task minors still open after it, from its Workflow result file, once per launch and in launch order.
• Engine: every task agent starts with the rulings in force; the adjudicator, final agents and a relaunch's pre-flight read them; only the security lens owns the task-minor checklist; carried minors reach it on a resume (final.carried_minors_open); a relaunch with nothing left to run skips pre-flight; run rulings are numbered PF-n.
• Setup writes an owner map; reviewers see who owns each file changed outside a task's Files list; implementers need a ruling before touching another lane's or a later task's file; failures outside a task are recorded as run-wide observed rulings.
• Docs: reference.md "Carry-over", SKILL.md Launch step 5 and Resume step 2, README.

Testing

• Full suite on Windows: 1497 tests, 1481 pass, 16 skipped, 0 fail.
• Python 3.8.20 (uv): full suite 1487 tests, 0 fail before the fix pass; the Python-backed files again after it, 176 tests, 0 fail.
• carry-launch exercised on copies of the sc1, f1a and hx1 archives.