Skip to content

docs: record CSRG-U5 as merged - #31

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

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

Conversation

@novelKR

@novelKR novelKR commented Oct 11, 2026 •

Copy link
Copy Markdown
Owner

Records CodeSpace's CSRG-U5 as merged and verified in DevGuard's ledger. It is bookkeeping, the same kind of change as #29, and is not part of U5's definition of done.

Why

The owner approved merging CSRG-U5 at its exact head on 2026-10-11. It merged as novelKR/CodeSpace#92: merge commit 0c21a7f, head 7b65c76, and the merge commit has the head's tree. The PR's CI on 7b65c76 passed every job. The post-merge CI is also green: CI run 38159467078 and documentation run 38159467733. U5 changes no pin, so CodeSpace still links this repository at 6e7e065. The ledger still records U5 as active (#30).

Changes

File Change
milestones.json CSRG-U5 is merged-verified, the value #29 gave U4. units.as_of stays 2026-10-11. U6 stays not-started. CS-RG stays in-progress, qualification not-run
docs/milestones.md The CS-RG row lists #92 and says U1–U5 are merged and verified. The dated note under the suspension notice says the same
AGENTS.md The dated current-state note says U5 is merged
docs/planning/README.md, docs/ko/planning/README.md The dated current-state note says U5 is merged
docs/planning/milestones/CS-RG.md, docs/ko/planning/milestones/CS-RG.md The dated current-state note says U5 is merged. It also says that until a separate Codex change lands, U5 observes PTY executions only after Codex reaps them, as the owner chose on 2026-10-11

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. U6, qualification, has not started.
  • 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 6bc7654, based on main at 668750b:

  • 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,protocol-analysis --diff-base origin/main: all four 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 as active again, which would be inaccurate now that U5 is merged.

CSRG-U5 merged in CodeSpace on 2026-10-11 as novelKR/CodeSpace#92
(0c21a7f, at head 7b65c76, whose CI passed in full; the merge commit has
that head's tree). Record U5 as merged-verified in 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. The CS-RG plan also notes that until a separate Codex change
lands, U5 observes PTY executions only after Codex reaps them, as the
owner chose on 2026-10-11. 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>
@novelKR
novelKR merged commit cd0681c into main Oct 11, 2026
4 checks passed
novelKR pushed a commit that referenced this pull request Oct 12, 2026
The owner directed CSRG-U6 to start on 2026-10-12, after CSRG-U5 merged
in CodeSpace as novelKR/CodeSpace#92 (0c21a7f), recorded here by #31,
and governed PTY executions came to be observed before the reap through
novelKR/CodeSpace#93 and novelKR/CodeSpace#95, recorded by #32. Record
U6 as active with the units dated 2026-10-12, 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,
DG-1's qualified release is unchanged, 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