From 672b847e1902285ed09700ed693fc06b1ec2f37d Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 2 Nov 2026 09:28:23 +0000 Subject: [PATCH] Refresh stale Stackwich agents on a Codex upgrade (#51) The Codex installer's step 4 only handled names taken by unrelated agents, so an upgrade left advisor/executor/verifier from an earlier revision in place: a real rev 3 -> 7 upgrade refreshed them only because the request said so explicitly. - Step 4: an agent carrying the Stackwich Codex credit comment is an earlier install. Compare it with its template (renames applied, model and model_reasoning_effort ignored); if it differs, offer an in-place refresh that keeps its name and model settings, never overwriting without asking, and offer it on every upgrade. - Step 5: check each Stackwich agent written or kept matches its template. - CHANGELOG: an Unreleased section; no policy or plugin change, so stackwich-codex-rev stays 7 and the version stays 3.6.1. Mirrors #31 for the Claude Code skill. Closes #51. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01TgCNfwCj3YG9xP3pMB6z2k --- CHANGELOG.md | 10 ++++++++++ codex/SKILL.md | 10 ++++++++++ 2 files changed, 20 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 45eafa3..d2dc918 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,16 @@ Headings are `## — `. Ports are named in the body with their own rev counters: a port tracks the parent's layer structure, not its revision number. +## Unreleased + +No policy or Claude Code plugin change; `stackwich-codex-rev` stays at 7. + +### Fixed +- The Codex installer left Stackwich agents from an earlier revision in place on an upgrade. Step 4 + now treats an agent carrying the Stackwich Codex credit as an earlier install and offers an + in-place refresh that keeps its `name` and model settings; step 5 checks it. Codex users pick it + up by copying `codex/` again. (#51) + ## 3.6.1 — confirm agents without `/agents` The policy is unchanged: `policy-rev` stays at 9 and there is nothing to re-run. Update the plugin diff --git a/codex/SKILL.md b/codex/SKILL.md index 2a5b629..e8f63d2 100644 --- a/codex/SKILL.md +++ b/codex/SKILL.md @@ -57,6 +57,14 @@ matching `name` values. If a name belongs to an unrelated agent, ask for a repla substitute it consistently in the policy block, filenames, TOML `name` values, descriptions, and in-body references. Never overwrite an unrelated agent. +An existing agent file whose header comment is the Stackwich Codex credit (`# Created by +Abhirup Banerjee (@ovhirup) as part of the Stackwich Codex architecture.`) is an earlier +install, not a collision. Compare it with its template, with any rename applied and ignoring +`model` and `model_reasoning_effort`, which users may tune. If it differs, tell the user it is +out of date and offer to replace it in place, keeping its `name` and those model settings; +never overwrite it without asking. On an upgrade, offer this even if the user doesn't mention +agents. + Write standalone TOML files from the templates to the chosen agents directory. Do not pin model names: the templates use reasoning and sandbox settings so they remain portable across accounts and future model catalogs. @@ -65,6 +73,8 @@ accounts and future model catalogs. - Confirm there is exactly one opening marker and one closing marker in the target file. - Parse every created agent TOML with Python's `tomllib` when Python 3.11+ is available. +- Every Stackwich agent written or kept matches its template apart from renames and model + settings, or the user chose to keep an older or edited one, and you say so. - Inspect the resulting diff or changed paths and run `git diff --check` for project scope when the target is in a Git repository. - Verify behavior or structure rather than re-reading a just-written file solely to confirm