coordination: 2026-08-18 closeout execution, dependency, and maintainer-decision queue

[ll7]

Purpose

Convert the current open-issue surface into a bounded execution and decision queue. This is the authoritative coordination snapshot for the 2026-08-18 closeout pass. It does not replace the owning issues, authorize scientific claims, submit compute, or create a second readiness framework.

The queue is ordered by repository integrity, evidence truthfulness, release/legal exposure, and ability to unblock several downstream paths. New research expansion remains below closeout, publication, and already-authorized evidence work.

Operating rules

• Keep no more than three P0/P1 implementation PRs and two campaign/operations lanes active at once.
• One issue has one implementation owner. Do not open a competing PR when an exact owner is named below.
• state:working means a live PR or validated implementation exists. state:ready means a bounded slice can start. Blocked parents are not agent dispatch targets.
• Close an issue only after its exact acceptance criteria pass on the merged head. A merged helper or green smoke is not evidence that an empirical parent is complete.
• Preserve fallback, degraded, missing, incomplete, and unavailable states explicitly.

Immediate execution queue

Order	Issue / owner	Required action	Exit condition
1	#7451	Add local capacity preflight, shared-venv default, and safe dry-run reclamation inventory.	Worktree creation fails before partial checkout on low space; safe host readback passes.
2	#7448	Reject fabricated/non-live exact-head SHA carriers before PR-body mutation and in hosted body contracts.	Exact live head is required; affected open PRs no longer present false exact-head claims.
3	#7376 / PR #7406	Restore green main without weakening the optimized-mode invariant test.	Current main fast/required CI is green.
4	#7297 / PR #7428	Exclude model weights from source distributions and verify archive contents.	Clean sdist/wheel inspection is green and contains no model weights.
5	#7300 / PR #7431	Make licensing workflows trigger on every consumed legal/provenance input.	Trigger-coverage fixture and focused release checks pass.
6	#7407 / PR #7417	Require canonical merge-gate authority in the stacked_prs direct merge path.	Missing/stale/failed gate evidence and explicit holds block the final CAS path.
7	#7408	Apply and verify main-protection only after the caller/workflow fixes are merged.	Required gate context, merge queue, conversation resolution, and a healthy post-merge observation are proven.
8	#7416 / PR #7420	Distinguish current failure, queued starvation, and superseded checks.	Exact-head queue state is truthful while merge remains fail-closed.
9	#7449	Stop the issue audit from reopening decisions after a valid later canonical ruling.	Full read-only plan has no ruled-issue false positives and still catches genuine reopen requests.
10	#7128 / PR #7144	Land canonical exact-repeat execution-context provenance.	Cross-host verdicts expose all required context mismatches and legacy reports fail closed.
11	#7430 / PR #7436	Synchronize every tracked SVG with the map registry or an approved exclusion.	Generator and validator agree on merged main.
12	#7454 / PR #7357	Land observed-condition binding and horizon identity checks in the CALF/LegNav comparator.	Swapped/mismatched rows block; canonical smoke remains available.
13	#7327	Select one characterization PR owner between #7446 and #7456; close the duplicate implementation path.	One reviewed characterization baseline lands; no production refactor occurs.
14	#7298 / PR #7433 and #7299 / PR #7432	Complete dependency and asset-rights inventories without implying rights from project licensing.	Unknown/conflicting rights remain explicit and release checks are reproducible.
15	#7287 / PR #7440, #7265 / PR #7437, #7276 / PR #7438, #7285 / PR #7439	Finish bounded workflow/docs repairs already represented by active PRs.	Each owning issue is closed only after its focused merged-head validation.

Authorized operations and campaign queue

These lanes are ordered independently from local code work. Do not substitute more preparation issues for a missing execution receipt.

1. compute(5579): run canary-only six-row MPC solver execution gate before #6700 production #7313 → compute decision: launch the frozen #5579 production campaign after the passed 6/6 canary #6700 → SLURM study: test model-predictive under-tuning with matched budgets and held-out evaluation #5579: run only the six-row MPC canary; production follows only after pass_6_of_6.
2. preflight: make #6642 ready for its authorized SLURM radius sweep #7256 → benchmark(6600 Gate 2): SLURM production radius sweep (0.5/0.8/1.0 m) over 14 planners x 48 cells x seeds 111-140 #6642 → benchmark(6600 Gate 3): rank-stability analysis, durable evidence bundle, and verdict propagation #6643 → benchmark: quantify planner-ranking sensitivity to collision-envelope radius #6600: make the radius packet submit-ready without compute; execute the one authorized attempt only after every admission predicate passes; analyze only complete/fail-closed inputs.
3. benchmark: submit the missing #5346 S30 planner shards #7049 → evidence recovery: finalize and assess the frozen 34,560-row S30 mean-matched campaign #5346: custody-check the missing S30 shards, submit only genuinely missing ORCA/Social Force shards, and reuse the completed Goal shard.
4. interpretation handoff: admit or bound the completed 2,160-cell speed-tier campaign #6102 → benchmark: execute pre-submission pedestrian-pace sweep at typical walking speed #6561: complete and integrity-check robot-speed evidence before the pedestrian-speed production run.
5. release-op(6155): publish immutable 0.0.5 tag, GitHub Release, and Zenodo version #7320/release-verify(6155): independently retrieve and verify published 0.0.5 artifacts and DOI lineage #7321: publication remains blocked by the exact rights/disposition surface; no tag, release, or DOI claim without the selected immutable route and independent retrieval.

Dependency graph requiring explicit propagation

#7451 local capacity
  └─ unblocks all local worktree/validation lanes

#7445 0.0.3 metadata disposition
  └─ #7447 duplicate-custody comparison
      └─ separate retirement authorization, if byte identity is proven

#7128 / PR #7144 current context contract
  ├─ #7452 historical #5498 compatibility disposition
  └─ #5498 defensible second-host exact-repeat matrix

#7129 / PR #7139 + #7450 envelope-version decision
  └─ #6643 radius Gate-3 durable evidence

#7256 preflight
  └─ #6642 production radius sweep
      └─ #6643 analysis
          └─ #6600 bounded verdict

#7313 six-row canary
  └─ #6700 production MPC tuning-sensitivity campaign
      └─ #5579 bounded interpretation

#7407 caller authority + reviewed workflow changes
  └─ #7408 protection rollout and live merge-group proof

Maintainer decision queue

Resolve these before dispatching implementation that depends on the choice:

1. schema: radius_rank_stability envelope stays v1 while gaining required fields #7450: recommended bump-radius-envelope-v2 before the first durable report.
2. reproducibility: registered #5498 exact-repeat reports are not replayable under the #7128 execution-context contract #7452: recommended document-pre-7128-verification-boundary; retain the current verifier default.
3. benchmark: #5409 launch-packet validator and paired-horizon report disagree on valid campaign IDs #7453: recommended share-explicit-campaign-id-pair across launch and report contracts.
4. release: close the 0.0.3 DOI and reproduction-status gap #7445: recommended record-no-doi-keep-not-run unless a named archival requirement justifies a deposit or clean reproduction.
5. repo-hygiene: legacy model checkpoint binaries (~9.3 MB) committed to git, not LFS — inconsistent with registry strategy #6268: retain working-tree migration without history rewrite unless a new measured cost justifies repository-wide coordination.
6. workflow: adopt risk-tiered stale-base merge validation #6272/workflow: wire or remove orphaned PR checkers (check_pr_closing_reference, check_merge_queue_protection) #7287: keep exact-head proof mandatory; select one stale-base and checker-wiring policy rather than parallel enforcement paths.

Existing canonical rulings on #7409, #7411, #7412, and #6095 are terminal until a later explicit reopen event; #7449 must make the audit respect them.

Parked / post-closeout work

Keep the #7381 scenario-intelligence programme and children #7392–#7399 as proposal-stage/post-closeout work. The only currently justified dissertation-supporting vertical slice is the existing trace-dossier path under #7086. Do not launch new training, search, forecasting, clustering, or planner campaigns from the portfolio epics.

Audit and completion

For each queue revision, post:

• issues closed because merged work fully satisfies acceptance;
• issues changed from ready to working because an active PR exists;
• blocked issues whose prerequisites closed;
• duplicate PR/issue paths retired;
• decisions made, with exact ruling tokens;
• campaign/operation receipts obtained or exact blockers retained.

This coordination issue closes when the P0/P1 integrity queue is empty, authorized operations have terminal receipts or explicit deferrals, and the residual open surface is correctly classified as ready, blocked, decision-required, parked, or post-closeout.

schema: goal_autopilot_preparation.v1
repository: ll7/robot_sf_ll7
issue: 7457
source_body_sha256: 10ce50b1baf738874698b294a627d021da85241f7a5d1bb8b36033a32668a50d
source_comments_sha256: 
audit_schema: open_issue_contract_audit.v1
audit_digest: 1c191411793929640684e0827d763f3a2009a8682ab98dcefa8c2ded3e54f4ea
audit_classification: state_conflict
next_action: reconcile_state_labels
authority: lifecycle_owner
execution_mode: lifecycle
preferred_worker: MaxRunner
expected_pr_runner_label: runner:max
implementation_admitted: False
state_ready_change_proposed: False
mutation_batch: open-issues-20260830-04

This packet is preparation evidence only. It never overrides live labels, exact claim state, branch state, typed dependencies, domain gates, compute authority, release authority, or scientific evidence rules.

[ll7]

Reconciliation changes applied

The first closeout pass has now changed repository state as follows:

• All open issues newer than evidence: refresh Chapter 7 v2 package after the frozen collision-exclusion ruling #7412 were reviewed and received an issue-specific implementation, dependency, or maintainer-decision packet.
• friction: reap stale worktree venvs — /dev/shm and / hit 100% and blocked all worktree creation #7455 was closed as a duplicate of the canonical disk-capacity issue friction: host disk exhaustion blocks agent worktree creation and local validation #7451; its live-process, dirty-worktree, shared-venv, and evidence-custody safeguards were carried forward.
• PR test: characterize camera-ready campaign orchestration #7446 was closed as a duplicate implementation path for test(6456): characterize _run_campaign_orchestrator before any structural decomposition #7327. PR test(benchmark): characterize camera-ready campaign orchestration (#7327) #7456 is the sole characterization owner.
• friction: distinguish queued CI starvation from superseded-check failures #7416 and friction: synchronize tracked SVG maps with the map registry #7430 moved to state:working because PRs fix(ci): classify queued runner starvation (#7416) #7420 and fix(maps): synchronize tracked SVG catalog #7436 already own their implementation.
• fix(benchmark): bind CALF/LegNav paired slots to the observed observation contract #7454 moved to state:working; its prepared binding fix should land through PR feat(research): add CALF/LegNav comparator diagnostic #7357.
• Older live-PR issues were reconciled from ready/blocked to working, including P0: unbreak main — CI failing at 5a3a9b9b1 (auto-filed by main-ci-watch) #7376, bug(release): exclude model weights from Robot SF source distributions #7297, bug(release): trigger licensing checks on all provenance and legal inputs #7300, bug: stacked_prs direct merge path bypasses the required Merge Queue Gate #7407, reproducibility: bind exact-repeat cross-host verdicts to canonical execution-context provenance #7128, friction: make PR queue polling resilient to transient GitHub GraphQL 503s #7371, friction: retry transient GitHub API failures in review-bot routing #7372, workflow: collect canonical archetype/evidence-tier metadata in all issue forms (#1512 contract) #7265, test: remove cwd-dependent "run from repo root" skips in regression tests #7276, technical-debt: consolidate the two parallel context-note freshness checkers #7285, workflow: wire or remove orphaned PR checkers (check_pr_closing_reference, check_merge_queue_protection) #7287, release: add reproducible dependency license inventory for optional extras #7298, and licensing: inventory maps, media, examples, and data rights before release #7299.
• workflow: wire or remove orphaned PR checkers (check_pr_closing_reference, check_merge_queue_protection) #7287's decision is resolved: the two scripts are intentional opt-in support tools; PR docs: classify development support tools #7440 is the owner.

Queue correction

Item 13 in the original table is resolved: use #7327 / PR #7456. Do not revive PR #7446 or merge both characterization modules.

Immediate dispatch order

Until local capacity is restored, do not multiply worktrees. The next sequence remains:

