chore: delete the five unmapped root entries - #1097
Closed
hyperpolymath wants to merge 1 commit into
Closed
hyperpolymath wants to merge 1 commit into
hyperpolymath wants to merge 1 commit into
Conversation
Owner ruling D241 (2026-09-30): delete all five rather than map or relocate. Removed from the repository root (git history keeps every byte): ULTRAPLAN-2026-09-24.adoc, ULTRAPLAN-2026-09-29.adoc, arena-session-787/, patches/, ziz-drop/. Gate D (scripts/check-standards-map.sh): rc=1 with 5 violations on main 74d2f66, rc=0 on this tree. Positive control: an unmapped probe file at the root makes it fail again with 1 violation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QYY8Gp4v4x2J7iSNn1vZ57
Contributor
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (23)
💤 Files with no reviewable changes (23)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (15)
📝 SummarySummary by CodeRabbit
WalkthroughThe pull request deletes two issue-triage documents, four session records, a stored patch, and the Žiz design, interpreter, examples, and Tree-sitter grammar materials. ChangesRoot entry removals
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The deletions implement the chosen repository cleanup without breaking the triage scripts. No actionable merge-blocking risk was identified; the change is ready for normal checks. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Linked Issues checkExplanation Issue [
✨ Finishing Touches 💡 1📝 Generate docstrings
🛠️ Fix failing CI checks 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. A rabbit checks the burrow’s rows, Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Owner
Author
|
Superseded by #1088. Its commit a805686 was cherry-picked and signed there as a5061ff. Under the fully-green rule this PR could never pass on its own: its three reds (registry sync, Repo self-tests, Hypatia Baseline) were main's own, and only #1088 cures them. #1088 in turn needed this deletion, so the two cures had to land together. The branch is kept; 🤖 Generated with Claude Code |
hyperpolymath
added a commit
that referenced
this pull request
Sep 30, 2026
…uuid-v7, map roots, canon 2.1.2, docstring calibration (#1088) Restores `standards` main to green. The reds on main and on this PR hold each other in a cycle, so every cure is in this one PR: under the fully-green rule, no smaller PR can pass CI alone. ## What each commit fixes 1. **Lock-gate staging pin bump.** The `ref:` under "Checkout standards for the lock gate" in `governance-reusable.yml` moves to `5f82b635`. `scripts/check-lock-gate-pin-freshness.sh` returns rc=1 on main and rc=0 on this branch. Each tree's own copy of the script was run; running one tree's copy against another tree reads the wrong workflow and passes vacuously. 2. **Registry `source_hash` regeneration** (#1092). #1072 and #1075 changed files under the RSR spec home without regenerating `.machine_readable/REGISTRY.a2ml`, so `build-registry.sh --check` fails. That failure reds Self-tests, and the pin guard step never runs because it comes after the failing suite. The change is one regenerated hash line. Under D231 it is a regeneration only; migrating off the generated file is a later piece of work. 3. **`uuid-v7.yml` hardening.** It adds `timeout-minutes: 10`, a `concurrency` group, and a `push` trigger bounded to `main`. These are the three unfiltered Hypatia Baseline findings on main: missing_timeout_minutes, d_burn_double_trigger, and WH006. 4. **Delete the five unmapped root entries** (D241, cherry-picked and signed from #1097). This cures the map-integrity red that woke on this PR. 5. **Canon PATCH 2.1.1 → 2.1.2.** #1041 added a KNOWN-TENSIONS row under `0-canon/constitution/` without the same-commit bump and sha256 rewrite that `canon.lock` requires. Gate A is path-filtered, so main never ran it and the drift stayed invisible until this PR woke the gate. This commit bumps the version, sets released to 2026-09-30 and the tag to `canon-v2.1.2`, rewrites the constitution hash to `be48496f…`, and adds a header note. The spine's dogfood red was a stale hypatia compile error, fixed upstream at 9d2e6de3. Re-running rsr-template-repo run 36475038466 turned it green. 6. **Fetch the docstring calibration commit by SHA** (#1099). #1073's `docstring-scan-test.sh` calibrates against `1cc72cdc80c9`, PR #1034's pre-squash head, which no clone of main can contain. Self Test on main (run 36741131926) failed on this as well as the stale registry. I read only the first failure, so my earlier claim that this PR cured every main red was wrong. The test now fetches the commit by full SHA on a miss, without `--depth` (which would make a complete clone shallow), and still fails closed if the fetch fails. The branch was rebased onto main 74d2f66 (signed) so the test file is present. Closes #1092 Closes #1094 Closes #1095 Closes #1099 ## Local verification on 6192c92 (rebased on main 74d2f66) | check | result | |---|---| | `bash scripts/run-shell-test-suite.sh` | 63 of 63 test files passed | | `check-lock-gate-pin-freshness.sh origin/main` | PASS | | `build-registry.sh --check` | clean | | `check-canon-lockstep.sh --spine rsr-template-repo@8256a6e --base origin/main` | GATE A PASSED (9 passed, 1 skipped: hypatia oracle not local) | | `check-standards-map.sh` | GATE D PASSED, 124 entries | | **positive control:** one appended byte in `KNOWN-TENSIONS.adoc`, `canon.lock` untouched | GATE A FAILED, naming `constitution` | | docstring calibration: watched failing locally (object absent, 25 passed / 1 failed), then green after the fix | files=2, functions=13, documented=0, skipped=3, coverage=0.00%; clone not shallow afterwards | #1097 is superseded by commit 4. This PR lands under the fully-green rule only when every check is green. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01QYY8Gp4v4x2J7iSNn1vZ57 --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1095.
Owner ruling D241 (2026-09-30, selector): delete all five rather than map or relocate them.
ULTRAPLAN-2026-09-24.adocULTRAPLAN-2026-09-29.adocarena-session-787/patches/ziz-drop/Git history keeps every byte, so any of them can be restored from
74d2f66.Evidence
scripts/check-standards-map.sh) on main74d2f66: rc=1,GATE D FAILED — 5 violation(s).GATE D FAILED — 1 violation(s).Left as is
scripts/triage-2026-09-24-apply.shandscripts/triage-2026-09-29-apply.shcite the two ULTRAPLANs in comments and in issue-comment text. Those scripts have already run; the citations remain valid through history.This is one of the two pre-existing main reds that #1088 is held on (ruling D240). The other is #1094.
🤖 Generated with Claude Code
https://claude.ai/code/session_01QYY8Gp4v4x2J7iSNn1vZ57