@yunhozz/arc 0.2.2 → 0.2.3

package/MANIFEST.sha256

@@ -1,24 +1,37 @@
-91ca5f2044012209912e41a22b7153412e59c44418d5fceca1f0a4e01e403731  README.md
+927d47fe007447d632ceb6f4d6e936c1ea227da2d18c088185dc67260c42e412  README.md
 d41edeb8c6631dee30c67c705d4edad977aa1631627ec9de59c013f8990f4018  bin/arc-upgrade.mjs
 484d9b2002ce542c87589bb719d644d3762706aad28a6ee010024875f8cc00e2  bin/arc.mjs
-8f89783551d51f1e78ab344f7251cbe588494b365f28f722abe7643c92d9a405  claude/agents/arc-implementer.md
-839fb5731d158cbde3d11a477f412b23adffba49e6308bb1119e27ebf1c095d9  claude/agents/arc-planner.md
+b14bc5e40d8c54dd43a0087243f6e8735e2b618d95ea90bf6d70019b93ad337d  claude/agents/arc-implementer.md
+5aeaf55ef714bc3de4d9e7bdb56ca21edceefffe28cfc3e790b156a755dee1d8  claude/agents/arc-planner.md
 20a157ada8121055de9fa31f428e14d66ff04d40a8dc114c5448ae911914bb4e  claude/agents/arc-qa.md
 251d2cdc70ba3783fa03db15a0851d2410ad396e4c4e6a39ca08b1624f018425  claude/agents/arc-reviewer.md
 7710eccc6cd1049dbd67eda504d10bcd63b52d7219d53a09cf2e060d84924e7b  claude/agents/arc-scouter.md
-408c8a5dc09fb41ca9144672579b7cd31197ede0bbd87bd5cc70fd4c59a2b75f  claude/skill/SKILL.md
+533ebe426b7b60c4fbea30f15837e8c8baeb59e2cd3ddf4f30ed5b74d6383a4a  claude/skill/SKILL.md
 0bf77247b82371b3fe12a8dbe8fd2415c98d06e676d2c234b086b1f1e661b9db  claude/skill/hooks/git-policy.json
 b188c24d1339367acfe16b81be5743298e498856915e5e91b45e1a7220dad602  claude/skill/hooks/role-git-guard.mjs
 5126d44470486cb2581790b7c8d1605c4d0ee2448b725cf536ba1141eb40fa81  claude/skill/hooks/runtime-gate.mjs
+caa37aedaa352a9a324067095f303a8a4ca89fd39ca1c4e34455380d87c6de0c  claude/skill/references/arc-visual-companion.md
+6ee10d1481b8a2580d5336ff66c5c08acc9d4b251b13bbc3bfd31be99c261d43  claude/skill/references/brainstorming.md
+36d51a4723d6f0a3ce5811a0ea3b3a8424f07533947e1355f5d8cb8cce40c55e  claude/skill/references/builder-check-prompt.md
 cb4a2c2ce99621c074b85cd9dac086fdb273295d5fab14f64eeb1260733b2534  claude/skill/references/commit.md
-d8e9a8b934d876f72be23b7dd6131c77e7176afffd459750dafc310f42cd7860  claude/skill/references/coordination.md
+4bc0af1d432d3194a2a24dc0c41928545d088c1fd88f5d191be08d40707359d2  claude/skill/references/coordination.md
 b2e788737de39779706453a75fa52fab1c87482613098cd7379f0b72dd2dbd2f  claude/skill/references/git-recovery.md
 bc31a41b42c5d9db0fb218a608ff96869810c6492bd1c10f69357b21993986f1  claude/skill/references/handoff-prep.md
 e8bc06390870e677cef1f57149841eb7259c2cdc8bc33009efdb742a1577d104  claude/skill/references/handoff.md
 d6d7d6ab779d259eabee9f30a5e4421c08ee21825498ee68f4d9efe88aecd97d  claude/skill/references/limits.md
-3008b417be954f412ee3fdf0545d16e49a25beb8ed1d42924625fd5a3a4b0f5e  claude/skill/references/planning.md
-4fdc0b5c61f3de7dd92d4ac24a3acb39707ee888d7a6d6c23bd925de2b048809  claude/skill/references/verification.md
-1f476aa5d634881372d1a818d5393299de393cfbc5ce6bfde6b763aeb182d719  claude/skill/references/visual-companion.md
+5aa9bf6967ee51008d54c3b9845e478ab9b5a15ff926ff1edd6609f5a71d952a  claude/skill/references/planning.md
+6a8a4e58bd6a44b904e2e3c57de774481d909204597e1498de53f1b2fecc4c4e  claude/skill/references/scripts/frame-template.html
+43c6d69954a46ec34a2a262bcc62a9a7e83e839c739f199cb72646d397c686e3  claude/skill/references/scripts/helper.js
+763abf96510e0b892a1141397b31aa82ef900cf87ed34dde94bc8782baf4a7ca  claude/skill/references/scripts/server.cjs
+a4e5ae84275bcaacd2f84345afeabe59cf7b00ba080e123da7cc1fb226f12847  claude/skill/references/scripts/start-server.sh
+0b5ccbbd57f62d3ed88993f7940b5ee0e5c0fc9b21c550c623da4f6292e47daf  claude/skill/references/scripts/stop-server.sh
+a37e0e9697144819e1d965176ac4ae5bc3fa02d11e7812036bbcadf6dafe2400  claude/skill/references/superpowers-LICENSE
+1b34d8c945038724378bb5497e21199c9c4b1cab4ded711d44d0f7209b05c20b  claude/skill/references/superpowers-provenance.json
+64b03fce4aee5a97a93160cea8111f3ba13a17b7c001db4bd5836d67fd10705d  claude/skill/references/test-driven-development.md
+5ee0604a99713a8c54fe5eadf96ac3296e7e8c70ac43a66775502efafab0f7bf  claude/skill/references/verification.md
+6ffcb038b53254bd31debaa15e12dcd4ff24bd63d690e0b644ac6396701cf2e2  claude/skill/references/visual-companion.md
+51471c853306ff92ca8bb41dcaea05f31c0e46b03651f8f3c99754b7172f4ae1  claude/skill/references/writing-good-tests.md
+a6c67c1900064347c2a329990dd3c555657c51c3ec53b259a08aa01a2c26139a  claude/skill/references/writing-plans.md
 f9b4caf6a97d02f2bc4e2d72c2434a3c668db57961975a9cad57b1ed6a475db8  claude/skill/runtime/acceptance.mjs
 30d8cdcb9d7ab6396cab09cd9f5cf6b8003f5490fb5c0ffe9f5acffbb0534978  claude/skill/runtime/adapters/claude.mjs
 d30d118d3b42b805195ed05a3dea0ed3cf939eac811cf0228ca0b0cafeda7969  claude/skill/runtime/adapters/codex.mjs
