Repository navigation
fix(cron): Let managers read run receipts [AI-932] - #13
Open
finn-atlas wants to merge 1 commit into
Open
finn-atlas wants to merge 1 commit into
finn-atlas wants to merge 1 commit into
Conversation
Author
|
@codex review |
|
To use Codex here, create a Codex account and connect to github. |
Allow admitted channel owners and Control UI administrators to inspect targeted automation run history while preserving ordinary session visibility and rejecting all-history reads. Refs AI-932.
finn-atlas
force-pushed
the
atlas/ai-932-cron-runs-management
branch
from
November 9, 2026 04:58
5d5d123 to
894dd21
Compare
finn-atlas
changed the base branch from
maintain/googlechat-patch-stack-2026-10-17
to
patch/shared-googlechat-2026-11-08
November 9, 2026 04:58
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
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.
What Problem This Solves
Fixes: an authenticated automation manager receives
Automation not foundwhen it reads a run receipt from an automation in another conversation session.User Impact
User impact: configured channel owners and Control UI administrators can inspect targeted run history for automations they already manage. Ordinary turns still see only their sessions, and agent-runtime callers cannot request all-history reads.
This change expands read permission for targeted automation run metadata. Merge and deployment require recorded Sysops approval.
Why This Change Was Made
The automation management grant permits list, get, update, run, and remove operations, but it omits
cron.runs. The request therefore uses ordinary conversation visibility and hides a valid job from an admitted manager.This change adds targeted run-history reads to the existing management capability. It checks that capability again before disclosure and keeps
scope: allblocked for agent-runtime callers.Evidence
5b5c6ff859fb737ba04a3dd76d6af1294526150d. Thecron.runsrequests returnedAutomation not foundafter list and get found both job IDs.894dd21a0688bb662a5df64d249b34ff15f17426has a valid GitHub signature fromfinn-atlasand uses the deployed revision as its parent.pnpm tsgo:core, all 19 source-test typecheck shards, targeted formatting and lint checks, and the PR behavior-proof check.Rollback: deploy revision
5b5c6ff859fb737ba04a3dd76d6af1294526150dagain.