[kyle-sexton]

Refs: #7886

Summary

The intake caller moves to ci-workflows v0.49.0 (ff8cd36), which gates intake by author id (ci-workflows#773) and triages an issue named by a workflow_dispatch run (ci-workflows#774). v0.49.0 drops the OWNER/MEMBER admit rule, so this caller now passes the listed humans' ids explicitly.

Fix

• check-born-triaged emits human-ids: the trusted-actor list's kind: human ids, comma-joined, and empty when the list is unreadable.
• intake-triage.yml passes allowed-author-ids (those ids) and allowed-bot-sender-ids (41898282, github-actions[bot], plus the lanes App id when AUTOMATION_LANES_APP_SENDER_ID is set). It also gains a workflow_dispatch trigger with issue-number and passes that number through. A dispatch runs only from main, so the trusted-actor list, models block and AGENTS.md always come from the default branch.
• The lanes App id stays in allowed-bot-sender-ids. This is the owner's decision: issues the lanes App opens get intake.
• The reusable is pinned to ff8cd36321423de961381e608e4a31563e74adb3 # v0.49.0. The repin also brings in v0.46.0 through v0.48.0. git diff --stat v0.45.0 v0.48.0 touches only pr-review.yml and a compose-args test, so none of those changes reach this caller. v0.49.0 changes intake-triage.yml and nothing that file uses (report-lane-outcome is unchanged).

Verification

• node --test .github/actions/check-born-triaged/check-born-triaged.test.mjs .github/actions/resolve-config/callers.test.mjs: 31 pass, 0 fail, including the dispatch guard, the id wiring and the bot id list.
• actionlint and zizmor --offline on the touched workflow and action: clean.
• runner-policy.mjs --root .: passes after merging main, which carries the standards sync #8058 of the reviewed intake-triage contract (standards#802).
• Not run live yet. Intake triage skips every issue: repin the author-id gate and add dispatch intake #7886 holds the post-merge checklist: the opened path, the dispatch path and the skipped-job path.

Related

• ci-workflows#772, Intake triage skips every issue: repin the author-id gate and add dispatch intake #7886, docs(pr-pipeline): hold a lane PR on a not-verified item that can stop the lane #7888.
• The runner-input contract: standards#802, synced here by #8058.

🤖 Generated with Claude Code

https://claude.ai/code/session_019bQ8pL7fJgVy7YjQ7wK1Zw

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-18T07:31:55.130073Z	6fa815c	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

claude-security-review reviewed 6fa815c1bc820898726be576fb1369c1244dbf71: 0 finding(s), 0 as inline comments.

Security review: PR #7924 (head 6fa815c)

No security findings.

This change lets the intake lane admit listed humans by id and adds a workflow_dispatch entry point to intake-triage.yml. I read the full diff and the final intake-triage.yml and action.yml. I did not read the reusable workflow at ci-workflows v0.49.0, so its admission behavior is taken from the comments in this diff.

• Dispatch from a branch. The born-triaged job now has if: github.event_name == 'issues' || github.ref == 'refs/heads/main'. On a dispatch from another ref that job is skipped. Its outputs are then empty, so claude-args is empty and the intake-triage job does not run. A branch-modified workflow therefore cannot run intake with its own trusted-actor list, models block or AGENTS.md, and it never reaches the secrets.
• Injection. issue-number reaches the script only through an env: variable. The script accepts it only if it matches ^[1-9][0-9]*$, and the test for 7; echo confirms a bad value is rejected. LANES_APP_ID is also passed through env:. The bot-id step keeps it only if it is all digits.
• Trusted ids. humanIds keeps only kind: human entries whose id is a positive integer. A list that cannot be read or has the wrong version gives an empty string, so the reusable turns away every person.
• Bot admission. Listing github-actions[bot] (41898282) lets a dispatch sent with a repository GITHUB_TOKEN through. That is intended and limited to workflows in this repository. The comment correctly notes that an issue opened with a GITHUB_TOKEN starts no issues run, so the id does not admit issue events.
• Residual trust. A dispatcher on the allowlist can ask for any issue number to be triaged, including one an outsider opened. That is by design: the dispatcher is trusted, and the lane's own untrusted-content handling covers the issue text. Nothing in this diff changes that.
• Permissions. They are unchanged: permissions: {} at the top, contents: read and issues: read for the gate, and issues: write for the lane.
• Pin. The reusable moves from v0.45.0 to v0.49.0, still pinned to a full SHA. Pin changes are zizmor's lane, so I did not review them further.

[github-actions]

claude-review reviewed 6fa815c1bc820898726be576fb1369c1244dbf71: 0 finding(s), 0 as inline comments.

No findings on PR #7924 at 6fa815c.

What I checked

• check-born-triaged.mjs: humanIds(list) returns an empty string when the list is unreadable. It keeps only kind: human actors with a positive integer id. main() computes it before the issue read, so human-ids is still emitted when the issue number is invalid or the issue is unreadable. writeOutputs handles the hyphenated key, and the CLI test regex now accepts it.
• action.yml and the README add the human-ids output and document the new fall-through: a failed gate leaves skip and human-ids empty, so the reusable turns away every person.
• intake-triage.yml:
  • The born-triaged job's if runs for issues events and for dispatches from refs/heads/main. A dispatch from another ref skips the job. intake-triage then also skips, because its claude-args guard is empty.
  • The gate takes issue-number from github.event.issue.number || inputs.issue-number.
  • The bot-id step composes 41898282 plus the lanes App id only when it matches ^[1-9][0-9]*$.
  • The concurrency group falls back to inputs.issue-number.
• The reusable is repinned to ff8cd363… (v0.49.0), and the runner-policy policy.json already has an entry for that SHA.
• The other consumer of the action, intake-label-needs-triage.yml, reads only skip, so the extra output does not affect it.
• The new tests in callers.test.mjs have their imports (spawnSync, mkdtempSync and the rest). The evaluate helper supports the || and == operators the new if uses.

Not verified

• I could not run node --test in this session because the sandbox required approval. The "31 pass" figure is the author's claim and I did not confirm it.
• Whether the reusable (ci-workflows v0.49.0) checks the issue author on a dispatch is outside this diff and not confirmed. If it does not, a GITHUB_TOKEN workflow, listed as an admitted bot by id 41898282, could dispatch intake for an issue an untrusted person opened. That is a question for the security lane and the reusable, not this diff.

Closing issue
The PR uses Refs: #7886, not a closing keyword, and the context file has no closing-issue section, so there were no acceptance criteria to check.