@@ -43,23 +56,36 @@ e2e768e62a46c8ef568fc3021ac8415c4dc68fa9843b9ffb3dbbbb2e5fa3a6af  claude/skill/r
 4eb2401060533b54fa5f0335d7f4e142866892c0981aa7fa79514c209224a981  claude/skill/runtime/verification.mjs
 e4445f3582c55861907e11dfe97ea9e87c69bcc3ff773d3d583914c198f1d024  claude/skill/scripts/apply-models.py
 0c2370f827bc921cf98ab0caa91df574b52cfd3e10a49e3542c423f4b098bfcd  claude/skill/scripts/model_config.py
-9d8bd3855217d29d04fd2db756e69b406356185d134fd72f867884e48bddf2e8  codex/agents/arc-implementer.toml
-de22d6deed4206e0e77739481efeb957c5ed12d022f91af1e58d76bd6e4117ac  codex/agents/arc-planner.toml
+7f2fb9ddd6dcdfe57d346205018ed37c60071d51d9ff04a73df49102e97363f1  codex/agents/arc-implementer.toml
+cb36ad432a447fa00189d98b7d154e40a443f2e50f04f6f77e58de6ee41f33b5  codex/agents/arc-planner.toml
 3079708a5b3fbe4c15d4bc590d7ce7f08c4109ae92cd4ba97db89562fbf319a4  codex/agents/arc-qa.toml
 cdc5d82345a1cc827d5c4fb87cf239ebe430167c76f6b62f2c6f7c2c94751f70  codex/agents/arc-reviewer.toml
 81e1171a4a021a7d1d065751f5f658391d0b1cd975588449c63c96906ed3b351  codex/agents/arc-scouter.toml
-cbd2af08ddae99516c836d3f7521b972d65135ced9bfe7f41cf1ae38be7ad729  codex/skill/SKILL.md
+9aa70abca596443743817ad77e11654660917d1bdb2ffb29205a6ea87d34a794  codex/skill/SKILL.md
 019f190ee7a2ccfea059a289ca971265574b043353f89bc96e219436c9827e9e  codex/skill/hooks/runtime-gate.mjs
+5f39ba5be8cae7b78769a63aac7748006dded2b8a9991b9ac71521647b52e0f8  codex/skill/references/arc-visual-companion.md
+6ee10d1481b8a2580d5336ff66c5c08acc9d4b251b13bbc3bfd31be99c261d43  codex/skill/references/brainstorming.md
+36d51a4723d6f0a3ce5811a0ea3b3a8424f07533947e1355f5d8cb8cce40c55e  codex/skill/references/builder-check-prompt.md
 da1a566e409b21c2f610435194c6dc876a067a48d74564a94dc8d8e0dc5ed370  codex/skill/references/commit.md
-1c9fccd408296cf49b61b97f1ae4171dd54610e308971a88a669af65b143cd1b  codex/skill/references/coordination.md
+68bd352abb9d45a1f3700d84efa92236bb7697029db4a790f365b327b31106e5  codex/skill/references/coordination.md
 fedf0cff15db8fc8bc4f399a15028e11ae4b69da25aa1beeda14c7062455f756  codex/skill/references/git-recovery.md
 44025b469fc9c5028cbecaeaead85bd8b6329d1ff7872debdc7d701d4cecc81b  codex/skill/references/handoff-prep.md
 e8d05c36d1a0ec52478cf2c9392cac9881b70c0a2885945537dddd09bb353224  codex/skill/references/handoff-worktree.md
 ceeaa4e8d56ab05e71f468bae60e13933e377af7b0c4700a20f038f9b6fa8453  codex/skill/references/handoff.md
 1baf9464564bb793408eb8380a371c27b7edc21a6bd10cdfe6479d67ff3200b2  codex/skill/references/limits.md
-042a4b5534bd042f31b8b5b87c8053637aa1a6448a6b9ca251614eb6968eda96  codex/skill/references/planning.md
-a96ea4273e693f2d48d8f61b76e7ffc03e52b2986ecef17c716d59039b95737d  codex/skill/references/verification.md
-e974eba2834e4510218852a97a9f0b5cc3f12a1166aa9e67da631edfe5847323  codex/skill/references/visual-companion.md
+72556e93b662d0d7d8ea14b3ed6ede1d1d9758e5023d36066ffc8120fe4c59bc  codex/skill/references/planning.md
+6a8a4e58bd6a44b904e2e3c57de774481d909204597e1498de53f1b2fecc4c4e  codex/skill/references/scripts/frame-template.html
+43c6d69954a46ec34a2a262bcc62a9a7e83e839c739f199cb72646d397c686e3  codex/skill/references/scripts/helper.js
+763abf96510e0b892a1141397b31aa82ef900cf87ed34dde94bc8782baf4a7ca  codex/skill/references/scripts/server.cjs
+a4e5ae84275bcaacd2f84345afeabe59cf7b00ba080e123da7cc1fb226f12847  codex/skill/references/scripts/start-server.sh
+0b5ccbbd57f62d3ed88993f7940b5ee0e5c0fc9b21c550c623da4f6292e47daf  codex/skill/references/scripts/stop-server.sh
+a37e0e9697144819e1d965176ac4ae5bc3fa02d11e7812036bbcadf6dafe2400  codex/skill/references/superpowers-LICENSE
+1b34d8c945038724378bb5497e21199c9c4b1cab4ded711d44d0f7209b05c20b  codex/skill/references/superpowers-provenance.json
+64b03fce4aee5a97a93160cea8111f3ba13a17b7c001db4bd5836d67fd10705d  codex/skill/references/test-driven-development.md
+a2998ecd9daffe6610297231400a4ec165344e873713589edcc13822913a59f4  codex/skill/references/verification.md
+6ffcb038b53254bd31debaa15e12dcd4ff24bd63d690e0b644ac6396701cf2e2  codex/skill/references/visual-companion.md
+51471c853306ff92ca8bb41dcaea05f31c0e46b03651f8f3c99754b7172f4ae1  codex/skill/references/writing-good-tests.md
+a6c67c1900064347c2a329990dd3c555657c51c3ec53b259a08aa01a2c26139a  codex/skill/references/writing-plans.md
 f9b4caf6a97d02f2bc4e2d72c2434a3c668db57961975a9cad57b1ed6a475db8  codex/skill/runtime/acceptance.mjs
 30d8cdcb9d7ab6396cab09cd9f5cf6b8003f5490fb5c0ffe9f5acffbb0534978  codex/skill/runtime/adapters/claude.mjs
 d30d118d3b42b805195ed05a3dea0ed3cf939eac811cf0228ca0b0cafeda7969  codex/skill/runtime/adapters/codex.mjs
