Repository navigation
Conversation
🌱 graft blast radius2 areas changed → 1 area can be affected. 4 dependent symbols, depth 2. flowchart TB
A0(("CLI Wiring<br/>4 symbols"))
classDef reached fill:#D9EDF3,stroke:#3AA7C9,stroke-width:1.5px,color:#0E313C;
class A0 reached;
Who knows this code — 2 people across 3 areas
Ownership is git history over each area's own files, weighted towards recent work (120-day half-life). Merge commits and bots are dropped, and you are dropped from your own PR. A name with no All 4 dependent symbols, grouped by areaCLI Wiring — 4 symbols in 2 files
Test signal per changed area — 2 ✓Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.
3 test suites also reference this code4 symbols, kept out of the diagram and the table so they cannot crowd out the areas a reviewer has to look at.
Open the interactive graph → — click an area to see its dependent symbols at file:line. |
Claude initialization currently replaces malformed or non-object project settings with fresh configuration. This change refuses initialization before installation writes and preserves those bytes. Host retraction now mutates only when
apply: true; omitted/false options remain previews.Adds 12 inert temporary-repository/home cases covering invalid/missing/valid settings and explicit retraction.
Validation on the same proposal in fork PR #1: full CI succeeded. Linux: 1,369 total, 1,368 passed, 1 skipped, 0 failed. Windows: 1,369 total, 1,363 passed, 6 skipped, 0 failed. Node 24 WASM regression passed. Blast radius, Blast viewer, and Cursor Bugbot completed successfully.
The fork PR was ordinarily squash-merged as
dbaf1ef3e3131cf305369b3419ad68a2faac0c66on basefe30ead39d5e6f0c921018d364da2bdbc9d4b3ad; merged source retains upstream's separate init child-loader change. Fresh merged-main CI 37071143192 remains in progress at this evidence snapshot. Fork results do not imply upstream workflow admission or maintainer approval. No native hooks, provider, package installation, npm publication or application deployment was performed locally.Tracks JCK-104: https://linear.app/jckail/issue/JCK-104/audit-and-improve-codex-agent-configuration-and-repository