Repository navigation
ci: validate GraphQL operations in Python sources #12784
Description
The GraphQL operations test from #12734 (.github/scripts/graphql-operations/graphql-operations.test.cjs) scans tracked JS, shell and workflow sources only. Python sources are not scanned, so the operations in 8 files under plugins/source-control/skills/babysit-prs/scripts/ are never validated against GitHub's schema, including the resolvedBy{__typename login} paginator in babysit_gh.py, the same field whose ... on Bot spread broke the review lanes.
Found by the claude-review lane on #12734: #12734 (comment)
What is needed
- Add
pytoSOURCEand teach the extractor Python's string shapes: implicit concatenation of adjacent literals inside parentheses, f-string{expr}substitutions (placeholder per position, as the JS path does), and triple-quoted literals. - Add an
unextractable.txtrow for each Python site that still cannot be checked, with its reason. - Remove the "Python sources are not scanned" notes from the test header and
unextractable.txt.
Acceptance
Changing resolvedBy{__typename login} to resolvedBy{... on Bot{login}} in babysit_gh.py makes node --test graphql-operations.test.cjs fail.
Activity
github-actions commentedon Nov 3, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
I understand this as extending the GraphQL operations test to scan Python sources under the babysit-prs scripts. The extractor needs to handle adjacent-literal concatenation, f-string placeholders and triple-quoted strings. Sites it can't check get
unextractable.txtrows. The "not scanned" notes come out, and changingresolvedBy{__typename login}inbabysit_gh.pymust fail the test.#12784 (comment)
This decision settles the open questions. I found no likely duplicates.
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Nov 3, 2026
Not admitted to the issue lane yet: no trusted-human acceptance criteria: a listed human must put the confirmed
- [ ]criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited; intake's refinement of this body is due and may supply them.melodic-automation-lanes commentedon Nov 3, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: The GraphQL operations test scans Python sources under babysit-prs/scripts, so changing resolvedBy{__typename login} in babysit_gh.py fails it, with unextractable.txt rows for sites it cannot check.
Open questions
RECOMMENDED: Treat #12734 as a dependency and work this issue once its test and unextractable.txt are on the base branch. Basis: Glob and Grep of .base found no graphql-operations files and no 'unextractable' text anywhere
RECOMMENDED: Scan production scripts only and exclude tests/, since tests may hold intentionally partial operations; follow whatever scope the JS path already uses. Basis: The issue says 8 files, but grep finds query/mutation text in many more .py files, e.g. tests/guard_contract.py with 33 matches
RECOMMENDED: Yes, add a row with a reason for each, as the issue states. Basis: The issue's What is needed section, third bullet
Sources read
To answer, post a comment that starts with this line:
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.kyle-sexton commentedon Nov 3, 2026
Decision recorded.
Agent choice, not an owner answer.
Answers to the refinement's three questions. (1) This issue builds on the graphql-operations test and
unextractable.txtthat #12734 added; this record is posted after #12734 merged, so both are on the base branch. (2) The scan covers the production scripts underplugins/source-control/skills/babysit-prs/scripts/and not theirtests/directory, whose files hold partial operations on purpose. (3) Yes: each Python site the extractor cannot resolve gets anunextractable.txtrow with its reason, rather than a refactor of the Python.SOURCEincludespy, and its extractor handles implicit concatenation of adjacent literals inside parentheses, f-string{expr}substitutions (one placeholder per position, as the JS path does) and triple-quoted literals.plugins/source-control/skills/babysit-prs/scripts/that still cannot be checked has anunextractable.txtrow with its reason; files under that directory'stests/are not scanned.unextractable.txt.resolvedBy{__typename login}toresolvedBy{... on Bot{login}}inbabysit_gh.pymakesnode --test graphql-operations.test.cjsfail.15 remaining items
github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026
melodic-automation-lanes commentedon Nov 4, 2026
The work-resolve-issue run that
agent-readystarted waited in its slot past a change to its lane workflow files on main, so it stopped before any model turn. The run's report-outcome removed and addedagent-readyback to start a fresh run on main's workflow files. If this run ends the same way, it re-fires the issue again, waiting longer each time.melodic-automation-lanes commentedon Nov 4, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41756522409, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-04T01:50:00Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 4, 2026
github-actions commentedon Nov 4, 2026