Repository navigation
docs: record CSRG-U5 as the active unit - #30
Merged
Merged
Conversation
The owner directed CSRG-U5 to start on 2026-10-09, together with merging CodeSpace's test-timing cleanup, after CSRG-U4 merged in CodeSpace as novelKR/CodeSpace#90 (3e5e3e8), recorded here by #29. The cleanup merged as novelKR/CodeSpace#91 (470069c) on 2026-10-11 and U5 started that day. Record U5 as active with the units dated 2026-10-11, keep U6 not started, and say so in AGENTS.md, the milestone table and note, the planning index and the CS-RG plan, English and Korean. CS-RG stays in-progress with qualification not-run, and the suspension of the CSRG-C00-C09 plan is unchanged. Korean counterparts reviewed; planning-readme and planning-milestones-cs-rg hashes recorded. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 11, 2026
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
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.
Records CodeSpace's CSRG-U5 as the active unit in DevGuard's ledger. It is bookkeeping, the same kind of change as #25 and #28, and is not part of U5's definition of done.
Why
The owner directed CSRG-U5 to start on 2026-10-09, together with merging CodeSpace's test-timing cleanup. Its predecessor is on CodeSpace
main: CSRG-U4 merged as novelKR/CodeSpace#90 (3e5e3e8), recorded here by #29. The cleanup merged on 2026-10-11 as novelKR/CodeSpace#91 (470069c); it changes no pin, so CodeSpace still links this repository at6e7e065. The post-merge CI of #91 is green: CI run 38150456452 and documentation run 38150456959. U5 started on the owner's Mac on 2026-10-11 (draft novelKR/CodeSpace#92). The ledger still records U5 asnot-started.Changes
milestones.jsonCSRG-U5isactive, the value #25 and #28 gave U3 and U4 when they started.units.as_ofis2026-10-11. U6 staysnot-started. CS-RG staysin-progress, qualificationnot-rundocs/milestones.mdAGENTS.mddocs/planning/README.md,docs/ko/planning/README.mddocs/planning/milestones/CS-RG.md,docs/ko/planning/milestones/CS-RG.mdKorean counterparts reviewed;
planning-readmeandplanning-milestones-cs-rghashes recorded withscripts/check_docs.py record.What does not change
0.1.0-5daee5d-b3fa569e.Verification
At
b33994d, based onmainat79cb66c:python3 scripts/ci_plan.py --base origin/main --head HEAD: profileaffected, 8 normative paths, stages whitespace, source-contract and documentation, no Rust.python3 scripts/validate.py --stages whitespace,source-contract,documentation --diff-base origin/main: all three passed.python3 scripts/check_docs.py: passed, 18 reviewed pairs, 48 work units, 25 logical PR groups.Rollback
Revert the merge (
git revert -m 1 <merge commit>). The ledger then reports U5 asnot-startedagain, which would be inaccurate while U5 is under way.