@@ -91,25 +117,25 @@ a52b6a309ad3d48a46e7b81021b9589f15ed60c388b0cbd4ff3d59f0dc898464  lib/cli/root.m
 6b9dabe794bd463cadb796004bf3613d594bfff5b798d0b1e6aaad69ca7d8a28  lib/cli/upgrade.mjs
 7719a16f6327ea3ba35206ee41c829ab967f865df9ebbd161129ca28babceb3d  lib/installer/acquisition.mjs
 66bc9a18523f70ddbb1d9a0844173d311aabd2d00d9ed5c06ca6679179ba8b06  lib/installer/global-config.mjs
-061ff82e0c655f47b872610b6ad7bde5d1941eaf7c563491a44291c86b16a349  lib/installer/install.mjs
+b8d3b0a2882ecf563f5895440bf5179735baae368b953de3d396bf1d445a37e0  lib/installer/install.mjs
 f9a0958fc424742f49ce6e2e0a49c7cf2bbe288e0cf3551d69a8a912c8f2709f  lib/installer/language.mjs
 64713575291e51971abc542df716baa99e9a530a489e92b2f8345b782e0ce4cd  lib/installer/limits.mjs
-ef416db55f3a47e706c1a2e17d39d2d5d772f8d719ce74134d7f214b9e599aef  lib/installer/manifest.mjs
-1e6667f21dfa6eb427d7447df98038bbe534345ebb57d6b401f51efe1077f1ed  lib/installer/package-references.mjs
-6bb84ba262f850a6563eb360553896ad8d7992d3c7284fd3bd8bcdb0398ea557  lib/installer/plan.mjs
+f1a255ef0217085078d837cc5cc015d0407932609e147d1785952d2b2b1bd36d  lib/installer/manifest.mjs
+27a8fdf739355351314240ffdf044b75aa1975373358cd3a4cd807683272172d  lib/installer/package-references.mjs
+0418b8817ce2567ebf926f0c3b79ce70267e47be365a7927d16b22133d6b78fe  lib/installer/plan.mjs
 5a7860583cadb57295bdac8296a6c8caa4cedf0d1823e7d08c57846ed8342ba5  lib/installer/preset.mjs
 ce12783a6389253c6e4afc1e44d56b945028e18ae6bf4d48ac368cb221c55231  lib/installer/runtime-assets.mjs
 4892d61cfe498a85f47f4a8044a831c853660365c98543eb14f4f4449b727c2f  lib/installer/runtime-config.mjs
 bfc6c13638955fbd44b6002de3a5a2de911c50ad630a44ec1bcf0e987dfd825b  lib/installer/shell-completion.mjs
 c2ab7eda987cf62bba4dce1b7eb302f350a6c67679b0aaf063b3eea11eb010c5  lib/installer/stage-cleanup.mjs
-9ddaba872ecb050698fdbd79d32a9329d61a748ed3ada62ed16ba312e4217827  lib/installer/superpowers.mjs
+e8b600650ce068b0969d845acd10eaf90a2f39d476599a4edc3fca730e4213fa  lib/installer/superpowers.mjs
 adc7696add7e9d1e61b1d4292aad078de8d7fb1156eecd512b9cc2852502cca6  lib/installer/targets.mjs
-65ba12b4786b8b8c2cd65731a96475a64d1888644e8c68825bc369d74c266ab8  lib/installer/transaction.mjs
+e489831e2e0baacb018d847df3fb702eb8b94a94db0ca21156a8721b3488d6af  lib/installer/transaction.mjs
 4ebb59a9c5a322a2dbb4d233bf01a1affa4d9991981a0f1cfd446224c535ee79  lib/installer/uninstall.mjs
 053a5046aa5cf5a03fc316fcc76ceee7787e04ef9b367cdc690852a1336ef033  lib/installer/upgrade-state.mjs
-98994d6a1f61551db803bc753d89c263565bdc6004a4204a4a2e38f353240239  lib/installer/upgrade.mjs
+c8d42ecccc46580391541ad2b3e78b758d8e3bdabbce9aa2a33e6f5c6c2f84db  lib/installer/upgrade.mjs
 2946f055d61fbe2ffd6af1c182096e01d8c1a4bfb0aa274547ce5e147dccfd19  lib/limits.mjs
-997139a32623c22a97e00612d9cc13ad8e258ac1c36742dc26f8815ebedd97f8  lib/management/operations.mjs
+85388297ce93efc0f4c7b540996375cf6993288c1d92cec2cf7a9fdca3c66a07  lib/management/operations.mjs
 fbf9ddbc30f6cfc48df3ddae7c59e8e6569f4fbe88a39c2f1a446ff72f1c7053  lib/management/status.mjs
 7362c8b0c7c4ad6f0cbb17182dd0416510567d37f7e75522f0170705b3e25d27  lib/management/update.mjs
 7ecda29faac49d98739319e3282db2f415b88474f78e85b67d1d52dd4f16167a  lib/management/workflow.mjs
@@ -124,7 +150,7 @@ ee81dee01b1623d95dda9b1d195ce2008811dfb54af3da8324a9e538238ac84e  lib/npm/proces
 79f5824a3b1b44ab0cd0e95243ed418c3fa15881927bb4d1789047b480747939  lib/policy/placement.mjs
 2fd672429cf7d4032dd3755b92de9b73ac468b12128654fd19d2eec48b5d4a2c  lib/policy/render.mjs
 c004e34b4a6a59c27031543cd7745a4b10019554a474ff8606a7e3b25c31042b  lib/policy/role-policy.json
