Consolidation: stop historical status sections from claiming to be current (no new kappa)

[Mister-Meeseeks]

Card: scope-navigation (consolidation track, chooser seed ef0afbea84ae0155fdc123ffbb7a0329, base 49b3157d). Scope unchanged. No new κ.

The confusing path

docs/research/current-status.md is linked from CONTRIBUTING and autoresearch as the place to read the current result. Below its real top section, it contains:

• two more # Current reviewed status headings, under the Conditional κ = 0.001672188119205421: improved T16 owner packing on the seven-slot k8 word #1042 snapshot (κ 0.001672188…) and the Conditional κ = 0.001661960547713947: T37 whole-owner packing and all-T bound #942 snapshot (κ 0.001661960…);
• # Selected construction: … (κ 0.00066, Shared-edge supplier, coordinated frames and entrance banks: conditional kappa = 6.61885549259598e-4 #186);
• # Current contracts and research status (2^-30, October 8), with ## Current and earlier results, ## Exact current parameters and bottleneck and ## Next research priority. That last one says the next improvement "should target the bit finite network", but today the complex side binds.

A reader or agent that searches or jumps by heading can land on any of these. Several research notes already warn that historical notes say "current" for obsolete checkpoints; this page is the most-linked instance.

Change

• These seven headings are renamed to name their checkpoint (for example ## Reviewed status at the #1042 checkpoint and ## Research priority at the 2^-31 integration (superseded; see autoresearch.md)).

• One banner is added where the history begins. It says that "current/selected/latest/next" inside historical sections refer to their own checkpoint, and points to selected-result.json and autoresearch.md.

• No section body is changed, so the history is preserved verbatim.

• New tests/test_research_current_status.py:

  • only the first heading may say current, selected or next research;
  • the top section must contain the selected record's decimal, review filename and reproduce command;
  • the banner must be present.

  The test fails on main's text (2 failures) and passes with this change. When the status page is next updated, the previous top heading must be demoted, which is exactly the step that was missed.

Checks

• python3 -B -m unittest discover -s tests -p 'test_research_*.py': 23 OK, 1 skipped.
• No links to the renamed anchors exist in the repository.
• Three packages pin current-status.md (u8-terminal-cone-census, e8-joint-reader-bound, r480-quad12-exact-seed12). All pin older blobs as historical provenance, none of which match current main, so no live pin changes.
• Overlap: find_overlap.py 'current-status' 'current reviewed status' 'navigation' found no open PR or discussion on this page. Open PR file lists were not searched exhaustively.

Feedback: this is from the same contributor as #1228 and #1231. The friction from the first session was that "current" appears in many superseded headings.

Prepared by Douglas Colkitt with Claude (Anthropic) assistance. Apache-2.0.

🤖 Generated with Claude Code

[Mister-Meeseeks]

100-PR batch review at 1a0ecf7f534a67a910b7b5a7e0abe46be074c609.

Merged to main, preserving the original contributor commits and package attribution.

Reviewed scope: Labels historical current-status sections with their checkpoints and adds selected-record consistency checks; preserves historical content and routes readers to the authoritative current certificate.

The pinned scoped command passed; the batch ledger contains its command, input hashes, environment and log. This incorporates the research/tooling contribution and does not change the selected κ or discharge the inherited multiplication-theorem assumptions.

Batch review, attribution and evidence. Thank you for the contribution.