Skip to content

prompt: ship smoke-runner-delegation (#260) → complete - #283

Merged
Jammy2211 merged 1 commit into
mainfrom
claude/smoke-copy-drift-ci-docs-ozntvv
Aug 24, 2026
Merged

prompt: ship smoke-runner-delegation (#260) → complete#283
Jammy2211 merged 1 commit into
mainfrom
claude/smoke-copy-drift-ci-docs-ozntvv

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Summary

smoke-runner-delegation is complete. All ten vendored
.github/scripts/run_smoke.py copies are now thin delegators over the
PyAutoHands runners: 2085 lines → 1127, and most of what remains is the
docstring explaining why each file delegates.

Moves the prompt active/run_smoke_copy_drift.md
complete/2026/08/smoke-runner-delegation.md, prunes the active.md entry,
refreshes complete/index.md, regenerates the dashboard.

Merged

Repo PR Change
PyAutoHands #261 --list opt-in lists + the notebook leg
PyAutoHands #262 allowlist authoritative — the 13-script finding
PyAutoHands #263 regenerate_notebook resolves by relative path
4 × *_workspace_test #273 / #111 / #90 / #16 198 → 77
3 × user workspace #147 / #226 / #500 356 → 119
3 × HowTo already the end state

What the record keeps

  • The argument was never "they have drifted." Re-measured, there was zero
    functional drift inside any variant. That was the receipt for three manual
    N-repo sweeps, not evidence the design was safe — and the HowTo tier needed
    none of the three because it holds no logic.
  • The no_run-wins rule shipped in prompt: jax-grad-local-vs-ci-assertions (#260) — route, root cause, fix #261 would have silently dropped 13
    scripts
    from smoke coverage, with CI still green, because a skipped script
    is not a failure. Corrected before any workspace was touched, then confirmed
    in production.
  • regenerate_notebook's bare-filename lookup made the stale-notebook
    recovery dead for every real (nested) notebook. The old tests missed it
    because their fixture was flat.
  • Traps for the next person: --report-dir is load-bearing; run_notebook.py
    writes back in place; JUPYTER_MISSING_RC was not needed; a bare off/on
    entry in no_run.yaml parses as a YAML boolean and crashes should_skip.

Test Plan

  • lifecycle.py check → OK
  • lifecycle.py index --check → OK
  • All three record effects verified (record has ## Original prompt,
    active/ prompt gone, active.md section pruned)
  • Dashboard regenerated with pyauto-brain intake --apply dashboard

Generated by the PyAutoLabs agent workflow.


Generated by Claude Code

All ten vendored .github/scripts/run_smoke.py copies are now thin delegators
over the PyAutoHands runners. 2085 lines -> 1127, and most of what remains is
the docstring explaining why each file delegates.

Merged, each verified from the CI log rather than the green tick:
  PyAutoHands#261 --list opt-in lists + the notebook leg
  PyAutoHands#262 allowlist authoritative (the 13-script finding)
  PyAutoHands#263 regenerate_notebook resolves by relative path
  autolens_workspace_test#273, autogalaxy_workspace_test#111,
  autofit_workspace_test#90, autocti_workspace_test#16      (198 -> 77)
  autofit_workspace#147, autogalaxy_workspace#226,
  autolens_workspace#500                                     (356 -> 119)

The record keeps the two findings that mattered most: the no_run-wins rule
shipped in #261 would have silently dropped 13 scripts from smoke coverage with
CI still green, and regenerate_notebook's bare-filename lookup made the
stale-notebook recovery dead for every real (nested) notebook. Both were caught
by measuring the real repos before writing a delegator, and both are now pinned
by tests that were negative-tested against the old behaviour.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UpSFum81Jeq9KZ9wdKtaeZ
@Jammy2211
Jammy2211 merged commit c865bc2 into main Aug 24, 2026
2 checks passed
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