tools: PR-preservation minimal archive + Otto-207 session backfill (10 PRs)

docs/BACKLOG.md

@@ -9744,6 +9744,8 @@ systems. This track claims the space.
 
 - [ ] **Adopt `claude -w` (worktree mode) as default Claude Code launch pattern.** Maintainer 2026-04-24 Otto-241: *"from everyting i'm reading launching with -w will likely give us better results"*. Worktree-mode Claude Code runs each session in its own git worktree, preventing main-session filesystem contention when multiple Claudes share a repo. Analog of Otto-226 subagent `isolation: "worktree"` at the main-session layer. Scope: (1) test `claude -w` end-to-end on a mid-size task; (2) document the pattern in `CLAUDE.md` session-bootstrap + `docs/FACTORY-DISCIPLINE.md` active-disciplines; (3) optionally ship a wrapper `tools/claude-factory.sh` that enables `experimental.worktrees` + launches with `-w`; (4) validate via the Otto-240 same-machine-two-Claudes test — two `claude -w` sessions on the same repo should be totally isolated. Priority P3 convenience; effort S (test + doc) + S (optional wrapper). Composes with Otto-226 + Otto-240 + Otto-241. Note: Gemini CLI's built-in `-w` flag per its capability map uses `experimental.worktrees` feature gate; Claude Code's `-w` may have similar flag or be always-on.
 
+- [ ] **PR-archive pagination refactor — per-connection cursor pagination, not whole-query refetch.** Codex P2 review on PR #357 (2026-04-24): the current `paginate_top_level` function in `tools/pr-preservation/archive-pr.sh` reissues the monolithic GraphQL QUERY on every pagination step, so paging through `reviewThreads` also re-fetches the full `reviews` connection + `pullRequest` payload unnecessarily. Works correctly; wastes GraphQL rate budget on PRs with many threads. Scope: (1) split the single QUERY into per-connection GraphQL fragments — one query per `reviewThreads`, `reviews`, `comments-per-thread` — each with its own cursor; (2) compose the sub-query results client-side; (3) preserve the end-to-end archive format (no downstream schema change); (4) self-hosting smoke test stays green. Priority P2 research-grade; effort S. Composes with the PR-preservation Otto-207 backfill + the git-native PR-conversation preservation P2 row above.
+
 ## P2 — Rule-Zero axiomatic substrate (round-35 round-36 thread)
 
 - [ ] **Self-directed wellness / life-coach AI product — measure,

docs/pr-discussions/PR-0336-docs-ksk-naming-definition-doc-canonical-expansion-locked-ot.md

