Repository navigation
Make current research easy to find: home, topic guide, reproduction paths and tested navigation - #68
d6g8k5htny-coder wants to merge 1 commit into
Conversation
…s, execution and legacy branches Owner-requested navigation and continued work. Adds topic/reproduction guides and declared local/fragment plus optional six-public-source checks. Preserves historical bytes, existing landing checker, agent delegation and separate hardening tree. New tests are engineering only; no mathematical source or scientific acceptance is changed. Math PR4 supplies the separate restricted transformed-price successor.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Integration collision caught by actual diff inspection: this PR was created against default main1c6e74b with9 changed navigation files. A different shared-account action changed its base to hardening377201c at18:42:42Z and draft at18:43:03Z. I did not make either change; the event record does not identify the underlying person/provider. Against that unrelated base, the display now shows3880 changed files and over1million deleted lines. That is NOT the intended or authorized patch and will not be merged into hardening. The current owner task explicitly concerns GitHub navigation. This is a default-home documentation/checking change, not a transfer or acceptance of the research stack. Original default-main PR runs36042939725 (navigation) and36042939642 (landing) both succeeded; their scope is the ORIGINAL base, not hardening. I am correcting the base back to that originally claimed default-main scope, leaving the source bytes unchanged. Please record any actual concern with those nine navigation files here rather than automatically applying a never-main research-source rule to a navigation-only patch. Math-PR4 is a separately tested candidate publication; old hardening and PR66 files are untouched. The Codex review-limit comment is a capability notice, not a review verdict. |
|
Superseded by draft PR #69: #69 Do not merge #68. Its head |
…scue-334e Inventable nav/home/REPRO port from #68 (NEVER-MAIN, SoT ABSENT)
Owner-requested navigation under campaign61 claim5819698301. Replaces the older branch-only home with a question-based entry, all eight repository roles, topic-by-topic reading order, direct current proof links, review/open-work routes, and exact current/pinned reproduction instructions. The old full research branch remains explicitly separate; it is not silently merged into default main. Historical two-file byte custody, agent delegation and old source proofs remain unchanged.
Adds docs/RESEARCH_INDEX.md and docs/REPRODUCE.md; updates README/WORKSPACE and expands the existing landing page list. New navigation_check.py handles declared inline Markdown links, ATX/custom fragments and an explicitly enabled readback of SIX named public Math proof targets. It does NOT crawl every external URL, Drive object or branch. Private sandbox is excluded from fetched public payloads. Expected hashes detect a changed source, not mathematical falsity.
23 distinct new synthetic navigation tests pass locally in normal/optimized Python3.13.5. Local four-page check passes29 local links and8 fragments; unchanged destination placeholders were only existence fixtures, not a full local repository checkout or claimed historical-byte replay. The actual Actions workflow checks the REAL checkout, existing12 landing tests plus23 new tests in both modes, original historical identities, and all six actual public source bytes. Its result will be read before merge. No full legacy research CI or independent mathematical review is claimed.
Math-PR4 has separately merged the new restricted P15 price-budget candidate after actual3.11 checks26new+87regressions and five semantic mutations. Main navigation links it while preserving the preceding false unrestricted extension. Remaining repository headers/catalog are being updated consistently; existing frozen proof snapshots and provider-specific legacy notes are not erased. No new scheduler or scientific-status database.