fix(audit): honor TAG override in rolling prune script
No architecture/protocol flow changes; diagram files reviewed and no updates were needed for this package-script wiring fix.
This commit is contained in:
@@ -417,6 +417,17 @@
|
||||
],
|
||||
"test_status": "pnpm audit:phase0-baseline:live:refresh:drift:rolling:prune + pnpm audit:phase0-baseline:live:prune + pnpm test:run src/audit/phase0BaselineArtifactRetention.test.ts + pnpm typecheck passing"
|
||||
},
|
||||
"phase0-live-baseline-rolling-prune-tag-override-fix": {
|
||||
"status": "completed",
|
||||
"date": "2026-02-27",
|
||||
"updated": "2026-02-27",
|
||||
"summary": "Fixed `pnpm audit:phase0-baseline:live:refresh:drift:rolling:prune` to honor caller-provided `TAG` values (defaulting only when unset), so rolling refresh, drift checks, and prune reports consistently share one externally overridable tag.",
|
||||
"files_modified": [
|
||||
"package.json",
|
||||
"docs/plans/state.json"
|
||||
],
|
||||
"test_status": "pnpm typecheck passing"
|
||||
},
|
||||
"phase0-instrumentation-ticket-checklist": {
|
||||
"status": "completed",
|
||||
"date": "2026-02-25",
|
||||
|
||||
Reference in New Issue
Block a user