-ac293dd90abe1cc73c708a6aa070cdabc142b2ff152d367b6aeb21f5a678aeeb  lib/release/artifact.mjs
+6816acd10da3ab8db1276d7ae2712b99e0c97111f57ba2d547a2cc5c3f9e165b  lib/release/artifact.mjs
 f9b4caf6a97d02f2bc4e2d72c2434a3c668db57961975a9cad57b1ed6a475db8  lib/runtime/acceptance.mjs
 30d8cdcb9d7ab6396cab09cd9f5cf6b8003f5490fb5c0ffe9f5acffbb0534978  lib/runtime/adapters/claude.mjs
 d30d118d3b42b805195ed05a3dea0ed3cf939eac811cf0228ca0b0cafeda7969  lib/runtime/adapters/codex.mjs
@@ -154,7 +180,7 @@ eb73238b5b4495229bb04dc02415bcf5ca32511fca86322fa198372042a6d0a2  lib/tui/setup.
 57f841f9cbbfb9c2ad3ffb5294f943602c88f6d6f939647adf1835fca44cb571  lib/tui/terminal.mjs
 ff9c33c8b3c2bd466d54ffbe4c7139ccd87c79c7de34a6c4cde92e9f6e9b42d2  native/binding.c
 205bedc1dee1a9ffa58124c6e21256a1f0cbe24f06f7c8d7cb0b99524cfab9d0  native/binding.gyp
-6e0d934a2d78d1406a0188b885b8971b59912572fc61ac16e19eeb568e145def  package.json
+d46bd42aaae3b5e674a1edb602b322915bef15d2071613593396ab03c580af84  package.json
 208c65cfde244d39ce45c3cf1b0acb128f04d21199b6b3fb5466e62db5b64af9  prebuilds/darwin-arm64/arc_safe_fs.node
 572887ac794d10a8b921d8168ea2328e31f05b45987611ff02c83114dba901af  prebuilds/darwin-x64/arc_safe_fs.node
 2bb9443021f9d873712b26321de733eddd6794c45f0bc79e2d5dc98669196635  prebuilds/index.json
@@ -165,10 +191,9 @@ aa394307b1bba68ea7146f76bec479a21f2cbeff9ea18d0786516c677a2d9fbb  scripts/check-
 de88500b49726973d1de71c0bbdf9c993e28720a5b3f28751992c023b617e04c  scripts/pack-release.mjs
 0807cadae406606fd6bf047b6607339b9f0dc763cae40da8ad692b7acdfcf0bd  scripts/postinstall.mjs
 52aa4334c02e1877822304e66959b12f98a1649a547d51b9271623221ef3573a  scripts/probe-runtime-hooks.mjs
-9c6bce1c1ab29ba75b70742e4d67c1eb0d0a0cab31e06b8abd28b057253f32d0  scripts/update-manifest.mjs
+b3a0509b8d27081e0f15b72bf9007c68d6f8654b925f4dbd7cf218d67e164ab0  scripts/update-manifest.mjs
 e99ca8fd7dbde12840097e3d68bef06037f04284474fc5006976da40758cf6bb  scripts/update-role-policy.mjs
 25904c2ebed180355a7570b10254cda6d0d5b20b8b74ff116c40957aefc47690  scripts/update-runtime-assets.mjs
-ef97ed72062ef8db48cf54f8b2a5f90ffce00f3d8f1220db3aeb5ae9b9a239e6  scripts/update-superpowers-local.sh
 f7c5d8288905ed7a6f0e99e3668a34ed43a3c1a7a3157bc883f22ec94fe22e98  scripts/update-superpowers.mjs
 40f41cc52354e02d9743c7b8d270c187856aac02cd9d7996d19b1f1089355d88  scripts/vendor-toml.mjs
 a8884682a56e563b64931a2e0b025ec50a18bc758b0de7f5a92b7890ac36c4a5  scripts/verify-release.mjs

package/README.md

@@ -28,13 +28,11 @@ Package installation provides the CLI, not the harness. Install or manage the ha
 
 ## Manage ARC
 
-Choose `Install / Update` to select Codex, Claude Code, or both, set the preset, limits, language, and global settings, then select `Execute` and press Enter. `Change Preset` edits a draft; select the focused `Apply` row and press Enter to apply it. The blank line above either action is not selectable. These actions run after validation without a review screen.
+- **Install or update:** Open `Install / Update`, choose Codex, Claude Code, or both, then set the preset, limits, language, and global settings. Select `Execute` and press Enter. To change only the preset, use `Change Preset`, select `Apply`, and press Enter. Blank lines are not selectable. ARC validates and executes these actions without a review screen.
+- **Check version:** `Check Version` shows the current and latest CLI versions. `Version Upgrade` appears only when a newer version is available. Enter applies that version and preserves installed settings. A global upgrade replaces the CLI and ends the session; an npx upgrade uses the displayed payload without replacing the global CLI. Use `Install / Update` to reconfigure the same version.
+- **Uninstall:** Choose the harness targets and global instructions, then review with `Edit` or `Cancel`. ARC removes the verified global CLI only after all selected harnesses are removed successfully, including in an npx session. A harness failure or interruption skips CLI removal. Results report partial removals and CLI failures. Unselected harnesses, user files, other npm packages, and the shared npx cache remain. To remove only the CLI, run `npm uninstall -g @yunhozz/arc`.
 
-`Check Version` shows the current and latest CLI versions. A selectable `Version Upgrade` appears only when a newer version is available. Enter applies that displayed version while preserving installed settings. Global upgrades replace the CLI and end the session; npx upgrades use the displayed payload without replacing the global CLI. Use `Install / Update` to reconfigure or refresh the same version.
-
-`Uninstall` retains target/global-instruction selection and review with `Edit` and `Cancel`. After every selected harness is removed successfully, it removes the verified global CLI, including from an npx session. Harness failures or interruptions skip CLI removal. Results distinguish partial harness removal and CLI failure. Unselected harnesses, user files, other npm packages, and shared npx cache remain. `npm uninstall -g @yunhozz/arc` removes only the CLI.
-
-The TUI requires a terminal with input and output. Its only commands are `arc`, `arc --help`, and `arc --version`; help and version also work without a TTY.
+The TUI requires terminal input and output. It supports only `arc`, `arc --help`, and `arc --version`. Help and version also work without a TTY.
 
 ## Models and language
 

package/claude/agents/arc-implementer.md

@@ -29,7 +29,7 @@ Modify only assigned files in the approved absolute workspace. You are not alone
 made by others and never revert their work. Trust Orchestrator verified branch, HEAD, approvals, document commits,
 and execution target in the brief; read the canonical handoff record only for fields marked unchanged.
 Never create or switch branches or workspaces. Do not install dependencies or expand scope without authorization.
