Parent handoff milestone: #721
Related existing convergence: #666 #682
Related release/environment: #513 #526 #637–#646
Problem
#666 correctly governs branch convergence before the production trader subsystem lands, but the repository's final responsibility boundary needs a terminal repository-wide convergence gate after all admitted calendar, forecast, trader, feature, reproducibility and training-substrate work has landed.
At the August 20, 2026 terminal editorial audit the live branches are:
main;dev;codex/492-economic-calendar-vintages;dependabot/github_actions/github-actions-72d335de65;dependabot/pip/python-packaging-be9169ee7a.
dev and main are materially divergent; the calendar branch is stale and semantically superseded in part; the dependency branches alter release/environment inputs. A clean ML handoff cannot be certified while scientifically relevant code, tests, schemas, documentation or dependency/environment changes remain ambiguously stranded on side branches.
Outcome
Before #721 can close, produce one reviewed branch-disposition artifact and one exact certified handoff tree. Every live branch and any branch created during the remaining roadmap receives a terminal disposition:
- merged/rebased and included;
- selectively salvaged with exact commit/file lineage;
- superseded by named issue/implementation;
- dependency update intentionally rejected/deferred with rationale;
- content-neutral/obsolete and safe to delete after retention policy.
Required audit
For each branch compare against the intended release/handoff base and classify every changed file by subsystem and scientific relevance. Explicitly inspect:
- source/runtime code;
- schemas/contracts;
- tests/fixtures/reference kernels;
- docs/nonclaims;
- workflow/security/release configuration;
- lock/constraint/dependency files;
- generated architecture artifacts only insofar as they reveal package-boundary drift.
Do not infer that a branch is irrelevant from its name.
Calendar branch
Reuse #682's retain/refactor/supersede/drop map. The terminal gate must prove that every provider-neutral useful mechanic selected for retention has landed in the certified tree and that the licensed-provider source-of-truth assumption has not.
Dev/main convergence
The final merge/rebase sequence must be documented and followed by qualification of the resulting tree, not by assuming pre-merge evidence on either parent certifies conflict resolution. Scientific/content hashes, schema registries and handoff identities bind the post-convergence tree.
Dependency branches
Dependency/workflow updates are part of computational environment identity. For each outstanding dependency branch, either land and requalify it or explicitly defer/reject it before freezing the handoff environment. No pending dependency branch may ambiguously sit between the certified source tree and the lock/SBOM/environment identity.
No-stranded-work proof
Create a machine-readable terminal branch inventory binding branch/ref, head SHA, merge base, file-delta digest, disposition, successor/merge commit and reviewer/evidence status. The verifier fails if:
- a live branch contains an unclassified source/schema/test delta;
- a retained delta is absent from the final tree without explicit supersession;
- the final tree differs after certification;
- a dependency/lock change is applied without successor environment identity;
- a stale branch-private API is still required by the clean-room consumer.
Post-convergence gates
Run the applicable full hooks/tests/typing/docs/build/critical mutation/property suites and handoff clean-room tests against the exact resulting tree. Recompute package/tree/environment/schema/handoff identities after convergence.
Branch cleanup
Actual deletion is optional and governed by repository retention/operator preference. Certification requires unambiguous disposition, not destructive cleanup. If branches are retained for history, documentation must make clear that they are not alternate supported scientific heads.
Acceptance
Exactly one tree is identified as the certified histdata.com-tools ML-handoff implementation; every live side branch has a machine-readable disposition; no scientifically relevant code/test/schema/environment delta is stranded; the post-convergence tree passes its required gates; and #721 references only artifacts generated from that exact tree.
Parent handoff milestone: #721
Related existing convergence: #666 #682
Related release/environment: #513 #526 #637–#646
Problem
#666 correctly governs branch convergence before the production trader subsystem lands, but the repository's final responsibility boundary needs a terminal repository-wide convergence gate after all admitted calendar, forecast, trader, feature, reproducibility and training-substrate work has landed.
At the August 20, 2026 terminal editorial audit the live branches are:
main;dev;codex/492-economic-calendar-vintages;dependabot/github_actions/github-actions-72d335de65;dependabot/pip/python-packaging-be9169ee7a.devandmainare materially divergent; the calendar branch is stale and semantically superseded in part; the dependency branches alter release/environment inputs. A clean ML handoff cannot be certified while scientifically relevant code, tests, schemas, documentation or dependency/environment changes remain ambiguously stranded on side branches.Outcome
Before #721 can close, produce one reviewed branch-disposition artifact and one exact certified handoff tree. Every live branch and any branch created during the remaining roadmap receives a terminal disposition:
Required audit
For each branch compare against the intended release/handoff base and classify every changed file by subsystem and scientific relevance. Explicitly inspect:
Do not infer that a branch is irrelevant from its name.
Calendar branch
Reuse #682's retain/refactor/supersede/drop map. The terminal gate must prove that every provider-neutral useful mechanic selected for retention has landed in the certified tree and that the licensed-provider source-of-truth assumption has not.
Dev/main convergence
The final merge/rebase sequence must be documented and followed by qualification of the resulting tree, not by assuming pre-merge evidence on either parent certifies conflict resolution. Scientific/content hashes, schema registries and handoff identities bind the post-convergence tree.
Dependency branches
Dependency/workflow updates are part of computational environment identity. For each outstanding dependency branch, either land and requalify it or explicitly defer/reject it before freezing the handoff environment. No pending dependency branch may ambiguously sit between the certified source tree and the lock/SBOM/environment identity.
No-stranded-work proof
Create a machine-readable terminal branch inventory binding branch/ref, head SHA, merge base, file-delta digest, disposition, successor/merge commit and reviewer/evidence status. The verifier fails if:
Post-convergence gates
Run the applicable full hooks/tests/typing/docs/build/critical mutation/property suites and handoff clean-room tests against the exact resulting tree. Recompute package/tree/environment/schema/handoff identities after convergence.
Branch cleanup
Actual deletion is optional and governed by repository retention/operator preference. Certification requires unambiguous disposition, not destructive cleanup. If branches are retained for history, documentation must make clear that they are not alternate supported scientific heads.
Acceptance
Exactly one tree is identified as the certified
histdata.com-toolsML-handoff implementation; every live side branch has a machine-readable disposition; no scientifically relevant code/test/schema/environment delta is stranded; the post-convergence tree passes its required gates; and #721 references only artifacts generated from that exact tree.