docs(handoff): record the close of the 2026-09-27 session

[novelKR]

Summary

Adds docs/handoff/2026-09-27-session-close.md, a dated handoff that lets another agent or a reviewer continue the work of the 2026-09-27 session from GitHub alone. Documentation only, one new file. It is a record, not a design decision: it approves no architecture, starts no work unit, changes no ledger status and authorizes no merge. The CS-RG implementation hold stays in force.

Tracked by #14 (living tracker). CodeSpace counterpart: tracker novelKR/CodeSpace#76 and note PR novelKR/CodeSpace#77.

Why

The session is closing. Its results were split between four open PRs and records that exist only in the git-ignored local evidence directory, and the CS-RG analysis in #13 uses terms (N1.x, N2.x, E-1 to E-10, K1 to K9, P1 to P12) whose definitions were local only. This file gathers what a cold start needs and points to the rest.

What the file contains

1. Picking up the work: an ordered start procedure and a map of where each kind of information lives in both repositories.
2. The governing instruction (CS-DG-REASSESS-2026-09-27 and its revisions), the directive's gates G0 to G5 with their state, the boundaries, and the identifiers.
3. State at close: both main heads, the Codex pin, worktrees and kept branches, every open PR with its exact head and CI runs, and a timeline of the day with evidence.
4. Definitions of the terms used by the records: the N1 and N2 constraints, the thin-adapter scope, the directions excluded before comparison (E-1 to E-10), Codex capabilities per version (K1 to K9), CodeSpace execution paths (P1 to P12, W1 to W5), and how local finding IDs map to the public findings.
5. Open decisions: the merge track and the four architecture choices, plus the principles already settled so they are not asked again.
6. Known flaky tests (DG1-C03 stuck probe, DG1-C06 survivor race, CodeSpace ETXTBSY suspected and not yet confirmed fixed, CodeSpace hashFiles) and unresolved issues (D6, reap-first operability, OX-01 to OX-03, and others).
7. The local-only evidence index with manifest digests, and the bounded diagnostics that are recorded but not run.
8. Procedures: merging, reading CI, preserving evidence, delegated work, environment.

Revision history in this PR

1. Initial record.
2. Revised after an independent, context-free review of the published artifacts. Every point was checked against the sources first. The revision:
   • puts the PR numbers in the state tables;
   • flags that the earlier handoffs' "start CSRG-C00" step is withdrawn;
   • defines the remaining IDs (CS-RG, DG1-Cxx, DG-LINUX, DGP/CSP units, ADR-006, D1, Suspect, runner modes);
   • states where owner approvals come from;
   • gives plain gh equivalents for the local-only evidence collector;
   • states the bounded-diagnostic conditions and BD-1's path forward;
   • makes the approval list match Handoff: CS-RG hold, boundary revalidation and pending owner approvals (2026-09-27) #14;
   • links the CodeSpace note at a fixed revision;
   • marks the manifest digests as dated values.

What did not change

No other file. No unit, ID, status value or work count (48 units, 25 groups). milestones.json, product code, pins, dependencies, CI and the hold notices of #12 are unchanged. The earlier handoffs stay as the records of their moments.

Verification

• python3 scripts/check_docs.py: passed (17 reviewed pairs, 48 work units, 25 logical PR groups).
• git diff --check: clean. No local absolute paths and no host details; English only.
• Every local manifest the file cites was re-hashed against its files before writing: 17 manifests, 2,368 entries, no mismatch, no credential-pattern hit.
• Facts are cited from records at fixed revisions: PR heads, CI run IDs, docs(handoff): record the CS-RG boundary revalidation #13's analysis at 1af1921fb72bb969b4f19ff859bd59fdb361ca55.
• Not run: scripts/validate.py, because the change is one Markdown file; this PR's CI runs the repository checks.

Merge and rollback

Merging requires the owner's explicit approval of this exact head. #11, #12, #13 and this PR share the base and touch disjoint files. Merging one advances main but does not change the others' heads; under the owner's merge rule each remaining PR is re-verified against the moved base, and any update of its head needs a new approval. Rollback: revert the commit.

Related

• Handoff: CS-RG hold, boundary revalidation and pending owner approvals (2026-09-27) #14 (tracker), docs: suspend CS-RG implementation directives pending revalidation #12 (hold notices), docs(handoff): record the CS-RG boundary revalidation #13 (revalidation record and analysis), test(daemon): age the stuck-probe sample from the sampler's time #11 (independent test fix).
• Handoff: CS-RG managed-execution suspension (#75) and the DevGuard boundary revalidation (2026-09-27) CodeSpace#76 (CodeSpace tracker), docs: mark the planned CS-RG managed-execution design as suspended CodeSpace#75 (CodeSpace hold notices), docs: record the CS-RG suspension handoff note CodeSpace#77 (CodeSpace note).