Skip to content

backlog(B-0107): add P3 row — CodeQL dismiss pattern for peer-call siblings#897

Merged
AceHack merged 3 commits intomainfrom
backlog/B-0107-codeql-peer-call-dismiss-pattern-2026-04-30
Apr 30, 2026
Merged

backlog(B-0107): add P3 row — CodeQL dismiss pattern for peer-call siblings#897
AceHack merged 3 commits intomainfrom
backlog/B-0107-codeql-peer-call-dismiss-pattern-2026-04-30

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 30, 2026

Summary

Adds docs/backlog/P3/B-0107-codeql-peer-call-dismiss-pattern-2026-04-30.md.

Surfaced during slice 15 #896: CodeQL flagged js/indirect-command-line-injection on runContextCmd (by-design — --context-cmd is a user-supplied-shell-command feature). Resolution there was per-PR dismissal.

The two peer-call sibling ports (gemini.sh + codex.sh) will hit the same alert when ported. This P3 row tracks the structural fix: a path-scoped query-filter in .github/codeql/codeql-config.yml so all 3 peer-call TS ports share one acknowledgment.

Effort

S (small) — ~10 lines of YAML + verify on next sibling PR.

Test plan

  • Per-row schema (frontmatter + body).
  • CI gate (markdownlint + frontmatter validation).

🤖 Generated with Claude Code

…blings

Surfaced during slice-15 PR #896 review on 2026-04-30: CodeQL
flagged `js/indirect-command-line-injection` (medium severity)
on `runContextCmd` in tools/peer-call/grok.ts. By-design — the
script contract is 'user explicitly supplies a shell command via
--context-cmd'; same trust boundary as bash original's `eval`.

Resolution on #896 was per-PR dismissal via gh api code-scanning/
alerts/N. The two sibling ports (gemini.sh + codex.sh) will hit
the same alert when ported. This row tracks the structural fix:
add a path-scoped query-filter to .github/codeql/codeql-config.yml
so all 3 peer-call TS ports share one acknowledgment.

