docs(config-audit): cache-telemetry recipe + --with-telemetry-recipe flag (v5 M7)
This commit is contained in:
parent
e1e23edbcd
commit
df6e012903
4 changed files with 152 additions and 1 deletions
|
|
@ -29,6 +29,7 @@ Split `$ARGUMENTS` into a path and flags. Path is the first non-flag argument. D
|
|||
|
||||
- `--global` — also include the user-level `~/.claude/` cascade
|
||||
- `--json` — emit raw JSON instead of rendered tables (power-user mode)
|
||||
- `--with-telemetry-recipe` — include `telemetry_recipe_path` in the JSON output, pointing to `knowledge/cache-telemetry-recipe.md`. Use this when you want to verify a structural fix actually improved cache hit rate (manual jq recipe, opt-in)
|
||||
|
||||
### Step 2: Run the CLI silently
|
||||
|
||||
|
|
@ -105,6 +106,7 @@ rm -f "$TMPFILE"
|
|||
- **`/config-audit posture`** — overall health scorecard (Token Efficiency is the 8th area)
|
||||
- **`/config-audit fix`** — auto-fix deterministic issues (where applicable)
|
||||
- See `knowledge/opus-4.7-patterns.md` for the full pattern catalogue (CA-TOK-001 … 003)
|
||||
- **Verify cache hit rate after a fix:** rerun with `--with-telemetry-recipe` to surface the path to `knowledge/cache-telemetry-recipe.md` — a copy-paste `jq` recipe that reads cache hit rate from your session transcripts. Opt-in. The TOK scanner is structural; this recipe is the runtime escape hatch.
|
||||
```
|
||||
|
||||
## Scope and limits
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue