FailproofAI/failproofai

CHANGELOG.md currently contains 76 entries ending in a literal (#PR) instead of a pull-request number: grep -c '(#PR)' CHANGELOG.md # 76 The very first entry in the file — ## 1.0.1-beta.0 — 2026-08-12 — is one of them, so it's the first thing anyone reading the changelog sees. CONTRIBUTING.md asks every entry to end with its PR number (e.g. (#123)). (#PR) is the placeholder people write before the PR exists, and it's being forgotten on the way out. Two parts, both beginner-friendly 1. Backfill the numbers. For each (#PR), find the PR that introduced the entry and substitute the number. git log -S'<a distinctive phrase from the entry>' -- CHANGELOG.md will point you at the commit, and the merge commit or gh pr list --search gets you the number. Where an entry genuinely never had a PR, drop the (#PR) rather than inventing one. This is mechanical but not blind — take it in batches and note anything ambiguous in the PR description rather than guessing. 2. Add a CI guard so it can't

COPILOT_TOOL_MAP in src/hooks/types.ts canonicalises GitHub Copilot's tool names so that policies written against canonical names (Bash, Read, Task, …) fire on Copilot sessions. Two documented Copilot tools are missing from it: task and web_search. Why it matters Unmapped tool names pass through uncanonicalised. So a policy matching toolName === "Task" silently never fires on Copilot — no warning, no error, it simply doesn't run. For a guardrail tool that's the worst failure mode: the user believes they're protected and they aren't. Where to fix Add to COPILOT_TOOL_MAP in src/hooks/types.ts: task: "Task", web_search: "WebSearch", The existing web_fetch: "WebFetch" entry sits right there as a model to follow. One small judgement call Copilot also documents an ask_user tool. It has no filesystem or shell reach, so it's arguably benign and needs no entry at all. We genuinely haven't decided — form a view and say which way you went in the PR description. Either answer is fine if it's

writeCacheEntry() in lib/codex-sessions.ts does a read-modify-write with no atomic rename: function writeCacheEntry(sessionId: string, path: string): void { try { mkdirSync(dirname(CACHE_PATH), { recursive: true }); const cache = readCache(); cache[sessionId] = path; writeFileSync(CACHE_PATH, JSON.stringify(cache), "utf-8"); // not atomic } catch { // Cache is best-effort } } The dashboard fans out Codex session lookups in parallel on the projects page, so these writes can interleave. Why it matters A lost entry isn't the problem — that's just a cache miss, and the next lookup rescans and repopulates it. The problem is a torn file. If a write is interrupted partway, readCache() hits invalid JSON, throws, and the entire cache map is lost — not one entry. That turns a harmless race into a full cache wipe. Where to fix lib/codex-sessions.ts: Write to a process-unique temp path — ${CACHE_PATH}.${process.pid}.tmp renameSync() it into place (atomic on the s

failproofai policies prints ANSI colour even when NO_COLOR=1 is set, and there is no --no-color flag at all. Most of the CLI already gets this right — install-prompt.ts, audit/report.ts and audit/cli.ts all honour it. src/hooks/manager.ts is the holdout, and it happens to be the output people most often pipe into CI logs. Reproduce Under a real TTY (piping hides it, because a non-TTY disables colour anyway): script -qec "failproofai policies" /dev/null | grep -aoP '\x1B\[' | wc -l # 32 script -qec "env NO_COLOR=1 failproofai policies" /dev/null | grep -aoP '\x1B\[' | wc -l # 32 ← should be 0 The green ✓ marks come out as ESC[32m✓ESC[0m regardless. Where to fix src/hooks/manager.ts hardcodes ANSI escapes at 16 sites. Route them through paint() from src/hooks/tui.ts, which already gates on NO_COLOR through colorsEnabled(). src/hooks/install-prompt.ts:261 is a worked example of the pattern: const { dim, bold, guide: teal, pink, pinkBold } = paint(!process.env.NO_COLOR); Then ad

Description In the Hook Logs table (app/components/session-hooks-panel.tsx:329), a row is expanded only via <tr onClick={() => toggleRow(i)}> with cursor-pointer. The row has no tabIndex, no role="button", and no onKeyDown, and the disclosure indicator is a bare <ChevronDown> icon (:342), not a button. Interaction is mouse-only. Steps to Reproduce Open a session's Hook Logs panel in the dashboard. Using only the keyboard (Tab / Enter / Space), try to expand a row to see its details (Session ID, CWD, full reason, matched policies). There is no focusable control — the detail panel is unreachable without a mouse. Screen-reader users get no affordance that the row is interactive. Expected Behavior Row expansion should be operable by keyboard and announced to assistive tech — e.g. Tab to focus, Enter/Space to toggle, with aria-expanded reflecting state. Failproof AI Version 0.0.14-beta.1 Node.js / Bun Version Bun 1.3+ Operating System macOS Additional Context Approachable a11y starter