@@ -0,0 +1,250 @@
+---
+pr_number: 336
+title: "docs: KSK naming definition doc \u2014 canonical expansion locked (Otto-142..145)"
+author: AceHack
+state: OPEN
+created_at: 2026-04-24T08:38:34Z
+head_ref: docs/ksk-naming-definition-otto-142-145
+base_ref: main
+archived_at: 2026-04-24T11:22:13Z
+archive_tool: tools/pr-preservation/archive-pr.sh
+---
+
+# PR #336: docs: KSK naming definition doc — canonical expansion locked (Otto-142..145)
+
+## PR description
+
+## Summary
+
+Authoritative definition of **KSK = Kinetic Safeguard Kernel** at `docs/definitions/KSK.md`, plus a pointer entry in `docs/GLOSSARY.md`.
+
+Resolves Amara 16th-ferry §4 (KSK naming stabilization) + 17th-ferry correction #7. Authority: Aaron Otto-140 (rewrite approved; Max-coordination gate lifted) and Otto-142..145 (canonical expansion self-corrected from transient Otto-141 "SDK" typo to the Kernel form matching Amara's original).
+
+## Key distinction
+
+"Kernel" here is **safety-kernel / security-kernel** sense (Anderson 1972 reference-monitor, Saltzer-Schroeder complete-mediation, aviation safety-kernel). **NOT** an OS-kernel (not ring 0, not Linux / Windows / BSD kernel-mode). The doc's lead paragraph makes this disambiguation up-front because readers coming from OS-kernel contexts would otherwise misinterpret.
+
+## Doc content
+
+- Canonical definition + mechanism set (k1/k2/k3 capability tiers, revocable budgets, multi-party consent quorum, BLAKE3-hashed signed receipts, traffic-light outputs, optional anchoring)
+- "Inspired by..." (DNSSEC KSK, DNSCrypt, security kernels, aviation safety kernels, microkernel OS)
+- "NOT identical to..." (OS kernel, DNSSEC KSK, generic root-of-trust, blockchain, policy engine, authentication system)
+- Attribution + provenance (Aaron + Amara concept owners; Max initial-starting-point in LFG/lucent-ksk)
+- Zeta / Aurora / lucent-ksk relationship triangle
+- Cross-references to 5 prior courier ferries (5th / 7th / 12th / 14th / 16th / 17th)
+
+## Test plan
+
+- [x] `docs/definitions/` created as new directory (first entry).
+- [x] Glossary pointer added under "## Meta-algorithms and factory-native coinages" section.
+- [ ] Markdownlint clean on CI.
+- [ ] Future KSK graduations update this doc with `src/Core/` cross-references.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-04-24T08:42:26Z)
+
+## Pull request overview
+
+Adds a canonical documentation entry defining **KSK = Kinetic Safeguard Kernel**, and wires it into the repo glossary so the expansion and intended “kernel” meaning are stable and discoverable.
+
+**Changes:**
+- Introduces `docs/definitions/KSK.md` as the authoritative KSK definition and disambiguation doc.
+- Adds a new `KSK (Kinetic Safeguard Kernel)` glossary entry pointing to the definition doc.
+
+### Reviewed changes
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
+
+| File | Description |
+| ---- | ----------- |
+| docs/definitions/KSK.md | New definition doc describing the KSK concept, disambiguations, and cross-references. |
+| docs/GLOSSARY.md | Adds a glossary entry that summarizes KSK and links to the authoritative definition doc. |
+
+### COMMENTED — @AceHack (2026-04-24T11:18:56Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-04-24T11:18:58Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-04-24T11:19:00Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-04-24T11:19:02Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-04-24T11:19:04Z)
+
+_(no body)_
+
+### COMMENTED — @AceHack (2026-04-24T11:19:05Z)
+
+_(no body)_
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-04-24T11:22:11Z)
+
+## Pull request overview
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
+
+## Review threads
+
+### Thread 1: docs/GLOSSARY.md:819 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T08:42:24Z):
+
+This glossary entry references `LFG/lucent-ksk` as an in-repo path, but there is no `LFG/` directory here. Please clarify that this is an external repo (or replace with a valid in-repo reference) to avoid dead navigation for readers.
+```suggestion
+starting-point code: Max in the external repo
+`LFG/lucent-ksk`. Canonical expansion ratified 2026-04-24
+(Aaron Otto-142..145, after earlier Amara 5th / 7th / 16th
+ferry phrasing). Authoritative source: `docs/definitions/KSK.md`.
+```
+
+**@AceHack** (2026-04-24T11:18:56Z):
+
+Fixed in 364be82. Rewrote the GLOSSARY KSK entry's initial-starting-point reference to explicitly mark `Lucent-Financial-Group/lucent-ksk` as an external repository with URL, clarifying "not a local LFG/ directory in this repo." No more dead navigation.
+
+### Thread 2: docs/definitions/KSK.md:158 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T08:42:24Z):
+
+Operational standing rules forbid direct contributor/agent name attribution in docs; this section uses named individuals. Please rewrite to use role references (e.g., “human maintainer”, “external collaborator”) and move any required provenance/credit to allowed locations (e.g., `memory/persona/**` or `docs/BACKLOG.md`). Also update the new glossary entry to match the same no-names convention.
+```suggestion
+- The **human maintainer** and an **external AI
+  collaborator** are the concept owners of KSK-as-safety-
+  kernel for Zeta. The k1/k2/k3 + revocable-budget +
+  multi-party-consent + signed-receipt + traffic-light +
+  optional-anchoring design was articulated across courier
+  ferries documented under `docs/aurora/2026-04-23-*` and
+  `docs/aurora/2026-04-24-*`. If named provenance is needed,
+  keep it in allowed locations such as `memory/persona/**`
+  or `docs/BACKLOG.md`, not in this definition file.
+- An **external collaborator** committed the **initial
+  starting point** of the KSK code under `LFG/lucent-ksk`
+  under the human maintainer's direction. That starting
+  point remains fully rewritable; it is provenance for the
+  initial substrate, not a locked scope. See
+  `memory/feedback_ksk_naming_unblocked_aaron_
+  directed_rewrite_authority_max_initial_starting_point_
+  2026_04_24.md`.
+- **Naming stabilization** was raised in the relevant
+  courier-ferry review and resolved in the same review flow
+  after a brief transient "SDK" typo. Canonical expansion:
+  Kinetic Safeguard **Kernel**.
+```
+
+**@AceHack** (2026-04-24T11:18:58Z):
+
+Fixed in 364be82. Attribution section rewritten to use role references ("the human maintainer", "an external AI collaborator", "a trusted external contributor") instead of named individuals. Direct names preserved only in audit-trail surfaces per factory name-attribution policy (commit messages, tick-history, session memory).
+
+### Thread 3: docs/definitions/KSK.md:153 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T08:42:25Z):
+
+This doc links to `memory/feedback_ksk_naming_unblocked_aaron_directed_rewrite_authority_max_initial_starting_point_2026_04_24.md`, but that file path doesn’t exist in the repository. Please either add the referenced file, or change the reference to an existing in-repo source (or remove it if it’s intentionally out-of-repo).
+```suggestion
+  scope.
+```
+
+**@AceHack** (2026-04-24T11:19:00Z):
+
+Fixed in 364be82. Removed the memory/feedback_ksk_naming_unblocked_* path reference entirely; the factual substance (rewrite-authority context) was restated in role-based prose without creating a broken-link-from-outside dependency. Same pattern applied to #354 thread 59XfPF earlier.
+
+### Thread 4: docs/definitions/KSK.md:180 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T08:42:25Z):
+
+`LFG/lucent-ksk` is referenced as if it were an in-repo path, but there is no `LFG/` directory in this repository. Clarify that this is an external repository (and link to it if appropriate), or adjust the wording so readers don’t interpret it as a local path they can navigate to.
+```suggestion
+- **LFG/lucent-ksk** — the external `LFG/lucent-ksk`
+  repository, where Max's initial KSK starting-point code
+  lives. It may evolve independently; Zeta re-implements
+  KSK as an in-substrate module where that integration is
+  tighter. Cross-repo decisions follow Otto-90
+  (Aaron+Max-not-coordination-gates) and Otto-140 (KSK
+  rewrite authority resides with Aaron + Amara + Otto).
+```
+
+**@AceHack** (2026-04-24T11:19:02Z):
+
+Fixed in 364be82. Same fix as GLOSSARY thread 59VynF applied here: `Lucent-Financial-Group/lucent-ksk` marked as external repo with URL, plus explicit "separate repository" framing in the Relationship-to-Zeta-Aurora-lucent-ksk section.
+
+### Thread 5: docs/definitions/KSK.md:207 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T08:42:25Z):
+
+The cross-reference list includes several `docs/aurora/...` paths/patterns that don’t exist in the current tree (e.g., no `2026-04-23-amara-5th-ferry-*`, no `2026-04-24-...-12th/14th/...`, and no `...-16th-ferry.md`). Also, glob patterns in markdown aren’t navigable links. Please update these bullets to point at concrete existing files (or to `docs/aurora/README.md` entries) so the references remain clickable and accurate.
+```suggestion
+- `docs/aurora/README.md` — see the Aurora index entry for the
+  5th ferry: Aurora + KSK integration; first articulation of
+  k1/k2/k3, revocable budgets, multi-party consent,
+  signed receipts, traffic-light, and optional anchoring.
+- `docs/aurora/README.md` — see the Aurora index entry for the
+  7th ferry: Aurora-aligned KSK design research; formal
+  authorization rule `Authorize(a, t) = ¬RedLine ∧
+  BudgetActive ∧ ScopeAllowed ∧ QuorumSatisfied ∧ OraclePass`,
+  BLAKE3 receipt hashing, and the KSK-as-Zeta-module proposal.
+- `docs/aurora/README.md` — see the Aurora index entry for the
+  12th ferry: executive summary, KSK, integrity detector, and
+  integration plan.
+- `docs/aurora/README.md` — see the Aurora index entry for the
+  14th ferry: expanded cartel-detection context for KSK's
+  integrity-layer companion.
+- `docs/aurora/README.md` — see the Aurora index entry for the
+  16th ferry: KSK naming ambiguity identified and
+  stabilization recommended.
+- `docs/aurora/README.md` — see the Aurora index entry for the
+  17th ferry: the correction sequence that led to this doc.
+```
+
+**@AceHack** (2026-04-24T11:19:04Z):
+
+Fixed in 364be82. Cross-reference list rewritten to enumerate only verified in-repo references (6th / 7th / 17th / 19th ferries that actually exist on origin/main). The 5th / 12th / 14th / 16th ferries that were referenced don't exist as standalone `docs/aurora/` files; content archived in ROUND-HISTORY + session memory. Glob patterns removed (markdown doesn't navigate them). Explicit note added about when the list would be updated if those earlier ferries graduate to standalone docs.
+
+### Thread 6: docs/definitions/KSK.md:191 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T08:42:25Z):
+
+This continuation line starts with a literal `+`, which markdownlint treats as a new nested list marker (and the repo convention explicitly forbids `+` at the start of a wrapped continuation line). Please reword so the line continues without a leading `+` (e.g., “and traffic-light …” or move the `+` to the previous line’s end).
+```suggestion
+  and traffic-light + optional-anchoring.
+```
+
+**@AceHack** (2026-04-24T11:19:05Z):
+
+Fixed in 364be82. The literal `+` continuation line was in the old Attribution section; the Attribution rewrite (thread 59Vyns) replaced that section with role-based prose that doesn't use `+` continuations. Markdownlint verified clean locally (`markdownlint-cli2 docs/definitions/KSK.md` exit 0).
+
+### Thread 7: docs/definitions/KSK.md:219 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T11:22:10Z):
+
+P1: This claims the 5th/12th/14th/16th ferry content is “archived in `docs/ROUND-HISTORY.md` tick rows”, but `docs/ROUND-HISTORY.md` doesn’t contain tick rows or any “ferry” references (it reads as round-level narrative). Please either point to the actual in-repo artifact(s) that preserve those ferry contents, or remove the `ROUND-HISTORY.md`/tick-rows claim so readers aren’t sent to a dead end.
+```suggestion
+16th) have not landed as separate `docs/aurora/` files yet.
+When those ferries graduate to their own `docs/aurora/`
+files, this cross-reference list updates at that time.
+```
+
+### Thread 8: docs/definitions/KSK.md:151 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-04-24T11:22:11Z):
+
+P1: The parenthetical here says the doc’s “ferry references below” are 5th/7th/12th/14th/16th/17th, but the Cross-references section actually lists 6th, 7th, 17th, and 19th as the verified in-repo sources. Please update this list (or reword the sentence) so it matches the references that follow and doesn’t imply missing/incorrect citations.
+```suggestion
+  2026-04-23 and 2026-04-24 — the 6th / 7th / 17th / 19th
+  ferry references below are the verified in-repo topical
+  labels for those sources).
+```
+
+## General comments
+
+### @chatgpt-codex-connector (2026-04-24T08:38:40Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).