chore: prompt files 0o600 + record bulletproof certification verdict#69
Merged
Conversation
Closes the two LOW findings from the certification audit and records the audit verdict in CLAUDE.md and the Obsidian launch playbook. 1. Prompt file perms 0o644 → 0o600 (LOW). internal/runtime/registry.go (CLIRuntime.BuildCommand) and internal/runtime/tmux_runner.go (Runner.Run) wrote agent prompt files at 0o644 — readable by every user on a shared dispatch host. Prompt content carries goal text + system context + WAVE_CONTEXT + acceptance criteria, any of which may include DSNs or other sensitive context. Tightened to 0o600 (and the parent .vxd-prompts dir to 0o700). 2. YAML pipe/semicolon caveat documented (LOW). ValidateConfigShellCommand deliberately allows `|`, `;`, `&&` for legitimate multi-step QA commands. CLAUDE.md item 52 records this as an explicit operator trust boundary so a future reviewer doesn't mistake it for a bypass. 3. CLAUDE.md certification block (item 43-52 + "Bulletproof certification 2026-06-11" subsection). Records the six-audit cycle, the verdict sentence verbatim, the 24-PR closing summary, and the remaining non-security tech debt. 4. Obsidian launch playbook — adds the 🛡️ certification banner with the verdict sentence and the audit-trail summary (govulncheck zero, 28/28 packages green, OWASP headers, bearer auth + bootstrap nonce, both CRITICAL findings closed, Go 1.26.4). All 28 packages still pass with -count=1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the two LOW findings from the certification audit and records the verdict in CLAUDE.md + the Obsidian launch playbook.
Prompt file perms (LOW)
`internal/runtime/registry.go` (`CLIRuntime.BuildCommand`) and `internal/runtime/tmux_runner.go` (`Runner.Run`) wrote agent prompt files at `0o644` — readable by every user on a shared dispatch host. Prompt content carries goal text + system context + WAVE_CONTEXT + acceptance criteria, any of which may include DSNs. Now `0o600`, with the parent `.vxd-prompts` dir at `0o700`.
YAML pipe/semicolon caveat (DOCUMENTED)
`ValidateConfigShellCommand` deliberately allows `|`, `;`, `&&` for legitimate multi-step QA commands. CLAUDE.md item 52 records this as an explicit operator trust boundary.
Certification record
Test plan