-Before feature or behavior changes, read the brief-cited `references/superpowers/test-driven-development/SKILL.md` path and its required
+Before feature or behavior changes, read the brief-cited `references/test-driven-development.md` path and its required
 references. Write and observe a failing test, implement the smallest change, and run focused checks and the project
 suite. If TDD cannot be completed, stop before source edits and report the exact constraint and required approval to
 Orchestrator. A waiver or documentation exception requires Orchestrator recorded precise scope and justification;

package/claude/agents/arc-planner.md

@@ -28,7 +28,7 @@ Written-spec approval precedes dependent plan drafting. Return drafts only; Orch
 **Stay in your role:** ONLY draft designs, specs, and plans for Orchestrator; NEVER implement, verify, review,
 or save documents.
 
-Read the assigned evidence, brief-cited `references/superpowers/brainstorming/SKILL.md` and `references/superpowers/writing-plans/SKILL.md`, and cited references. Return a design, specification,
+Read the assigned evidence, brief-cited `references/brainstorming.md` and `references/writing-plans.md`, and cited references. Return a design, specification,
 or implementation plan draft with acceptance criteria, dependencies, risks, and verification.
 Orchestrator saves documents and requests approval. Do not edit files, implement code, run commands,
 or request user approval directly. Return visualization or execution needs that exceed these tools to Orchestrator.

package/claude/skill/SKILL.md

@@ -66,7 +66,7 @@ Do not load all references on every task.
 | [commit](references/commit.md) | Plan-task acceptance and its focused commit, resuming a task with an unclear commit result |
 | [verification](references/verification.md) | Orchestrator's verification design, QA/Reviewer assignment, correction rechecks, UI acceptance checks, risk classification, acceptance and completion; QA and Reviewer use their profiles and only brief-cited sections |
 | [git-recovery](references/git-recovery.md) | Branch collision, Git preparation failure, partial completion, metadata write denial, handoff record write denial recovery |
-| [visual-companion](references/visual-companion.md) | Visual companion offer or operation |
+| [visual-companion](references/arc-visual-companion.md) | Visual companion offer or operation |
 
 Before deciding eligibility for a small-task, plan-omission, or TDD exception, read the full conditions in [handoff](references/handoff.md), including Implementer TDD and constraints and Orchestrator direct path for small tasks; read [planning](references/planning.md) for design/plan-depth judgments and [verification](references/verification.md) for the full risk criteria before deciding eligibility. An exception name or this index alone never proves eligibility.
 

package/claude/skill/references/arc-visual-companion.md

@@ -0,0 +1,33 @@
+# Visual companion
+
+Use a visual when it materially helps design discussion or verification. Orchestrator determines the available
+capability and consent required by the actual tool. Planner returns visualization needs to Orchestrator because its
+tools are read-only file inspection; do not invent browser or shell access for it.
+Other depth 2 roles must stay within their exact allowlists and may not delegate visualization to another agent.
+
+Determine actual available browser and preview capabilities before use; do not assume the platform provides a preview tool.
+Use an available authorized local/browser workflow only when scoped by Orchestrator.
+Keep preview artifacts separate from user files, record generated side effects, preserve unrelated work,
+and report unavailable capabilities without claiming visual verification. MUST NOT expose secrets or publish a preview without authorization.
+
+Upstream guide/scripts: `<installed ARC>/references/visual-companion.md` and adjacent `scripts/`.
+ARC guide: `references/arc-visual-companion.md`; Orchestrator briefs absolute paths and retains approval/server/browser
+ownership. Missing files stop dependent work. MUST NOT use a global fallback.
+
+Run the upstream relative commands from the installed ARC `references/` directory. Orchestrator supplies that
+absolute working directory and records `screen_dir`, `state_dir`, and the complete keyed URL returned by the server
+or this session's `state/server-info`; do not guess another session path.
+
+An A/B highlight proves only the browser selection display. Check the recorded session's exact `state_dir/events`
+file separately for saved choice events. Clicking does not start a chat turn or an automatic assistant response.
+Tell the user to return to chat and send a follow-up message after selecting. On that actual next user turn, read
+the same session's events file again and combine it with the current message. Treat current chat text as primary and
+events as supplemental; current chat text wins on conflict, and missing or ambiguous feedback needs clarification.
+Do not claim event storage from a highlight or next-turn consumption from an earlier QA parse. Preserve the imported
+guide and scripts unchanged.
+
+## Follow-up Verification of Approved Visual Sources
+
+Each visual criterion requires the exact location, version, approval, and access state of the approved visual source; criterion IDs, properties, and comparison method; and evidence linking the actual output to its revision. An Implementer report does not replace fresh QA's direct comparison. Record results as pass, mismatch, or unverified and connect them to the existing proven/unmet/unverified criterion verdicts. Use pass only when accessible evidence meets the visual criterion; keep unsupported claims unverified. Missing output-to-revision linkage is unverified; a visible difference is a mismatch. Record these separately; do not infer the current branch UI state. Hold the comparison if the approved source or actual output is inaccessible or interpretation approval is missing.
+
+Static policy, generated-file, and manifest checks are structural evidence. They do not prove actual role behavior, an installed build, Claude Code CLI runtime compliance, or visual fidelity. Reports include actual changes, exclusion rationale, checks run and omitted, each criterion's evidence and limits, and platform availability. Keep baseline failures separate; progress on independent work does not relax required checks or acceptance criteria.

package/claude/skill/references/coordination.md

@@ -107,8 +107,8 @@ resolve or explicitly disposition findings before dependent implementation. This
 ### Local superpowers references
 
 Orchestrator briefs absolute paths under the selected installed ARC directory: Planner reads
-`references/superpowers/brainstorming/SKILL.md` and `references/superpowers/writing-plans/SKILL.md`;
-Implementer reads `references/superpowers/test-driven-development/SKILL.md`, including required relative references.
+`references/brainstorming.md` and `references/writing-plans.md`;
+Implementer reads `references/test-driven-development.md`, including required relative references.
 Resolve paths within each skill directory. Runtime needs no global discovery, external Skill invocation, or automatic download.
 Missing/damaged local files stop dependent work: report exact paths to Orchestrator, without global fallback.
 ARC approval, ownership, TDD exceptions and executor adapters still apply.
@@ -125,7 +125,7 @@ application, concurrency or depth enforcement.
 New sessions reload profiles; running agents retain their current settings and parent relationships. Configuration
 changes do not automatically reparent running agents or prove runtime parent behavior.
 
-For browser visualization needs read [visual-companion](visual-companion.md). Use only capabilities
+For browser visualization needs read [visual-companion](arc-visual-companion.md). Use only capabilities
 available within each role's exact allowlist; report unavailable capabilities and preserve unverified visual scope.
 
 Claude profile `model` and `effort` frontmatter values are shipped defaults; installation overwrites them with the active `models.toml` preset values.

package/claude/skill/references/planning.md

@@ -271,9 +271,9 @@ Return scope changes and unresolved decisions to the user through Orchestrator.
 
 ## Local planning references
 
-Orchestrator briefs absolute ARC paths `references/superpowers/brainstorming/SKILL.md` and
-`references/superpowers/writing-plans/SKILL.md`. Planner reads them directly; resolve relative references within each
-skill. Missing files stop the stage; report paths without global fallback. Keep ARC approval and ownership gates.
+Orchestrator briefs absolute ARC paths `references/brainstorming.md` and
+`references/writing-plans.md`. Planner reads them directly; resolve relative references from the installed
+`references/` directory. Missing files stop the stage; report paths without global fallback. Keep ARC approval and ownership gates.
 
 
 ## Instruction and Input Provenance

package/claude/skill/references/verification.md

@@ -102,7 +102,7 @@ Orchestrator accepts using verdicts, findings, rechecks, and remaining gaps, not
 disposition never turns unverified into proven. Low-risk work without QA likewise links each criterion to Orchestrator
 focused-check evidence.
 
-Read brief-cited `references/superpowers/test-driven-development/SKILL.md`; preserve ARC TDD exceptions.
+Read brief-cited `references/test-driven-development.md`; preserve ARC TDD exceptions.
 
 
 ### Final plan Reviewer correction loop

package/claude/skill/references/visual-companion.md

@@ -1,21 +1,299 @@
-# Visual companion
+# Visual Companion Guide
 
-Use a visual when it materially helps design discussion or verification. Orchestrator determines the available
-capability and consent required by the actual tool. Planner returns visualization needs to Orchestrator because its
-tools are read-only file inspection; do not invent browser or shell access for it.
-Other depth 2 roles must stay within their exact allowlists and may not delegate visualization to another agent.
+Browser-based visual brainstorming companion for showing mockups, diagrams, and options.
 
-Determine actual available browser and preview capabilities before use; do not assume the platform provides a preview tool.
-Use an available authorized local/browser workflow only when scoped by Orchestrator.
-Keep preview artifacts separate from user files, record generated side effects, preserve unrelated work,
-and report unavailable capabilities without claiming visual verification. MUST NOT expose secrets or publish a preview without authorization.
+## When to Use
 
-Upstream guide/scripts: `<installed ARC>/references/superpowers/brainstorming/visual-companion.md` and adjacent `scripts/`.
-ARC guide: `references/visual-companion.md`; Orchestrator briefs absolute paths and retains approval/server/browser
-ownership. Missing files stop dependent work. MUST NOT use a global fallback.
+Decide per-question, not per-session. The test: **would the user understand this better by seeing it than reading it?**
 
-## Follow-up Verification of Approved Visual Sources
+**Use the browser** when the content itself is visual:
 
-Each visual criterion requires the exact location, version, approval, and access state of the approved visual source; criterion IDs, properties, and comparison method; and evidence linking the actual output to its revision. An Implementer report does not replace fresh QA's direct comparison. Record results as pass, mismatch, or unverified and connect them to the existing proven/unmet/unverified criterion verdicts. Use pass only when accessible evidence meets the visual criterion; keep unsupported claims unverified. Missing output-to-revision linkage is unverified; a visible difference is a mismatch. Record these separately; do not infer the current branch UI state. Hold the comparison if the approved source or actual output is inaccessible or interpretation approval is missing.
+- **UI mockups** — wireframes, layouts, navigation structures, component designs
+- **Architecture diagrams** — system components, data flow, relationship maps
+- **Side-by-side visual comparisons** — comparing two layouts, two color schemes, two design directions
+- **Design polish** — when the question is about look and feel, spacing, visual hierarchy
+- **Spatial relationships** — state machines, flowcharts, entity relationships rendered as diagrams
 