1. friction: host disk exhaustion blocks agent worktree creation and local validation #7451 capacity/reclamation safeguards;
2. bug(provenance): PR bodies carry fabricated exact-head SHAs in gate-verdict trailers #7448 false exact-head carrier prevention;
3. active P0 merges/reviews for P0: unbreak main — CI failing at 5a3a9b9b1 (auto-filed by main-ci-watch) #7376, bug(release): exclude model weights from Robot SF source distributions #7297, bug(release): trigger licensing checks on all provenance and legal inputs #7300, and bug: stacked_prs direct merge path bypasses the required Merge Queue Gate #7407;
4. bug: activate main-protection merge gate and prove a healthy post-merge observation #7408 maintainer protection rollout only after those caller/workflow changes are effective.

No compute was submitted, no release was published, no file was deleted, and no scientific or dissertation claim was changed during this reconciliation.

[ll7]

Live delta — 2026-08-18, second reconciliation pass

The queue produced new implementation and workflow state after this issue was filed. Apply the following updates.

Duplicate and queue control

• bug(provenance): PR bodies carry fabricated exact-head SHAs in gate-verdict trailers #7448: PR fix(dev): fail closed on non-live exact-head SHA carriers (#7448) #7471 is the sole implementation owner. Competing PR fix(workflow): reject fabricated PR head provenance #7462 was closed because it allowed a stale but Git-resolvable commit to satisfy an exact-head carrier. Equality to the live remote PR head is the rule.
• friction: competing PRs for the same issue can be opened without detecting an active claim #7474: new P1 prevention issue. The canonical PR opener must detect an existing open PR for the same issue before creating another implementation.
• Routine Dependabot PRs deps: bump the python-minor-patch group with 8 updates #7480 and deps: bump setuptools from 83.0.0 to 84.0.0 #7481 were closed under the closeout freeze. Recreate only after the P0/P1 queue is drained, unless a concrete security advisory requires an earlier update.

New blocking workflow repairs

• friction: bound reclaim inventory directory-size scans #7476 (P1): PR fix(dev): preflight worktree capacity before checkout #7461's capacity gate is useful, but friction: host disk exhaustion blocks agent worktree creation and local validation #7451 cannot close until reclaim inventory size scans are bounded and return explicit unknown on timeout.
• friction: refresh benchmark namespace inventory after merged trace-dossier module #7482 (P1): refresh the benchmark namespace inventory for the already-merged trace_dossier_package.py. This currently blocks full readiness of unrelated PRs after thousands of passing tests; one audit-only PR should own it.
• friction: docs proof helpers reuse incomplete fresh-worktree environments #7478 (P2): fresh-worktree docs helpers must not leave or reuse an incomplete .venv without an actionable bootstrap failure.
• friction: make evidence ratchet baseline refresh update its review companion #7467 (P3): evidence-ratchet baseline refresh must emit the review-companion delta before the full readiness suite.

Recorded bounded rulings

• fix(packaging): wheel shared-data table is inert (tool.hatchling typo) #7458: remove-inert-wheel-shared-data-until-rights-cleared — do not start shipping rights-blocked SVGs by correcting an inert table.
• decide: dependency-license gate scope for unrepresented lock rows #7459: gate-declared-profiles-and-classify-unrepresented-lock-rows — supported profiles are the gate surface; all excluded lock rows need explicit grouped dispositions.
• friction: pin empty-changed-lines coverage verdict introduced by PR #7435 #7460: treat-pure-deletion-as-zero-new-lines-covered — no whole-file fallback for a diff with zero new executable lines.
• friction: make optional readiness model downloads resilient to GitHub rate limits #7470: verified-cache-retry-then-blocked-external — no credentialed mirror is authorized.

New implementation ownership

The earlier decision queue now has active implementation owners:

