From 26b2a3518f545c33ed3e08b617cc5de2fb8c9d37 Mon Sep 17 00:00:00 2001 From: M Waleed Kadous Date: Sat, 25 Jul 2026 02:04:20 -0700 Subject: [PATCH 1/6] docs(arch-init): make compaction a mandatory part of every state save --- .claude/skills/arch-init/SKILL.md | 16 ++++++++++++---- .codex/skills/arch-init/SKILL.md | 16 ++++++++++++---- codev-skeleton/.claude/skills/arch-init/SKILL.md | 16 ++++++++++++---- codev-skeleton/.codex/skills/arch-init/SKILL.md | 16 ++++++++++++---- 4 files changed, 48 insertions(+), 16 deletions(-) diff --git a/.claude/skills/arch-init/SKILL.md b/.claude/skills/arch-init/SKILL.md index e032a0f5f..0d20aff16 100644 --- a/.claude/skills/arch-init/SKILL.md +++ b/.claude/skills/arch-init/SKILL.md @@ -77,11 +77,19 @@ plus the most recent dated section*, so a save must leave exactly that behind: 1. **Rewrite the current-state / open-loops section in place** — overwrite it with where things actually stand now (current focus + open loops + how to - resume). Do not accumulate stale "current state" blocks. + resume). Do not accumulate stale "current state" blocks, and never leave two + sections with the same heading (a duplicated "How to resume" or "Open loops" + means you appended where you should have overwritten). **Delete resolved + loops entirely** — a closed item's record is the log entry, not a lingering + line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. -3. **Keep it to one screen (compaction discipline).** The state file is a - summary, not a transcript. When you append, prune stale dated sections so - the file stays readable at a glance. +3. **Compact — this is part of the save, not optional polish.** Every save + both adds AND removes: after writing, keep only the last 2–3 dated log + entries in full and collapse everything older into a single one-line + "(compacted — see git log of this file)" entry. Hard cap: the whole file + stays under ~80 lines / one screen. If your save pushed it over, the save + is not done — prune until it fits. The file's history lives in git; the + file itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/.codex/skills/arch-init/SKILL.md b/.codex/skills/arch-init/SKILL.md index e032a0f5f..0d20aff16 100644 --- a/.codex/skills/arch-init/SKILL.md +++ b/.codex/skills/arch-init/SKILL.md @@ -77,11 +77,19 @@ plus the most recent dated section*, so a save must leave exactly that behind: 1. **Rewrite the current-state / open-loops section in place** — overwrite it with where things actually stand now (current focus + open loops + how to - resume). Do not accumulate stale "current state" blocks. + resume). Do not accumulate stale "current state" blocks, and never leave two + sections with the same heading (a duplicated "How to resume" or "Open loops" + means you appended where you should have overwritten). **Delete resolved + loops entirely** — a closed item's record is the log entry, not a lingering + line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. -3. **Keep it to one screen (compaction discipline).** The state file is a - summary, not a transcript. When you append, prune stale dated sections so - the file stays readable at a glance. +3. **Compact — this is part of the save, not optional polish.** Every save + both adds AND removes: after writing, keep only the last 2–3 dated log + entries in full and collapse everything older into a single one-line + "(compacted — see git log of this file)" entry. Hard cap: the whole file + stays under ~80 lines / one screen. If your save pushed it over, the save + is not done — prune until it fits. The file's history lives in git; the + file itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.claude/skills/arch-init/SKILL.md b/codev-skeleton/.claude/skills/arch-init/SKILL.md index e032a0f5f..0d20aff16 100644 --- a/codev-skeleton/.claude/skills/arch-init/SKILL.md +++ b/codev-skeleton/.claude/skills/arch-init/SKILL.md @@ -77,11 +77,19 @@ plus the most recent dated section*, so a save must leave exactly that behind: 1. **Rewrite the current-state / open-loops section in place** — overwrite it with where things actually stand now (current focus + open loops + how to - resume). Do not accumulate stale "current state" blocks. + resume). Do not accumulate stale "current state" blocks, and never leave two + sections with the same heading (a duplicated "How to resume" or "Open loops" + means you appended where you should have overwritten). **Delete resolved + loops entirely** — a closed item's record is the log entry, not a lingering + line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. -3. **Keep it to one screen (compaction discipline).** The state file is a - summary, not a transcript. When you append, prune stale dated sections so - the file stays readable at a glance. +3. **Compact — this is part of the save, not optional polish.** Every save + both adds AND removes: after writing, keep only the last 2–3 dated log + entries in full and collapse everything older into a single one-line + "(compacted — see git log of this file)" entry. Hard cap: the whole file + stays under ~80 lines / one screen. If your save pushed it over, the save + is not done — prune until it fits. The file's history lives in git; the + file itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.codex/skills/arch-init/SKILL.md b/codev-skeleton/.codex/skills/arch-init/SKILL.md index e032a0f5f..0d20aff16 100644 --- a/codev-skeleton/.codex/skills/arch-init/SKILL.md +++ b/codev-skeleton/.codex/skills/arch-init/SKILL.md @@ -77,11 +77,19 @@ plus the most recent dated section*, so a save must leave exactly that behind: 1. **Rewrite the current-state / open-loops section in place** — overwrite it with where things actually stand now (current focus + open loops + how to - resume). Do not accumulate stale "current state" blocks. + resume). Do not accumulate stale "current state" blocks, and never leave two + sections with the same heading (a duplicated "How to resume" or "Open loops" + means you appended where you should have overwritten). **Delete resolved + loops entirely** — a closed item's record is the log entry, not a lingering + line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. -3. **Keep it to one screen (compaction discipline).** The state file is a - summary, not a transcript. When you append, prune stale dated sections so - the file stays readable at a glance. +3. **Compact — this is part of the save, not optional polish.** Every save + both adds AND removes: after writing, keep only the last 2–3 dated log + entries in full and collapse everything older into a single one-line + "(compacted — see git log of this file)" entry. Hard cap: the whole file + stays under ~80 lines / one screen. If your save pushed it over, the save + is not done — prune until it fits. The file's history lives in git; the + file itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the From 9000d9f558d37fa5c6a2cecc1cd3632ca7bd4a2d Mon Sep 17 00:00:00 2001 From: M Waleed Kadous Date: Sat, 25 Jul 2026 02:41:04 -0700 Subject: [PATCH 2/6] docs(roles): architect presents PRFT (Problem/Root Cause/Fix/Testing) at human decision points --- codev-skeleton/roles/architect.md | 11 +++++++++++ codev/roles/architect.md | 11 +++++++++++ 2 files changed, 22 insertions(+) diff --git a/codev-skeleton/roles/architect.md b/codev-skeleton/roles/architect.md index 750e651fc..56cac231d 100644 --- a/codev-skeleton/roles/architect.md +++ b/codev-skeleton/roles/architect.md @@ -170,6 +170,17 @@ gh pr view --json files | jq '.files[].path' # See which subsystems - **Medium**: SPIR features, new commands, refactors touching 3+ files - **High**: Protocol changes, porch state machine, Tower architecture, security model +#### Presenting the decision to the human (PRFT) + +When you bring a fix to the human for a decision — a merge word, a `pr` gate, a dev-approval — present it **unprompted** in PRFT form, whatever the risk tier: + +- **Problem** — the user-visible symptom, in a sentence or two. +- **Root Cause** — the verified mechanism. Verify it yourself; a builder's summary is evidence, not ground truth. +- **Fix** — what changed and why it's safe. +- **Testing** — the evidence: suites run, live verification, CI state. + +Keep each part tight and lead with it — don't bury the decision under process narration. The human should be able to say yes or no from your message alone, without opening the diff. + #### Step 3: Execute Review **Low risk** — no external models needed: diff --git a/codev/roles/architect.md b/codev/roles/architect.md index cd3c0709e..aa07e6fbd 100644 --- a/codev/roles/architect.md +++ b/codev/roles/architect.md @@ -170,6 +170,17 @@ gh pr view --json files | jq '.files[].path' # See which subsystems - **Medium**: SPIR features, new commands, refactors touching 3+ files - **High**: Protocol changes, porch state machine, Tower architecture, security model +#### Presenting the decision to the human (PRFT) + +When you bring a fix to the human for a decision — a merge word, a `pr` gate, a dev-approval — present it **unprompted** in PRFT form, whatever the risk tier: + +- **Problem** — the user-visible symptom, in a sentence or two. +- **Root Cause** — the verified mechanism. Verify it yourself; a builder's summary is evidence, not ground truth. +- **Fix** — what changed and why it's safe. +- **Testing** — the evidence: suites run, live verification, CI state. + +Keep each part tight and lead with it — don't bury the decision under process narration. The human should be able to say yes or no from your message alone, without opening the diff. + #### Step 3: Execute Review **Low risk** — no external models needed: From 2f95b949086171fa25a2b3452930c71d7b647ac2 Mon Sep 17 00:00:00 2001 From: M Waleed Kadous Date: Sat, 25 Jul 2026 05:44:52 -0700 Subject: [PATCH 3/6] test(spec-1134): track strengthened compaction wording in arch-init skill --- .../agent-farm/__tests__/spec-1134-arch-init-skill.test.ts | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts b/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts index e25d521f4..5e98dab47 100644 --- a/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts +++ b/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts @@ -101,10 +101,11 @@ describe('Spec 1134 — /arch-init skill ships in both trees', () => { expect(t).toMatch(/append.*dated/i); }); - it('carries compaction discipline (one screen / prune stale sections)', () => { + it('carries compaction discipline (one screen / hard cap / prune)', () => { const t = text(); expect(t).toMatch(/one screen/i); - expect(t).toMatch(/prune stale/i); + expect(t).toMatch(/hard cap/i); + expect(t).toMatch(/prune/i); }); it('carries save content guardrails (no secrets, no transcript dumps)', () => { From 2a653e5facf719ee465f982022b85028aa630b4a Mon Sep 17 00:00:00 2001 From: M Waleed Kadous Date: Sat, 25 Jul 2026 06:11:56 -0700 Subject: [PATCH 4/6] =?UTF-8?q?docs(arch-init):=20drop=20hard=20line=20cap?= =?UTF-8?q?=20=E2=80=94=20compaction=20stays=20mandatory,=20size=20is=20ju?= =?UTF-8?q?dgment=20(one=20screen=20as=20order=20of=20magnitude)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .claude/skills/arch-init/SKILL.md | 13 +++++++------ .codex/skills/arch-init/SKILL.md | 13 +++++++------ codev-skeleton/.claude/skills/arch-init/SKILL.md | 13 +++++++------ codev-skeleton/.codex/skills/arch-init/SKILL.md | 13 +++++++------ .../__tests__/spec-1134-arch-init-skill.test.ts | 4 ++-- 5 files changed, 30 insertions(+), 26 deletions(-) diff --git a/.claude/skills/arch-init/SKILL.md b/.claude/skills/arch-init/SKILL.md index 0d20aff16..8ae456b1d 100644 --- a/.claude/skills/arch-init/SKILL.md +++ b/.claude/skills/arch-init/SKILL.md @@ -84,12 +84,13 @@ plus the most recent dated section*, so a save must leave exactly that behind: line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save - both adds AND removes: after writing, keep only the last 2–3 dated log - entries in full and collapse everything older into a single one-line - "(compacted — see git log of this file)" entry. Hard cap: the whole file - stays under ~80 lines / one screen. If your save pushed it over, the save - is not done — prune until it fits. The file's history lives in git; the - file itself is only the live summary. + both adds AND removes: after writing, keep the recent dated log entries in + full and collapse older ones into a single one-line "(compacted — see git + log of this file)" entry. The file is a summary a fresh session reads at a + glance — one screen is the right order of magnitude, judged by you. If a + save has grown it past easy readability, prune as part of that save rather + than leaving it for next time. The file's history lives in git; the file + itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/.codex/skills/arch-init/SKILL.md b/.codex/skills/arch-init/SKILL.md index 0d20aff16..8ae456b1d 100644 --- a/.codex/skills/arch-init/SKILL.md +++ b/.codex/skills/arch-init/SKILL.md @@ -84,12 +84,13 @@ plus the most recent dated section*, so a save must leave exactly that behind: line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save - both adds AND removes: after writing, keep only the last 2–3 dated log - entries in full and collapse everything older into a single one-line - "(compacted — see git log of this file)" entry. Hard cap: the whole file - stays under ~80 lines / one screen. If your save pushed it over, the save - is not done — prune until it fits. The file's history lives in git; the - file itself is only the live summary. + both adds AND removes: after writing, keep the recent dated log entries in + full and collapse older ones into a single one-line "(compacted — see git + log of this file)" entry. The file is a summary a fresh session reads at a + glance — one screen is the right order of magnitude, judged by you. If a + save has grown it past easy readability, prune as part of that save rather + than leaving it for next time. The file's history lives in git; the file + itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.claude/skills/arch-init/SKILL.md b/codev-skeleton/.claude/skills/arch-init/SKILL.md index 0d20aff16..8ae456b1d 100644 --- a/codev-skeleton/.claude/skills/arch-init/SKILL.md +++ b/codev-skeleton/.claude/skills/arch-init/SKILL.md @@ -84,12 +84,13 @@ plus the most recent dated section*, so a save must leave exactly that behind: line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save - both adds AND removes: after writing, keep only the last 2–3 dated log - entries in full and collapse everything older into a single one-line - "(compacted — see git log of this file)" entry. Hard cap: the whole file - stays under ~80 lines / one screen. If your save pushed it over, the save - is not done — prune until it fits. The file's history lives in git; the - file itself is only the live summary. + both adds AND removes: after writing, keep the recent dated log entries in + full and collapse older ones into a single one-line "(compacted — see git + log of this file)" entry. The file is a summary a fresh session reads at a + glance — one screen is the right order of magnitude, judged by you. If a + save has grown it past easy readability, prune as part of that save rather + than leaving it for next time. The file's history lives in git; the file + itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.codex/skills/arch-init/SKILL.md b/codev-skeleton/.codex/skills/arch-init/SKILL.md index 0d20aff16..8ae456b1d 100644 --- a/codev-skeleton/.codex/skills/arch-init/SKILL.md +++ b/codev-skeleton/.codex/skills/arch-init/SKILL.md @@ -84,12 +84,13 @@ plus the most recent dated section*, so a save must leave exactly that behind: line in current state. 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save - both adds AND removes: after writing, keep only the last 2–3 dated log - entries in full and collapse everything older into a single one-line - "(compacted — see git log of this file)" entry. Hard cap: the whole file - stays under ~80 lines / one screen. If your save pushed it over, the save - is not done — prune until it fits. The file's history lives in git; the - file itself is only the live summary. + both adds AND removes: after writing, keep the recent dated log entries in + full and collapse older ones into a single one-line "(compacted — see git + log of this file)" entry. The file is a summary a fresh session reads at a + glance — one screen is the right order of magnitude, judged by you. If a + save has grown it past easy readability, prune as part of that save rather + than leaving it for next time. The file's history lives in git; the file + itself is only the live summary. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts b/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts index 5e98dab47..9bbc6c380 100644 --- a/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts +++ b/packages/codev/src/agent-farm/__tests__/spec-1134-arch-init-skill.test.ts @@ -101,10 +101,10 @@ describe('Spec 1134 — /arch-init skill ships in both trees', () => { expect(t).toMatch(/append.*dated/i); }); - it('carries compaction discipline (one screen / hard cap / prune)', () => { + it('carries compaction discipline (one screen / compact / prune)', () => { const t = text(); expect(t).toMatch(/one screen/i); - expect(t).toMatch(/hard cap/i); + expect(t).toMatch(/compact/i); expect(t).toMatch(/prune/i); }); From aeab94e9421a3d6239e81f380ad8f1c2178771bb Mon Sep 17 00:00:00 2001 From: M Waleed Kadous Date: Sat, 25 Jul 2026 06:13:22 -0700 Subject: [PATCH 5/6] =?UTF-8?q?docs(arch-init):=20pruned=20state=20prose?= =?UTF-8?q?=20has=20no=20git=20fallback=20=E2=80=94=20compact=20by=20point?= =?UTF-8?q?ing=20at=20durable=20artifacts?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .claude/skills/arch-init/SKILL.md | 15 +++++++++------ .codex/skills/arch-init/SKILL.md | 15 +++++++++------ codev-skeleton/.claude/skills/arch-init/SKILL.md | 15 +++++++++------ codev-skeleton/.codex/skills/arch-init/SKILL.md | 15 +++++++++------ 4 files changed, 36 insertions(+), 24 deletions(-) diff --git a/.claude/skills/arch-init/SKILL.md b/.claude/skills/arch-init/SKILL.md index 8ae456b1d..b1d47ae0c 100644 --- a/.claude/skills/arch-init/SKILL.md +++ b/.claude/skills/arch-init/SKILL.md @@ -85,12 +85,15 @@ plus the most recent dated section*, so a save must leave exactly that behind: 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save both adds AND removes: after writing, keep the recent dated log entries in - full and collapse older ones into a single one-line "(compacted — see git - log of this file)" entry. The file is a summary a fresh session reads at a - glance — one screen is the right order of magnitude, judged by you. If a - save has grown it past easy readability, prune as part of that save rather - than leaving it for next time. The file's history lives in git; the file - itself is only the live summary. + full and collapse older ones into a single one-line summary that names + where the detail lives (the closed PRs, issues, and reviews it covered). + Remember these state files are gitignored — there is no git history to + fall back on, so pruned prose is gone for good. Prune by replacing detail + with pointers to durable artifacts, never by deleting the only record of + something. The file is a summary a fresh session reads at a glance — one + screen is the right order of magnitude, judged by you. If a save has grown + it past easy readability, prune as part of that save rather than leaving + it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/.codex/skills/arch-init/SKILL.md b/.codex/skills/arch-init/SKILL.md index 8ae456b1d..b1d47ae0c 100644 --- a/.codex/skills/arch-init/SKILL.md +++ b/.codex/skills/arch-init/SKILL.md @@ -85,12 +85,15 @@ plus the most recent dated section*, so a save must leave exactly that behind: 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save both adds AND removes: after writing, keep the recent dated log entries in - full and collapse older ones into a single one-line "(compacted — see git - log of this file)" entry. The file is a summary a fresh session reads at a - glance — one screen is the right order of magnitude, judged by you. If a - save has grown it past easy readability, prune as part of that save rather - than leaving it for next time. The file's history lives in git; the file - itself is only the live summary. + full and collapse older ones into a single one-line summary that names + where the detail lives (the closed PRs, issues, and reviews it covered). + Remember these state files are gitignored — there is no git history to + fall back on, so pruned prose is gone for good. Prune by replacing detail + with pointers to durable artifacts, never by deleting the only record of + something. The file is a summary a fresh session reads at a glance — one + screen is the right order of magnitude, judged by you. If a save has grown + it past easy readability, prune as part of that save rather than leaving + it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.claude/skills/arch-init/SKILL.md b/codev-skeleton/.claude/skills/arch-init/SKILL.md index 8ae456b1d..b1d47ae0c 100644 --- a/codev-skeleton/.claude/skills/arch-init/SKILL.md +++ b/codev-skeleton/.claude/skills/arch-init/SKILL.md @@ -85,12 +85,15 @@ plus the most recent dated section*, so a save must leave exactly that behind: 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save both adds AND removes: after writing, keep the recent dated log entries in - full and collapse older ones into a single one-line "(compacted — see git - log of this file)" entry. The file is a summary a fresh session reads at a - glance — one screen is the right order of magnitude, judged by you. If a - save has grown it past easy readability, prune as part of that save rather - than leaving it for next time. The file's history lives in git; the file - itself is only the live summary. + full and collapse older ones into a single one-line summary that names + where the detail lives (the closed PRs, issues, and reviews it covered). + Remember these state files are gitignored — there is no git history to + fall back on, so pruned prose is gone for good. Prune by replacing detail + with pointers to durable artifacts, never by deleting the only record of + something. The file is a summary a fresh session reads at a glance — one + screen is the right order of magnitude, judged by you. If a save has grown + it past easy readability, prune as part of that save rather than leaving + it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.codex/skills/arch-init/SKILL.md b/codev-skeleton/.codex/skills/arch-init/SKILL.md index 8ae456b1d..b1d47ae0c 100644 --- a/codev-skeleton/.codex/skills/arch-init/SKILL.md +++ b/codev-skeleton/.codex/skills/arch-init/SKILL.md @@ -85,12 +85,15 @@ plus the most recent dated section*, so a save must leave exactly that behind: 2. **Append one short dated log entry** capturing what changed this stretch. 3. **Compact — this is part of the save, not optional polish.** Every save both adds AND removes: after writing, keep the recent dated log entries in - full and collapse older ones into a single one-line "(compacted — see git - log of this file)" entry. The file is a summary a fresh session reads at a - glance — one screen is the right order of magnitude, judged by you. If a - save has grown it past easy readability, prune as part of that save rather - than leaving it for next time. The file's history lives in git; the file - itself is only the live summary. + full and collapse older ones into a single one-line summary that names + where the detail lives (the closed PRs, issues, and reviews it covered). + Remember these state files are gitignored — there is no git history to + fall back on, so pruned prose is gone for good. Prune by replacing detail + with pointers to durable artifacts, never by deleting the only record of + something. The file is a summary a fresh session reads at a glance — one + screen is the right order of magnitude, judged by you. If a save has grown + it past easy readability, prune as part of that save rather than leaving + it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the From 29c9c9db2793595e4542d3a5baeccf05c281c32e Mon Sep 17 00:00:00 2001 From: M Waleed Kadous Date: Sat, 25 Jul 2026 06:14:54 -0700 Subject: [PATCH 6/6] docs(arch-init): fix line wrap splitting the 'one screen' phrase the spec-1134 pin asserts --- .claude/skills/arch-init/SKILL.md | 8 ++++---- .codex/skills/arch-init/SKILL.md | 8 ++++---- codev-skeleton/.claude/skills/arch-init/SKILL.md | 8 ++++---- codev-skeleton/.codex/skills/arch-init/SKILL.md | 8 ++++---- 4 files changed, 16 insertions(+), 16 deletions(-) diff --git a/.claude/skills/arch-init/SKILL.md b/.claude/skills/arch-init/SKILL.md index b1d47ae0c..b69b0b751 100644 --- a/.claude/skills/arch-init/SKILL.md +++ b/.claude/skills/arch-init/SKILL.md @@ -90,10 +90,10 @@ plus the most recent dated section*, so a save must leave exactly that behind: Remember these state files are gitignored — there is no git history to fall back on, so pruned prose is gone for good. Prune by replacing detail with pointers to durable artifacts, never by deleting the only record of - something. The file is a summary a fresh session reads at a glance — one - screen is the right order of magnitude, judged by you. If a save has grown - it past easy readability, prune as part of that save rather than leaving - it for next time. + something. The file is a summary a fresh session reads at a glance — + one screen is the right order of magnitude, judged by you. If a save has + grown it past easy readability, prune as part of that save rather than + leaving it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/.codex/skills/arch-init/SKILL.md b/.codex/skills/arch-init/SKILL.md index b1d47ae0c..b69b0b751 100644 --- a/.codex/skills/arch-init/SKILL.md +++ b/.codex/skills/arch-init/SKILL.md @@ -90,10 +90,10 @@ plus the most recent dated section*, so a save must leave exactly that behind: Remember these state files are gitignored — there is no git history to fall back on, so pruned prose is gone for good. Prune by replacing detail with pointers to durable artifacts, never by deleting the only record of - something. The file is a summary a fresh session reads at a glance — one - screen is the right order of magnitude, judged by you. If a save has grown - it past easy readability, prune as part of that save rather than leaving - it for next time. + something. The file is a summary a fresh session reads at a glance — + one screen is the right order of magnitude, judged by you. If a save has + grown it past easy readability, prune as part of that save rather than + leaving it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.claude/skills/arch-init/SKILL.md b/codev-skeleton/.claude/skills/arch-init/SKILL.md index b1d47ae0c..b69b0b751 100644 --- a/codev-skeleton/.claude/skills/arch-init/SKILL.md +++ b/codev-skeleton/.claude/skills/arch-init/SKILL.md @@ -90,10 +90,10 @@ plus the most recent dated section*, so a save must leave exactly that behind: Remember these state files are gitignored — there is no git history to fall back on, so pruned prose is gone for good. Prune by replacing detail with pointers to durable artifacts, never by deleting the only record of - something. The file is a summary a fresh session reads at a glance — one - screen is the right order of magnitude, judged by you. If a save has grown - it past easy readability, prune as part of that save rather than leaving - it for next time. + something. The file is a summary a fresh session reads at a glance — + one screen is the right order of magnitude, judged by you. If a save has + grown it past easy readability, prune as part of that save rather than + leaving it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the diff --git a/codev-skeleton/.codex/skills/arch-init/SKILL.md b/codev-skeleton/.codex/skills/arch-init/SKILL.md index b1d47ae0c..b69b0b751 100644 --- a/codev-skeleton/.codex/skills/arch-init/SKILL.md +++ b/codev-skeleton/.codex/skills/arch-init/SKILL.md @@ -90,10 +90,10 @@ plus the most recent dated section*, so a save must leave exactly that behind: Remember these state files are gitignored — there is no git history to fall back on, so pruned prose is gone for good. Prune by replacing detail with pointers to durable artifacts, never by deleting the only record of - something. The file is a summary a fresh session reads at a glance — one - screen is the right order of magnitude, judged by you. If a save has grown - it past easy readability, prune as part of that save rather than leaving - it for next time. + something. The file is a summary a fresh session reads at a glance — + one screen is the right order of magnitude, judged by you. If a save has + grown it past easy readability, prune as part of that save rather than + leaving it for next time. **Content guardrails.** No secrets (tokens, keys, credentials). No transcript dumps or raw tool output. Include only: current focus, open loops, and the