lifecycle: record arxiv-inbox-pat-scope complete - #319
Merged
Conversation
The filing fix shipped as PR #317 (main 308d4fa), so the draft that carried the diagnosis is no longer a draft. Records it to complete/2026/08/ and folds the prompt in under `## Original prompt` by hand — `record --prompt` folds an active/ prompt, and this task never entered active/ (it was filed and shipped in one session, never routed through /create_issue). `--prompt` is optional and 299 existing records carry no issue line, so neither is a special case. The record keeps five things worth not rediscovering: - a green clone is NOT write access. The 403 lands on the push, several steps after a reader assumes auth was proven. #57's record checked that the secret existed, not that its scope covered the new target, and a public-repo clone succeeds either way. - you cannot test arxiv_papers.yml from a branch that edits it. claude-code-action refuses when the file differs from the default branch's copy, then exits SUCCESS — so the POST fails on a missing payload, the inbox step never runs, and the error blames an expired OAuth token instead. - the backfill window is 168h, not 24h: the lookback is submission-anchored, so a paper announced today may have been submitted days earlier (#79's trap, reachable again through the recovery path). - adding a draft/ file makes dashboard.md stale and reddens PR CI; regenerate AFTER merging the base in, or it is stale again on landing. - intake's --apply is a global flag before the subcommand while --check is a subcommand flag. They are not symmetric. The one deliberately-open item is split out rather than buried: the board's empty inbox still reads the same whether arXiv was quiet or the filing broke — the ambiguity the #papers heartbeat already kills on the Slack side, with no equivalent on the board. Filed as draft/feature/pyautomemory/inbox_board_staleness_signal.md. lifecycle check: OK lifecycle index: OK intake dashboard --check: current 197 tests passed Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Sr4R6EDkgmAhm9tmvPiDUV
…eue-issue-x16qll # Conflicts: # complete/index.md # dashboard.md
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.
Close-out for the arXiv inbox filing bug, whose fix shipped as #317 (main
308d4fa). The draft that carried the diagnosis is no longer a draft, so thismoves it into the completion ledger.
Why it is recorded by hand
The task was filed and shipped in one session and never routed through
/create_issue, so it never enteredactive/.lifecycle.py record --promptfolds an
active/prompt; there is none, so the prompt is folded in under## Original promptmanually.--promptis optional and 299 existing recordscarry no
issue:line, so neither is a special case.What the record keeps
Five things worth not rediscovering:
steps after a reader assumes auth was proven. Daily arXiv strong-lensing paper digest → Slack #papers #57's record checked that
PAT_PYAUTOLABSexisted, not that its scope coveredPyAutoMemory, and apublic-repo clone succeeds either way.
arxiv_papers.ymlfrom a branch that edits it.claude-code-action@v1refuses when the file differs from the defaultbranch's copy — then exits success, so the POST fails on a missing payload,
the inbox step never runs, and the error blames an expired
CLAUDE_CODE_OAUTH_TOKENinstead of the real cause.so a paper announced today may have been submitted days earlier — PyAutoMind#79's
trap, reachable again through the recovery path.
draft/file makesdashboard.mdstale and reddens PR CI.Regenerate after merging the base in, or it is stale again on landing.
intake's--applyis a global flag before the subcommand while--checkis a subcommand flag. They are not symmetric.
The open item is split out, not buried
The board's empty inbox still reads identically whether arXiv was quiet or the
filing broke — the ambiguity the
#papersempty-day heartbeat already kills onthe Slack side, with no equivalent on the board. Filed as
draft/feature/pyautomemory/inbox_board_staleness_signal.mdrather than left asa paragraph inside a completed record.
Checks
lifecycle.py check: OKlifecycle.py index --check: OKintake dashboard --check: currentdashboard.md/dashboard.htmlregenerated (142 prompts — one draft removed,one added, net zero) and
complete/index.mdrefreshed to 1130 records.🤖 Generated with Claude Code
https://claude.ai/code/session_01Sr4R6EDkgmAhm9tmvPiDUV
Generated by Claude Code