• release: close the 0.0.3 DOI and reproduction-status gap #7445 → PR docs(release): record no-DOI correction for 0.0.3 and keep reproduction not_run (#7445) #7477
• friction: issue audit re-adds decision-required after canonical ruling comments #7449 → PR fix(audit): honor canonical issue rulings #7463
• schema: radius_rank_stability envelope stays v1 while gaining required fields #7450 → PR fix(benchmark): version radius stability envelope #7479
• reproducibility: registered #5498 exact-repeat reports are not replayable under the #7128 execution-context contract #7452 → PR fix(repro): bind exact-repeat verdicts to execution context #7144
• benchmark: #5409 launch-packet validator and paired-horizon report disagree on valid campaign IDs #7453 → PR fix(benchmark): accept reviewed issue 5409 rerun receipts #7146
• evidence: bind Chapter 7 v2 to a canonical source registry and durable retrieval #7411 → PR feat(provenance): bind Chapter 7 v2 to canonical source registry #7468
• evidence: refresh Chapter 7 v2 package after the frozen collision-exclusion ruling #7412 → PR feat(evidence): refresh Chapter 7 package after frozen ruling #7465
• friction: host disk exhaustion blocks agent worktree creation and local validation #7451 → PR fix(dev): preflight worktree capacity before checkout #7461, with residual friction: bound reclaim inventory directory-size scans #7476

Effective freeze

Until the P0/P1 integration queue is materially smaller:

1. Open no new feature, research, broad refactor, or routine dependency PR.
2. Permit at most one open implementation PR per issue.
3. Prefer finishing, reviewing, closing, or explicitly blocking existing PRs over filing another helper issue.
4. Do not enable main-protection under bug: activate main-protection merge gate and prove a healthy post-merge observation #7408 until the required caller/workflow fixes are merged and a real merge-group proof can be observed.

The immediate objective is now queue drainage, not more issue discovery.

[ll7]

Open-PR reconciliation — 2026-08-18 final live pass

This comment is the authoritative PR-level companion to the issue queue. GitHub live state was re-read after concurrent pushes, closures, and merges. No PR was merged by this audit.

Repository changes observed during the pass

• PR fix(dev): fail closed on non-live exact-head SHA carriers (#7448) #7471 merged through the repository workflow at commit 2e0f1d557e0d9d0fceab37db4307895a60ef4711. It is now the canonical exact-head carrier guard.
• PR fix(compliance): add dependency license inventory (#7298) #7433 merged through the repository workflow at commit 9378779aad54727796e6b48aff1aa3c87956a374. The dependency-license inventory exists; unresolved profile rows and policy dispositions remain explicit.
• PR fix(workflow): reject fabricated PR head provenance #7462 was closed in favour of fix(dev): fail closed on non-live exact-head SHA carriers (#7448) #7471 because it accepted non-live but Git-resolvable SHAs as exact-head carriers.
• PRs test: refresh benchmark namespace baseline after trace dossier #7485 and test: refresh benchmark namespace inventory count #7488 were closed as narrower duplicates of fix(dev): refresh benchmark namespace inventory (#7482) #7486. Competing PR test(ci): keep dependency review contract step-order independent #7490 remained closed.
• PRs feat(research): expose explicit yield dimensions #7092 and feat(research): execute answerability proof surfaces #7102 were closed as superseded by consolidated owner feat(research): wire answerability into campaign admission #7469.
• PR docs: align evidence template vocabularies #7307 was closed because its live stacked diff contradicted its claimed four-file template-only scope.
• PR fix(dev): fail closed on incomplete worktree venvs in docs-proof and shared-venv helpers (#7478) #7492 was closed as a competing implementation of friction: docs proof helpers reuse incomplete fresh-worktree environments #7478; profile-based owner fix(dev): fail closed on incomplete worktree environments (#7478) #7483 remains canonical.
• Routine dependency PRs deps: bump the python-minor-patch group with 8 updates #7480, deps: bump setuptools from 83.0.0 to 84.0.0 #7481, and deps: bump the actions group with 3 updates #7484 were closed under the closeout dependency freeze.

Immediate merge/review queue

1. fix(dev): refresh benchmark namespace inventory (#7482) #7486 — current-main test-contract repair for friction: refresh benchmark namespace inventory after merged trace-dossier module #7482 and friction: dependency review test assumes the license action is the last workflow step #7489.

   • Sole owner after duplicate retirement.
   • Local final readiness passed at current head 39a072752ca812ab3417c58462152ece33963586.
   • Current-head CI, CodeQL, security, planner-smoke, body-contract, and PR-contract workflows are still queued.
   • Earlier reviews target predecessor heads; require a fresh exact-head review.

2. fix(ci): emit evidence ratchet review deltas #7487 — evidence-ratchet review-delta generator.

   • Sole owner of friction: make evidence ratchet baseline refresh update its review companion #7467.
   • Current head 9497bdca881786f0da0492f1e3a142025d39f8d8 has 43 focused tests and exact-head self-review.
   • Hosted workflows and independent review remain pending.
   • Must remain opt-in, emit TODO dispositions, and never update or approve the human companion automatically.

3. P0: unbreak main — tolerate contended optimized guard proof timeout #7406 — P0 optimized-mode guard timeout repair.

   • One-file fail-closed test repair with green recorded workflows.
   • Refresh/prove current-base applicability and obtain independent exact-head review; preserve a real 180-second wedge failure.

4. fix(ci): require exact-head changed coverage for admission #7435 — exact-head changed-coverage admission.

   • Current head includes the ruled pure-deletion 0/0 semantics.
   • Earlier accepted reviews are stale; current CI and exact-head review are required.
   • After merge, refresh fix(dev): label committed readiness scope #7475 and require older PRs to push a new head before relying on the new check.

5. fix(release): bind legal inputs to validators #7431 — legal/provenance input trigger coverage.

   • Current branch has partial green legal/security checks but stale review evidence and queued workflows.
   • Require current-head legal/release review. This PR grants no rights.

6. fix: fail closed on Robot SF gate evidence #7343 → fix(workflow): gate stacked merges on queue check #7417 → bug: activate main-protection merge gate and prove a healthy post-merge observation #7408 — merge-authority sequence.

   • fix: fail closed on Robot SF gate evidence #7343 owns the trusted source-head workflow.
   • Refresh and reconcile its carrier/hold parser with merged fix(dev): fail closed on non-live exact-head SHA carriers (#7448) #7471; prove event triggers do not loop and use trusted-base code with live PR state.
   • Then refresh fix(workflow): gate stacked merges on queue check #7417 so the direct stacked_prs CAS path consumes the same authority.
   • Only then apply branch protection and run the real merge-group proof under bug: activate main-protection merge gate and prove a healthy post-merge observation #7408.

Closeout-support queue after #7486

These are bounded, reviewable repairs. Each must refresh onto the resulting main, rerun focused tests plus final readiness, and obtain exact-head review:

• fix(dev): fail closed on incomplete worktree environments (#7478) #7483 — named dependency profiles for incomplete worktree environments.
• fix(dev): preflight worktree capacity before checkout #7461 — pre-checkout capacity guard and bounded read-only reclaim inventory.
• fix(audit): honor canonical issue rulings #7463 — chronological canonical-ruling classifier.
• test(benchmark): characterize camera-ready campaign orchestration (#7327) #7456 — tests-only camera-ready orchestrator characterization.
• fix(tools): make W&B run-tree inventory symlink-safe (#7444) #7472 — symlink-safe, read-only W&B run-tree inventory.
• fix(ops): make issue 5303 v2 checker authoritative #7473 — v2 checker authority while preserving historical v1 evidence.
• fix(models): bound GitHub release download retries #7494 — verified-cache-first model retrieval with bounded retry then external_unavailable.
• fix(workflow): detect competing open PRs in prepublication gate (#7474) #7493 — competing-PR guard, after narrowing hard-block ownership signals; generic Refs/Part of text must not supersede legitimate child or stacked PRs.

Evidence and release stack

Process this stack in order. Do not skip directly to admission or publication.

#7486 current-main test contracts
  -> #7487 ratchet companion-delta tooling
      -> #7468 legacy v1/v2 custody registry
          -> extend custody to exact v2.1 identity
              -> #7465 immutable v2.1 package refresh
                  -> #7415 final v2.1 verifier hardening
                      -> #7323 human admission receipt and bounded propagation

Additional constraints:

• feat(provenance): bind Chapter 7 v2 to canonical source registry #7468: immutable Git history proves custody/retrievability, not redistribution rights. Replace repository-license-based rights assertions with rights not evaluated by this custody record or a separate reviewed rights record.
• feat(evidence): refresh Chapter 7 package after frozen ruling #7465: may remain not_admitted only; no completion until the exact v2.1 tree is in the custody registry.
• fix(evidence): harden Chapter 7 v2 diagnostic verification #7415: requires Domain-Aware Approval and must verify the registered v2.1 identity after the preceding stack lands.
• docs(release): record no-DOI correction for 0.0.3 and keep reproduction not_run (#7445) #7477: no-DOI correction follows fix(ci): emit evidence ratchet review deltas #7487 and current-main refresh; preserve tag/assets and reproduction_status: not_run.
• docs: record Issue 7313 MPC canary diagnostic #7423: remove or justify unsupported numerical confidence percentages, independently read back the W&B source receipt, and preserve the six-row/100-step diagnostic boundary.
• docs(research): close out lane formation diagnostic (#6962) #7495: may close diagnostic: is the lane-formation non-result a corridor-configuration artifact or a model property? #6962 only as diagnostic_complete_inconclusive_with_raw_source_unavailable, after domain and source-custody review. It does not resolve spontaneous emergence or authorize calibration: can parameter tuning produce lane formation in bidirectional_corridor, and at what fidelity cost? #6969 Stage B.
• feat(research): add negative-result mechanism-boundary atlas #7046: card-level result-state and bounded-claim interpretations require maintainer domain approval.
• feat(adversarial): add issue-6105 outcome producer #7081: remains blocked on the native-versus-adapter runtime contract and domain approval; no campaign is authorized.

Other ruled contract PRs

• fix(repro): bind exact-repeat verdicts to execution context #7144: approved execution-context contract; refresh after fix(dev): refresh benchmark namespace inventory (#7482) #7486 and preserve historical reproducibility campaign: execute and register the #5263 exact-repeat matrix after ORCA restoration #5498 bytes/verdicts.
• fix(benchmark): accept reviewed issue 5409 rerun receipts #7146: approved shared versioned campaign-ID pair; refresh after fix(dev): refresh benchmark namespace inventory (#7482) #7486 and obtain current-head implementation review. No compute is authorized.
• fix(benchmark): version radius stability envelope #7479: approved radius-envelope v2 decision; branch is stale/non-mergeable and needs complete current-base readiness.
• feat(research): add CALF/LegNav comparator diagnostic #7357: remains blocked until fix(benchmark): bind CALF/LegNav paired slots to the observed observation contract #7454 condition-slot binding and horizon identity checks are incorporated and the diagnostic boundary is approved.
• fix(workflow): route metadata conflicts to fresh review #7419: refresh only after merged fix(dev): fail closed on non-live exact-head SHA carriers (#7448) #7471 so conflict routing preserves the live-head carrier guard.
• fix(ci): classify queued runner starvation (#7416) #7420: refresh after current-main repairs; queued/starved states remain fail-closed, never success.

Parked PRs

Keep these in draft until the P0/P1 and evidence-closeout queues are clear:

• feat(research): add Open Dreamer model quality gate #7104 Open Dreamer quality-gate research slice.
• feat(benchmark): prepare legacy checkpoint cutover parity #7236 rights-gated checkpoint-cutover preparation.
• fix(workflow): harden stale-base observation provenance (#7261) #7336 stale-base policy measurement support.
• fix(training): bind optimization smoke arms to matched order (#7254) #7364 predictive-training smoke correction; prior fabricated exact-head claim has been removed from the body.
• audit: inventory tracked production assertions #7365 production-assert inventory.
• refactor: share PySF state slice constants (clean replacement) #7389 PySF state-slice deduplication.
• refactor: share Bresenham rasterizer (clean replacement) #7390 Bresenham rasterizer deduplication.
• feat(research): execute feasibility-first search on a real manifest #7414 feasibility-first real-manifest diagnostic.
• refactor: consolidate context note freshness checks #7439 context-note freshness consolidation.
• test: share homogeneous probe command fakes #7441 subprocess fake deduplication.
• refactor: share non-empty string validation #7443 partial string-validation migration.
• test: cover obstacle force geometry branches #7464 obstacle-force test repair.
• test: enforce skipped video manifest contract #7466 video-manifest test hardening.
• fix(dev): label committed readiness scope #7475 readiness wording repair until fix(ci): require exact-head changed coverage for admission #7435 lands.
• feat(research): wire answerability into campaign admission #7469 consolidated answerability/admission integration until friction: wire answerability into production campaign admission and complete research-yield dimensions #7090 Domain-Aware Approval.

Operational rules

• Maximum active review set: three implementation PRs plus two evidence/operations lanes.
• A draft PR must not carry merge-ready; stale instances found during this pass were removed.
• An accepted review is exact-head evidence only. A push, rebase, or metadata change requires a new live-state readback and, where applicable, a new review.
• Do not merge from body text alone. Require terminal current-head checks, resolved review threads, the canonical gate, and an unchanged live head.
• Do not open another PR for an issue that has a canonical owner. Use fix(workflow): detect competing open PRs in prepublication gate (#7474) #7493 only after its ownership-signal semantics are narrowed as recorded above.

[ll7]

Coordination delta: requested PR consolidation and queue freeze

The following requests are now recorded on the owning PRs:

1. fix(dev): refresh benchmark namespace inventory (#7482) #7486: freeze the branch, reconcile the live exact head once, rerun final readiness, and land before unrelated blocked PRs are recycled again.
2. fix(packaging): remove inert tool.hatchling wheel block and guard the hatch namespace (#7503) #7509 / fix(packaging): drop inert wheel shared-data table (issue #7458) #7499: make fix(packaging): remove inert tool.hatchling wheel block and guard the hatch namespace (#7503) #7509 the sole packaging-namespace owner, transfer the explicit robot_sf/maps shared-data exclusion and fix(packaging): wheel shared-data table is inert (tool.hatchling typo) #7458 closing reference, then close fix(packaging): drop inert wheel shared-data table (issue #7458) #7499 as superseded.
3. fix(dev): surface evidence-ratchet companion delta on baseline refresh (#7467) #7510 / fix(ci): emit evidence ratchet review deltas #7487: make fix(dev): surface evidence-ratchet companion delta on baseline refresh (#7467) #7510 the sole friction: make evidence ratchet baseline refresh update its review companion #7467 owner, consolidate the read-only companion audit and pre-write deterministic template around one delta model, then close fix(ci): emit evidence ratchet review deltas #7487 as superseded.
4. P0: unbreak main — tolerate contended optimized guard proof timeout #7406: reproduce the timeout problem on current main before retaining the 60→180 second increase; close as stale if the mechanism no longer reproduces.

Until these four lanes reach terminal dispositions, do not open another PR for the same issues or adjacent maintenance symptoms. Existing exact-head review evidence becomes invalid after every head move; one writer should own each final stabilisation window.

This coordination update authorizes no merge, branch-protection change, evidence admission, campaign, release, or claim change.

[ll7]

Follow-up filing: Chapter 7 v2 closeout scan

The final follow-up scan found no new standalone issue to create; the actionable work is already owned by existing issues:

• Live-state refresh: re-read the exact origin/main SHA and evidence-admit(7097): issue and independently verify Chapter 7 v2 admission receipt, then propagate bounded consumers #7323/evidence: admit and propagate Chapter 7 release-cell package v2 #7097/friction: reconcile closed #7042 ruling with Chapter 7 v2 diagnostic status #7548 state before making any new evidence claim. The last package proof was at 41bd0972b84bc0056532e7bc9ca5705e8f368dea; origin/main later advanced to 7a554c54881b245d5b9132fd89429d1511ba0a4e. GitHub API throttling means this is a resumable revalidation step, not evidence of admission.
• Diagnostic wording/regression: friction: reconcile closed #7042 ruling with Chapter 7 v2 diagnostic status #7548 owns reconciliation of the stale metric_semantics_blocked_issue_7042 wording and the focused exclusion/status assertions.
• Durable custody and admission: evidence: bind Chapter 7 v2 to a canonical source registry and durable retrieval #7411, evidence: refresh Chapter 7 v2 package after the frozen collision-exclusion ruling #7412, evidence-admit(7097): issue and independently verify Chapter 7 v2 admission receipt, then propagate bounded consumers #7323, and evidence: admit and propagate Chapter 7 release-cell package v2 #7097 own registry retrieval, immutable package handling, domain approval, independent verification, and the terminal admission receipt.
• Worktree friction/tidy-up: friction: benchmark namespace inventory should support detached review worktrees #7496 owns detached review-worktree support. Worktree removal remains deferred until ignored validation outputs and unrelated local material are classified and preserved.

No package bytes, admission status, or downstream consumer claim should change from this filing alone.