Skip to content

docs: record CSRG-U4 as the active unit - #28

Merged
novelKR merged 1 commit into
mainfrom
claude/project-thread-af6ntg
Oct 8, 2026
Merged

novelKR merged 1 commit into
mainfrom
claude/project-thread-af6ntg

Conversation

@novelKR

@novelKR novelKR commented Oct 8, 2026 •

Copy link
Copy Markdown
Owner

Requested by Seongjae · project thread

Records CodeSpace's CSRG-U4 as the active unit in DevGuard's ledger. It is bookkeeping, the same kind of change as #22, #25 and #26, and is not part of U4's definition of done.

Why

The owner directed CSRG-U4 to start on 2026-10-08. Its predecessors are on CodeSpace main: CSRG-U3 merged as novelKR/CodeSpace#88 (d543ea5), recorded here by #26. CodeSpace then moved its DevGuard pin to 6e7e065, this repository's main after #27, as novelKR/CodeSpace#89 (e0610c4). The post-merge CI of #89 is green: CI run 37769948152 and documentation run 37769949071. The ledger still records U4 as not-started.

Changes

File Change
milestones.json CSRG-U4 is active, the value #25 gave U3 when it started. units.as_of is 2026-10-08. U5 and U6 stay not-started. CS-RG stays in-progress, qualification not-run
docs/milestones.md The CS-RG row and the dated note under the suspension notice say U4 is the active unit
AGENTS.md The dated current-state note says U4 is active
docs/planning/README.md, docs/ko/planning/README.md The dated current-state note says U4 is active
docs/planning/milestones/CS-RG.md, docs/ko/planning/milestones/CS-RG.md The dated current-state note says U4 is the active unit

Korean counterparts reviewed; planning-readme and planning-milestones-cs-rg hashes recorded with scripts/check_docs.py record.

What does not change

  • CS-RG is not marked implemented or qualified. U4 is not recorded as merged: that waits for its CodeSpace PR and the owner's exact-head approval.
  • The suspension of the CSRG-C00–C09 plan stays in force, and no historical text is rewritten: each change is the existing dated note or the living status row.
  • No product code, contract, design revision, pin, dependency, CI policy or test changes. The DG-1 qualified release stays 0.1.0-5daee5d-b3fa569e.

Verification

At f7d937c, based on main at 6e7e065:

  • python3 scripts/ci_plan.py --base origin/main --head HEAD: profile affected, 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 U4 as not-started again, which would be inaccurate while U4 is under way.

The owner directed CSRG-U4 to start on 2026-10-08, after CSRG-U3 merged in
CodeSpace as novelKR/CodeSpace#88 (d543ea5) and CodeSpace moved its DevGuard
pin to 6e7e065 as novelKR/CodeSpace#89 (e0610c4), both with their post-merge
CI green. Record U4 as active with the units dated 2026-10-08, keep U5 and 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants