pdurlej/platform

Fork 0

docs(prompts): clean stale ADR references #790

Merged

pdurlej merged 1 commit from codex/issues/prompt-adr-reference-cleanup into main

2026-06-17 23:06:43 +02:00

codex commented

2026-06-11 01:40:46 +02:00

Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

Prompt files should not send future Codex sessions toward non-existent ADR files or stale ADR numbers. These prompts are used as execution guidance, so stale references create avoidable agent wandering and bad branch names.

What changed

Corrects the Iskra family-assistant prompt from stale ADR-0006/ADR-0008 references to the merged ADR-0010 and explicit future unnumbered design references.
Corrects future slice branch names so they no longer encode stale ADR numbers.
Replaces a Hermes prompt reference to non-merged ADR-0012 with an explicit Phase 07 scope-lock draft note.

Why it changed

The related docs/spec cleanup was split away from prompts/ so safe docs and governance prompt changes can be reviewed separately. This PR contains only the prompt-side cleanup.

Files touched

prompts/codex-hermes-voice-clone-spike.md
prompts/codex-iskra-family-assistant-tier.md

Relevant context

ADR-0010 is the merged cousin role taxonomy ADR.
No durable job-bundle ADR or local-admin/privacy-tier ADR is currently merged under the stale numbers referenced by the old prompt text.
prompts/ is a full-review surface because it influences future agent execution.

Runtime evidence

No runtime mutation. Local static checks only.

Known constraints

Prompt changes are guidance changes, not implementation. This does not authorize Phase 07/08 runtime activation, schema migration, Honcho space provisioning, or any cross-repo runtime write.

Explicit out-of-scope

No runtime, schema, module, workflow, or secret changes.
No activation of family-assistant tier or Hermes voice work.
No merge before the Patchwarden workflow fix in #789, because current main still has fragile Patchwarden client dry-run behavior for governance surfaces.

Requested decision

Approve the prompt cleanup as a separate full-review PR after #789 is merged.

Merge blockers

Any remaining references to non-existent numbered ADR files in the touched prompts.
Any wording that implies future runtime activation is already approved.

Spec sources read

prompts/codex-hermes-voice-clone-spike.md — stale Hermes prompt reference.
prompts/codex-iskra-family-assistant-tier.md — stale Iskra prompt references.
decisions/0010-cousin-role-taxonomy.md — confirmed current ADR number.
docs/specs/iskra-family-assistant-tier-v0/02-plan.md and related spec files via search — confirmed future job-bundle/privacy-tier design is not a merged numbered ADR.

No closing keyword; this is queue hygiene for future agent execution.

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story Prompt files should not send future Codex sessions toward non-existent ADR files or stale ADR numbers. These prompts are used as execution guidance, so stale references create avoidable agent wandering and bad branch names. ### What changed - Corrects the Iskra family-assistant prompt from stale ADR-0006/ADR-0008 references to the merged ADR-0010 and explicit future unnumbered design references. - Corrects future slice branch names so they no longer encode stale ADR numbers. - Replaces a Hermes prompt reference to non-merged ADR-0012 with an explicit Phase 07 scope-lock draft note. ### Why it changed The related docs/spec cleanup was split away from `prompts/` so safe docs and governance prompt changes can be reviewed separately. This PR contains only the prompt-side cleanup. ### Files touched - `prompts/codex-hermes-voice-clone-spike.md` - `prompts/codex-iskra-family-assistant-tier.md` ### Relevant context - ADR-0010 is the merged cousin role taxonomy ADR. - No durable job-bundle ADR or local-admin/privacy-tier ADR is currently merged under the stale numbers referenced by the old prompt text. - `prompts/` is a full-review surface because it influences future agent execution. ### Runtime evidence No runtime mutation. Local static checks only. ### Known constraints Prompt changes are guidance changes, not implementation. This does not authorize Phase 07/08 runtime activation, schema migration, Honcho space provisioning, or any cross-repo runtime write. ### Explicit out-of-scope - No runtime, schema, module, workflow, or secret changes. - No activation of family-assistant tier or Hermes voice work. - No merge before the Patchwarden workflow fix in #789, because current `main` still has fragile Patchwarden client dry-run behavior for governance surfaces. ### Requested decision Approve the prompt cleanup as a separate full-review PR after #789 is merged. ### Merge blockers - Any remaining references to non-existent numbered ADR files in the touched prompts. - Any wording that implies future runtime activation is already approved. ## Spec sources read - `prompts/codex-hermes-voice-clone-spike.md` — stale Hermes prompt reference. - `prompts/codex-iskra-family-assistant-tier.md` — stale Iskra prompt references. - `decisions/0010-cousin-role-taxonomy.md` — confirmed current ADR number. - `docs/specs/iskra-family-assistant-tier-v0/02-plan.md` and related spec files via search — confirmed future job-bundle/privacy-tier design is not a merged numbered ADR. No closing keyword; this is queue hygiene for future agent execution.

codex added the

labels

2026-06-11 01:40:46 +02:00

codex added 1 commit

2026-06-11 01:40:46 +02:00

docs(prompts): clean stale ADR references

canary-required / collect-diff (pull_request) Successful in 4s

Details

canary-required / canary (pull_request) Successful in 13s

Details

base-is-main / guard (pull_request) Successful in 1s

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 4s

Details

patchwarden-client-dry-run / dry-run (pull_request) Failing after 18s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 1m34s

Details

4c6c54b9ec

patchwarden commented

2026-06-11 01:45:14 +02:00

First-time contributor

Patchwarden PR sanity

Status: eligible_sanity_clean
PR: 790
Commit: 4c6c54b9eca95d58769761e56e5009aedee4efc7
Security-sensitive label: missing
Authority: advisory model review plus deterministic blockers only
3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

`global-glm` / `glm-5.1:cloud`

Status: ok
Verdict: OK
Findings: none

`global-deepseek` / `deepseek-v4-pro:cloud`

Status: ok
Verdict: OK
Findings: none

`redteam` / `kimi-k2.6:cloud`

Status: ok
Verdict: OK
Findings: none

Policy notes

GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
Auto-merge is not enabled here.

# Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `790` - Commit: `4c6c54b9eca95d58769761e56e5009aedee4efc7` - Security-sensitive label: `missing` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.

codex added the

agent/codex

flow/review

labels

2026-06-11 08:14:56 +02:00

codex commented

2026-06-17 23:06:30 +02:00

Author

Collaborator

Role: executor

PR-zero verification before merge:

Checked touched prompts for stale ADR-0006, ADR-0008, ADR-0012, decisions/0006, decisions/0008, and old slice branch names -> no matches.
git diff --check origin/main...HEAD -> clean.

Prompt guidance cleanup only; no runtime mutation.

**Role:** executor PR-zero verification before merge: - Checked touched prompts for stale `ADR-0006`, `ADR-0008`, `ADR-0012`, `decisions/0006`, `decisions/0008`, and old slice branch names -> no matches. - `git diff --check origin/main...HEAD` -> clean. Prompt guidance cleanup only; no runtime mutation.