Repository navigation
docs: record governed PTY observation before the reap - #32
Merged
Merged
Conversation
…n note) CodeSpace merged novelKR/CodeSpace#95 on 2026-10-12 (main 181a020): the recorded patch on the pinned Codex (novelKR/CodeSpace#93) now gives a governed PTY root the same observation before the reap as a governed pipe root, completing the PTY option the owner chose on 2026-10-11. The CS-RG plan's dated current-state note said that until a separate Codex change lands, U5 observes PTY executions only after Codex reaps them. Date the note 2026-10-12 and say what holds now, English and Korean. The units ledger is unchanged: U5 stays merged-verified, U6 not started, CS-RG in-progress with qualification not-run. Korean counterpart reviewed; planning-milestones-cs-rg hashes recorded. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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>
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
2 participants
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.
Updates the CS-RG plan's dated note now that governed PTY executions are observed before the reap. It is bookkeeping, the same kind of change as #31.
Why
#31 recorded CSRG-U5 as merged and noted that, until a separate Codex change lands, U5 observes PTY executions only after Codex reaps them, as the owner chose on 2026-10-11 (option 3). That change has now landed in CodeSpace, each PR merged at its exact head on the owner's approval:
rust-v0.154.0pina75d0303d051fa, 2026-10-11634a19f181a020, 2026-10-12novelKR/CodeSpace#95's CI on
634a19fpassed all 17 jobs. Post-merge on CodeSpacemainat181a020: CI run 38205025558 passed all 17 jobs, and documentation run 38205025983 passed. Neither PR changes a pin, so CodeSpace still links this repository at6e7e065; novelKR/CodeSpace#95's tests use this repository's fixture authority as it is at that commit (pause_reconciler,hold_authority).Changes
docs/planning/milestones/CS-RG.md,docs/ko/planning/milestones/CS-RG.mddocs/translations.jsonplanning-milestones-cs-rghashes recorded withscripts/check_docs.py recordafter reviewing the Korean counterpartWhat does not change
milestones.json: U5 staysmerged-verified, U6not-started, CS-RGin-progresswith qualificationnot-run.AGENTS.md,docs/milestones.md, the planning index) say nothing about PTY observation and stay as docs: record CSRG-U5 as merged #31 left them.0.1.0-5daee5d-b3fa569e.Verification
At
0c43653, based onmainatcd0681c:python3 scripts/ci_plan.py --base origin/main --head HEAD: profileaffected, 3 normative paths, stages whitespace 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 note would then say again that PTY executions are observed only after Codex's reap, which is no longer true.