-Static policy, generated-file, and manifest checks are structural evidence. They do not prove actual role behavior, an installed build, Claude Code CLI runtime compliance, or visual fidelity. Reports include actual changes, exclusion rationale, checks run and omitted, each criterion's evidence and limits, and platform availability. Keep baseline failures separate; progress on independent work does not relax required checks or acceptance criteria.
+**Use the terminal** when the content is text or tabular:
+
+- **Requirements and scope questions** — "what does X mean?", "which features are in scope?"
+- **Conceptual A/B/C choices** — picking between approaches described in words
+- **Tradeoff lists** — pros/cons, comparison tables
+- **Technical decisions** — API design, data modeling, architectural approach selection
+- **Clarifying questions** — anything where the answer is words, not a visual preference
+
+A question *about* a UI topic is not automatically a visual question. "What kind of wizard do you want?" is conceptual — use the terminal. "Which of these wizard layouts feels right?" is visual — use the browser.
+
+## How It Works
+
+The server watches a directory for HTML files and serves the newest one to the browser. You write HTML content to `screen_dir`, the user sees it in their browser and can click to select options. Selections are recorded to `state_dir/events` that you read on your next turn.
+
+**Content fragments vs full documents:** If your HTML file starts with `<!DOCTYPE` or `<html`, the server serves it as-is (just injects the helper script). Otherwise, the server automatically wraps your content in the frame template — adding the header, CSS theme, connection status, and all interactive infrastructure. **Write content fragments by default.** Only write full documents when you need complete control over the page.
+
+## Starting a Session
+
+```bash
+# Start AFTER the user approves the companion. --open auto-opens their browser on
+# the first screen; --project-dir persists mockups and enables same-port restart.
+bash scripts/start-server.sh --project-dir /path/to/project --open
+
+# Returns: {"type":"server-started","port":52341,
+#           "url":"http://localhost:52341/?key=ab12…",
+#           "screen_dir":"/path/to/project/.superpowers/brainstorm/12345-1706000000/content",
+#           "state_dir":"/path/to/project/.superpowers/brainstorm/12345-1706000000/state"}
+```
+
+Save `screen_dir` and `state_dir` from the response. With `--open`, the browser opens itself when you push the first screen — you don't need to ask the user to open it, but still share the URL as a fallback (headless/remote setups won't auto-open).
+
+**The URL contains a session key (`?key=…`).** The server rejects any request
+without it, so always give the user the **complete** URL from the `url` field —
+never strip the query string, and never hand out a bare `http://host:port`. The
+key gates HTTP and WebSocket access so a stray browser tab or another machine on
+the network can't read the screens or inject events. After the first load the
+browser remembers the key via a cookie, so reloads and `/files/*` assets work
+without repeating it.
+
+**Finding connection info:** The server writes its startup JSON to `$STATE_DIR/server-info`. If you launched the server in the background and didn't capture stdout, read that file to get the URL and port. When using `--project-dir`, check `<project>/.superpowers/brainstorm/` for the session directory.
+
+**Note:** Pass the project root as `--project-dir` so mockups persist in `.superpowers/brainstorm/` and survive server restarts. Without it, files go to `/tmp` and get cleaned up. Remind the user to add `.superpowers/` to `.gitignore` if it's not already there.
+
+**Launching the server by platform:**
+
+**Claude Code:**
+```bash
+# Default mode works — the script backgrounds the server itself.
+bash scripts/start-server.sh --project-dir /path/to/project --open
+```
+
+On Windows, the script auto-detects and switches to foreground mode (which blocks the tool call). Use `run_in_background: true` on the Bash tool call so the server survives across conversation turns, then read `$STATE_DIR/server-info` on the next turn to get the URL and port.
+
+**Codex:**
+```bash
+# Codex reaps background processes. The script auto-detects CODEX_CI and
+# switches to foreground mode. Run it normally — no extra flags needed.
+bash scripts/start-server.sh --project-dir /path/to/project --open
+```
+
+**Gemini CLI:**
+```bash
+# Use --foreground and set is_background: true on your shell tool call
+# so the process survives across turns
+bash scripts/start-server.sh --project-dir /path/to/project --open --foreground
+```
+
+**Copilot CLI:**
+```bash
+# Start it with Copilot CLI's non-blocking/background shell mechanism so the
+# server survives across turns. Keep --foreground so the harness, not the
+# script, owns backgrounding. The launcher is a .sh, so invoke it via bash
+# (on Windows, call Git Bash's bash.exe from the PowerShell tool).
+bash scripts/start-server.sh --project-dir /path/to/project --open --foreground
+```
+
+**Other environments:** The server must keep running in the background across conversation turns. If your environment reaps detached processes, use `--foreground` and launch the command with your platform's background execution mechanism.
+
+If the URL is unreachable from your browser (common in remote/containerized setups), bind a non-loopback host:
+
+```bash
+bash scripts/start-server.sh \
+  --project-dir /path/to/project \
+  --host 0.0.0.0 \
+  --url-host localhost
+```
+
+Use `--url-host` to control what hostname is printed in the returned URL JSON.
+
+## The Loop
+
+1. **Check server is alive**, then **write HTML** to a new file in `screen_dir`:
+   - **Required: confirm the server is alive before referring to the URL or pushing a screen.** Check that `$STATE_DIR/server-info` exists and `$STATE_DIR/server-stopped` does not. If it has shut down, restart it with `start-server.sh` using the **same `--project-dir`** — it reuses the same port, so the user's open tab reconnects on its own (it shows a "paused" overlay while the server is down) and you don't need to send a new URL. The server auto-exits after 4 hours idle (configurable with `--idle-timeout-minutes`).
+   - Use semantic filenames: `platform.html`, `visual-style.html`, `layout.html`
+   - **Never reuse filenames** — each screen gets a fresh file
+   - Use your file-creation tool — **never use cat/heredoc** (dumps noise into terminal)
+   - Server automatically serves the newest file
+
+2. **Tell user what to expect and end your turn:**
+   - Remind them of the URL (every step, not just first)
+   - Give a brief text summary of what's on screen (e.g., "Showing 3 layout options for the homepage")
+   - Ask them to respond in the terminal: "Take a look and let me know what you think. Click to select an option if you'd like."
+
+3. **On your next turn** — after the user responds in the terminal:
+   - Read `$STATE_DIR/events` if it exists — this contains the user's browser interactions (clicks, selections) as JSON lines
+   - Merge with the user's terminal text to get the full picture
+   - The terminal message is the primary feedback; `state_dir/events` provides structured interaction data
+
+4. **Iterate or advance** — if feedback changes current screen, write a new file (e.g., `layout-v2.html`). Only move to the next question when the current step is validated.
+
+5. **Unload when returning to terminal** — when the next step doesn't need the browser (e.g., a clarifying question, a tradeoff discussion), push a waiting screen to clear the stale content:
+
+   ```html
+   <!-- filename: waiting.html (or waiting-2.html, etc.) -->
+   <div style="display:flex;align-items:center;justify-content:center;min-height:60vh">
+     <p class="subtitle">Continuing in terminal...</p>
+   </div>
+   ```
+
+   This prevents the user from staring at a resolved choice while the conversation has moved on. When the next visual question comes up, push a new content file as usual.
+
+6. Repeat until done.
+
+## Writing Content Fragments
+
+Write just the content that goes inside the page. The server wraps it in the frame template automatically (header, theme CSS, connection status, and all interactive infrastructure).
+
+**Minimal example:**
+
+```html
+<h2>Which layout works better?</h2>
+<p class="subtitle">Consider readability and visual hierarchy</p>
+
+<div class="options">
+  <div class="option" data-choice="a" onclick="toggleSelect(this)">
+    <div class="letter">A</div>
+    <div class="content">
+      <h3>Single Column</h3>
+      <p>Clean, focused reading experience</p>
+    </div>
+  </div>
+  <div class="option" data-choice="b" onclick="toggleSelect(this)">
+    <div class="letter">B</div>
+    <div class="content">
+      <h3>Two Column</h3>
+      <p>Sidebar navigation with main content</p>
+    </div>
+  </div>
+</div>
+```
+
+That's it. No `<html>`, no CSS, no `<script>` tags needed. The server provides all of that.
+
+## CSS Classes Available
+
+The frame template provides these CSS classes for your content:
+
+### Options (A/B/C choices)
+
+```html
+<div class="options">
+  <div class="option" data-choice="a" onclick="toggleSelect(this)">
+    <div class="letter">A</div>
+    <div class="content">
+      <h3>Title</h3>
+      <p>Description</p>
+    </div>
+  </div>
+</div>
+```
+
+**Multi-select:** Add `data-multiselect` to the container to let users select multiple options. Each click toggles the item's selected styling.
+
+```html
+<div class="options" data-multiselect>
+  <!-- same option markup — users can select/deselect multiple -->
+</div>
+```
+
+### Cards (visual designs)
+
+```html
+<div class="cards">
+  <div class="card" data-choice="design1" onclick="toggleSelect(this)">
+    <div class="card-image"><!-- mockup content --></div>
+    <div class="card-body">
+      <h3>Name</h3>
+      <p>Description</p>
+    </div>
+  </div>
+</div>
+```
+
+### Mockup container
+
+```html
+<div class="mockup">
+  <div class="mockup-header">Preview: Dashboard Layout</div>
+  <div class="mockup-body"><!-- your mockup HTML --></div>
+</div>
+```
+
+### Split view (side-by-side)
+
+```html
+<div class="split">
+  <div class="mockup"><!-- left --></div>
+  <div class="mockup"><!-- right --></div>
+</div>
+```
+
+### Pros/Cons
+
+```html
+<div class="pros-cons">
+  <div class="pros"><h4>Pros</h4><ul><li>Benefit</li></ul></div>
+  <div class="cons"><h4>Cons</h4><ul><li>Drawback</li></ul></div>
+</div>
+```
+
+### Mock elements (wireframe building blocks)
+
+```html
+<div class="mock-nav">Logo | Home | About | Contact</div>
+<div style="display: flex;">
+  <div class="mock-sidebar">Navigation</div>
+  <div class="mock-content">Main content area</div>
+</div>
+<button class="mock-button">Action Button</button>
+<input class="mock-input" placeholder="Input field">
+<div class="placeholder">Placeholder area</div>
+```
+
+### Typography and sections
+
+- `h2` — page title
+- `h3` — section heading
+- `.subtitle` — secondary text below title
+- `.section` — content block with bottom margin
+- `.label` — small uppercase label text
+
+## Browser Events Format
+
+When the user clicks options in the browser, their interactions are recorded to `$STATE_DIR/events` (one JSON object per line). The file is cleared automatically when you push a new screen.
+
+```jsonl
+{"type":"click","choice":"a","text":"Option A - Simple Layout","timestamp":1706000101}
+{"type":"click","choice":"c","text":"Option C - Complex Grid","timestamp":1706000108}
+{"type":"click","choice":"b","text":"Option B - Hybrid","timestamp":1706000115}
+```
+
+The full event stream shows the user's exploration path — they may click multiple options before settling. The last `choice` event is typically the final selection, but the pattern of clicks can reveal hesitation or preferences worth asking about.
+
+If `$STATE_DIR/events` doesn't exist, the user didn't interact with the browser — use only their terminal text.
+
+## Design Tips
+
+- **Scale fidelity to the question** — wireframes for layout, polish for polish questions
+- **Explain the question on each page** — "Which layout feels more professional?" not just "Pick one"
+- **Iterate before advancing** — if feedback changes current screen, write a new version
+- **2-4 options max** per screen
+- **Use real content when it matters** — for a photography portfolio, use actual images (Unsplash). Placeholder content obscures design issues.
+- **Keep mockups simple** — focus on layout and structure, not pixel-perfect design
+
+## File Naming
+
+- Use semantic names: `platform.html`, `visual-style.html`, `layout.html`
+- Never reuse filenames — each screen must be a new file
+- For iterations: append version suffix like `layout-v2.html`, `layout-v3.html`
+- Server serves newest file by modification time
+
+## Cleaning Up
+
+```bash
+bash scripts/stop-server.sh $SESSION_DIR
+```
+
+If the session used `--project-dir`, mockup files persist in `.superpowers/brainstorm/` for later reference. Only `/tmp` sessions get deleted on stop.
+
+## Reference
+
+- Frame template (CSS reference): `scripts/frame-template.html`
+- Helper script (client-side): `scripts/helper.js`

package/codex/agents/arc-implementer.toml

@@ -32,7 +32,7 @@ The only exception is the bounded optional read recovery in [scope.non-escalatio
 7. Before acting, state material assumptions, uncertainties, interpretations, and tradeoffs; route unresolved decisions to Orchestrator.
 8. Choose the simplest solution meeting the approved request and criteria, without speculative features, abstractions, or configuration; edit surgically in the local style without unrelated refactoring; clean up only artifacts you caused.
 9. Turn criteria into verifiable checks; for multi-step work outline brief steps consistent with Orchestrator's plan and ownership; continue through approved checks or report the precise blocker; claim success only with evidence.
-10. Before feature, bug-fix, or behavior edits, read brief-cited `references/superpowers/test-driven-development/SKILL.md` unless waived. A waiver needs every small, low-risk criterion (narrow, understood, readily reversible, verifiable through focused checks), every plan-skip criterion (one local change; no dependent stages, cross-component shared state, lifecycle, or integration-order concerns; one focused verification path), and Orchestrator's pre-start brief record of scope, why each criterion holds, acceptance criteria, and focused verification. An explicit user or task-specific TDD request overrides it; only for qualifying tasks does it override the local reference's generic trigger (do not change that skill). Ordinary multi-step or significant/high-risk work is ineligible.
+10. Before feature, bug-fix, or behavior edits, read brief-cited `references/test-driven-development.md` unless waived. A waiver needs every small, low-risk criterion (narrow, understood, readily reversible, verifiable through focused checks), every plan-skip criterion (one local change; no dependent stages, cross-component shared state, lifecycle, or integration-order concerns; one focused verification path), and Orchestrator's pre-start brief record of scope, why each criterion holds, acceptance criteria, and focused verification. An explicit user or task-specific TDD request overrides it; only for qualifying tasks does it override the local reference's generic trigger (do not change that skill). Ordinary multi-step or significant/high-risk work is ineligible.
 11. A waiver skips only failure-first/RED-GREEN steps; focused checks, evidence and limits reporting, and risk-appropriate QA/Reviewer remain. If risk is or becomes unclear or scope expands, stop and ask Orchestrator to reclassify.
 12. Non-behavior documentation/configuration may use only a specifically authorized brief-recorded exception: run approved structural checks, state their limits, never generalize it to behavior work. MUST NOT claim TDD under a waiver or exception.
 13. If an unavoidable constraint blocks a required TDD step, stop before editing; report intended scope, exact constraint and evidence, required TDD steps, alternatives, uncertainty, and approval needed; resume only after the authorized human's decision and precise scope are recorded.