Composes with B-0086 (TS+Bun migration) and PR #896.
Effort S. P3 — not blocking; per-PR dismissal works as fallback.
Copilot AI review requested due to automatic review settings April 30, 2026 06:04
@AceHack AceHack enabled auto-merge (squash) April 30, 2026 06:04
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new P3 backlog row to track a planned CodeQL suppression/tuning approach for the peer-call TypeScript ports, based on the CodeQL alert surfaced in slice 15 (#896).

Changes:

  • Add backlog row B-0107 documenting the js/indirect-command-line-injection alert context and proposed handling options.
  • Define a recommendation and acceptance criteria for a future structural fix in CodeQL configuration.

Comment thread docs/backlog/P3/B-0107-codeql-peer-call-dismiss-pattern-2026-04-30.md Outdated
…tance-criteria specificity

Two Copilot threads on PR #897:

1. Broken inline-code span: gh-api command was wrapped in backticks
   but split across two lines, breaking markdown rendering. Switched
   to a fenced bash code block with line-continuations + placeholder
   <N> for alert ID.

2. Acceptance-criteria specificity: original said 'query-filters'
   exclusion but path-scoping a single rule is non-trivial in
   CodeQL config. Reframed to require verifying the syntax
   during implementation (CodeQL supports query-filters rule-scoped
   AND paths-ignore path-scoped; per-rule + per-path needs combining
   them or a custom suite). Added link to GitHub docs.
@AceHack AceHack merged commit 205d12a into main Apr 30, 2026
21 checks passed
@AceHack AceHack deleted the backlog/B-0107-codeql-peer-call-dismiss-pattern-2026-04-30 branch April 30, 2026 06:12
AceHack added a commit that referenced this pull request Apr 30, 2026
…igration (#898)

* ts(B-0086): port 1 peer-call sibling (.sh→.ts) — slice 16 of TS/Bun migration

* ts(slice-16, wip 1/N): port peer-call/gemini (.sh→.ts)

Sibling of slice-15 grok port (PR #896). Wraps 'gemini -p'
non-interactive headless mode. Read-only safety preserved
(--approval-mode plan + --skip-trust per the Copilot fix on
the bash original PR #28).

Reuses the structural pattern from grok.ts:
- classifyFlag + MutableArgState parser (under cog-complexity 15)
- spawnSync + stdio:inherit for live LLM streaming
- isRegularFile + readHead helpers
- /bin/sh -c for context-cmd (same trust as bash eval)
- PREAMBLE preserved verbatim with Gemini-specific framing
  (proposes role per four-ferry consensus)

Lint-clean: bun --bun tsc --noEmit + eslint strictTypeChecked +
sonarjs all pass. Argument-validation byte-equivalent.

Note: the same CodeQL js/indirect-command-line-injection alert
will fire here as on grok.ts; per B-0107 (filed in PR #897)
the per-PR dismissal pattern applies. Will dismiss after PR opens.

* review(slice-16): address Codex P1 + P2 — head-only file read + pipe-through-head context-cmd

Two real Codex findings on PR #898 (both also apply to grok.ts —
backport in follow-up PR):

P1 — Read only file head instead of loading full file:
  Original used readFileSync + Buffer.subarray which loads the
  entire file into memory then slices. For large artifacts (logs,
  dumps) this is a memory-spike regression vs bash 'head -c 20000'.
  Replaced with openSync + readSync(fd, buf, 0, bytes, 0) which
  reads only the first FILE_HEAD_BYTES bytes from disk. Wrapped
  in try/finally for fd cleanup.

P2 — Truncate context command output at source:
  Original used spawnSync with maxBuffer up to 64MB then sliced
  to CTX_HEAD_BYTES afterward. For high-volume commands (wide
  'git diff' ranges) this blocks longer and uses more memory
  than the bash original's '... | head -c 20000' pipeline that
  short-circuits at the boundary.
  Reframed wrapped command as: (cmd) 2>&1 | head -c <N>
  so the shell pipeline truncates at source. Same trust contract
  preserved (user supplies cmd; we just augment with head-c).

Verified locally: 100MB test file reads only 20000 bytes via the
new head-only path.

* review(slice-16): preserve shell parse errors per Codex P2 + Copilot (#899 finding backport)

Same fix as #899 backport — runContextCmd was returning only
result.stdout, dropping shell-process stderr (where parse errors
land, OUTSIDE the (cmd) 2>&1 redirect). Concat stdout+stderr then
slice to CTX_HEAD_BYTES.

* review(slice-16): address #898 P1+P2 — exit codes, spawn classification, bash shell, file-read errors

Five real findings from Copilot+Codex on PR #898:

Copilot P1 — Exit codes 0|2|64 per repo-scripting.md:
  Switched return 1 → return 64 for invocation/usage errors
  (--model/--file/--context-cmd missing values, unknown flag,
  empty prompt). Aligns with the conventions in docs/best-
  practices/repo-scripting.md §exit-codes. Process-related
  errors (gemini missing on PATH, build-prompt error) keep 1
  for tooling/input failure.

Copilot P1 — spawnSync result.status ?? 1 collapses launch failures:
  Added classifySpawnFailure helper (4-case: status set /
  ENOENT → 127 / signal / other) — same pattern from PR #887.
  Distinguishes ENOENT/permission/signal from a normal non-zero
  exit, with a contextual stderr message.

Codex P2 — eval vs /bin/sh syntax difference:
  Switched /bin/sh -c → /bin/bash -c so the bash original's eval
  semantics (accepting bash-only features like `[[ ]]`, brace
  expansion, process substitution) are preserved. /bin/sh on
  Ubuntu is dash and rejects these.

Codex P2 — file-read failures silently dropping context:
  readHead() now returns ReadHeadResult { ok, content, error }.
  buildFullPrompt() propagates the error to the user via stderr
  instead of pretending context was attached when read failed
  (permission denied, race, etc.).

Threads on already-addressed findings (PRRT_kwDOSF9kNM5-pd16
runContextCmd full-buffering + PRRT_kwDOSF9kNM5-pd2a readHead
full-file-read) were resolved in the parse-error-fix commit
ceed1e7.

Threads on PRRT_kwDOSF9kNM5-pd2U PREAMBLE-names: pushing back
because the PREAMBLE is prompt content sent verbatim to the
LLM peer, not pure code-surface; changing it diverges from
the bash original byte-equivalence. A separate task to retool
PREAMBLE attribution on both bash AND TS together is the
right shape, not a one-side rename here.

* review(slice-16) round-2: revert exit-code 64 → 1; fix commandAvailable

Three new findings on the latest push:

Codex P2 (PRRT_kwDOSF9kNM5-pon2) + Copilot P0 x2 — exit codes:
  Last commit switched to exit 64 per docs/best-practices/repo-
  scripting.md. Reviewers correctly point out tools/peer-call/
  README.md is the more specific spec and says 0/1/2 uniform
  across all three peer-call wrappers. Specific wins on overlap.
  Reverted ArgError.exitCode 64 → 1 + the empty-prompt return
  64 → 1. Matches grok.ts (slice 15) and the bash original.

Copilot P1 — commandAvailable() shape:
  Was using `<cmd> --version` and requiring exit 0. Some CLIs
  exit non-zero on --version. Bash uses `command -v <cmd>`
  (PATH existence check, no execution). Switched to
  `spawnSync('/bin/sh', ['-c', \`command -v "${cmd}"\`])`
  to match bash semantics.

Copilot P1 (PRRT_kwDOSF9kNM5-ppuR) — PREAMBLE names: same as
prior thread; pushing back with same rationale (PREAMBLE is
verbatim prompt content sent to LLM, not pure code-surface;
preserving bash-equivalence). Will reply on the new thread
the same way.

Copilot P2 (PRRT_kwDOSF9kNM5-ppt6) — PR description says /bin/sh
but code uses /bin/bash. The /bin/bash switch was a Codex P2 from
the prior round (preserve eval semantics for bash-only features).
Will update PR description, not the code.
AceHack added a commit that referenced this pull request Apr 30, 2026
…igration (#900)

* ts(slice-17, wip 1/N): port peer-call/codex (.sh→.ts)

Third sibling of the peer-call cluster (after grok #896 and gemini
#898). Wraps 'codex exec -s read-only --skip-git-repo-check' (default)
or 'codex review' (with --review). --model is ignored in --review
mode with a warning to stderr.

Bakes in all the round-2 + round-3 fixes from the gemini.ts review
cycle:
- exit codes 0/1/2 uniform per tools/peer-call/README.md (NOT 64)
- commandAvailable via /bin/sh -c 'command -v <cmd>' (PATH check, not
  --version)
- /bin/bash -c (not /bin/sh -c) for context-cmd to preserve bash-only
  feature support (Codex P2)
- ReadHeadResult { ok, content, error } so file-read failures surface
  to stderr instead of silently dropping context
- classifySpawnFailure 4-case helper (status / ENOENT → 127 / signal /
  other) reused from PR #887 + slice-16 #898
- Concat stdout + stderr from runContextCmd to preserve shell parse
  errors that fall outside the inner ( ) 2>&1 redirect

Lint-clean: bun --bun tsc --noEmit + eslint strictTypeChecked +
sonarjs all pass. Argument-validation byte-equivalent.

Note: same CodeQL js/indirect-command-line-injection alert will fire
here as on grok.ts and gemini.ts. Per B-0107 (filed in PR #897) the
per-PR dismissal pattern applies until B-0107 implements the
structural fix.
AceHack added a commit that referenced this pull request Apr 30, 2026
…sure (#903)

Per the consolidated-row-pattern (rows from 03:41Z + 05:01Z arc
closures): when a session lands many small commits across multiple
ticks, a single consolidated row summarizing the arc is more
signal-dense than N minimal rows.

Covers the slices 15-19 arc that landed after the 05:43Z slice-14 row:
  - #896 slice 15 (grok.ts) — peer-call cluster opens
  - #898 slice 16 (gemini.ts) — peer-call sibling
  - #899 backport to grok from #898 review-cycle findings
  - #900 slice 17 (codex.ts) — peer-call cluster closes
  - #897 B-0107 row — CodeQL dismissal pattern
  - #901 slice 18 (daily-cost-report.ts) — budget wrapper
  - #902 slice 19 (project-runway.ts) — budget cluster closes (in flight)

Three new substrate observations recorded for future-Otto:
  - sibling-port-cost decreases monotonically (round-2/3 fixes
    bake into later siblings proactively)
  - kernel-pipe vs JS-space stream interleaving distinction
    (bash `2>&1` merges shell-side; `result.stdout + result.stderr`
    in JS does not preserve chronological ordering)
  - fix-the-bug + file-the-row + implement-the-row + closeout pattern
    is the durable shape (B-0106 + B-0107 are both worked examples)

Cron 98fc7424 still armed.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants