DashboardcraftRequire strict read-only, fail-closed r…

Require strict read-only, fail-closed release-workflow audits

Category: preference
Confidence: 0.80
ID: 01a07f06-99a5-78ab-8d99-2ee916d9760c
Project ID: e16af391-c497-4837-b681-c849a5514499
Cross-project: No
Recalled in other projects: 2
Source session: 00I9nKnPOSmFNVVKR
Created: 2026-09-08 03:18:54
Updated: 2026-09-08 03:18:54

Cross-Project Recalls

ProjectHitsLast recalled
opencode-lore 1 58m ago
opencode 1 9d ago

Content

When reviewing publish and CI-poller changes, perform an adversarial read-only audit of the exact uncommitted diff and relevant unchanged callers. Verify parser/documentation parity, canonical input authority, exact validation rules, byte preservation, safe cleanup, workflow triggers and gates, checkout/version requirements, JSON serialization, tests, and unrelated-diff hygiene. Treat destructive workflow paths as fail-closed: invalid or empty resolver/rewrite output must never edit issue content, and temporary files must be cleaned on every exit path. Preserve workflow_dispatch for CI-poller recovery. Report severity-ranked findings with precise file:line citations, explicit PASS/FAIL coverage for requested invariants, testing gaps, and end exactly with MERGE or DO-NOT-MERGE.

Move to: