Skip to content

Session Handoff [default]: #1739's Two-Channel Skills Report Released as 2.0.661, and #1756 Is Decided #1761

Closed

Description

@ptr727

One deliverable, start to finish: #1739 is implemented as decided, merged in #1755, promoted in #1760, and released as 2.0.661. skills_install.py --report now answers the Codex and opencode snapshot and the live Claude Code checkout separately. A correctly finished merge-and-release run now reads current after step 8, which was measured on this machine at release.

Next steps, in priority order

Re-ranked from #1753. Re-read each issue rather than trusting these summaries.

  1. Implement Bootstrap registers its temporary tree as the live Claude Code skills source, then deletes it #1756 as decided. The maintainer chose to clone the hub durably. When the bootstrap's host mode finds no hub clone, it clones the hub into the fleet layout's base-clone location and runs the skills installer from there, not from the extracted tarball. The decision comment is the spec. Done looks like a fresh bootstrap.sh --host whose --report shows live.checkout as an existing clone rather than a reason saying the checkout doesn't exist. bootstrap.sh and bootstrap.ps1 both change, and the PowerShell side needs a native Windows run before it counts as fixed.
  2. Act on A regex pins a phrase inside a # comment, so rewrapping that comment fails the test with a false explanation #1732. Carried unchanged: three assertions pin a whitespace-bearing needle against wrappable Python. Nothing started.
  3. Work the skills_install.py follow-ups: skills_install --report follow-ups: stamp-less live report, bootstrap remedy text, --intended guard test #1759, then skills_install source_ref hides ignored files and trusts an enclosing git repo #1758, then skills_install --report's live channel does not check that the plugin is installed and enabled #1757.
  4. Decide whether stacked pull requests are documented or banned (A stacked pull request's diff reopens after the parent squash-merges, and nothing documents it #1742). Carried. It's a question to ask when the work starts.
  5. Bump Financial-Modeling's hub workflow pins. Carried and still unattempted. Five sites are listed on Session Handoff [default]: One Issue Closed Whose Premise Was Wrong, and a Release #1735.
  6. Click Check for Updates on the four stalled repositories plus Financial-Modeling. Maintainer-only.
  7. Act on the regenerated Converge Financial-Modeling with the hub baseline (32 findings) #1579, after re-running it against current main. Then The widened configuration shape misses the unspaced key=value an environment file writes #1717 and issue-ref reads no URL outside instruction text, so an own-repository tracker URL in code is banned and unreported #1719.
  8. skills_install.py runs a bare claude argv, which may miss a Windows .cmd shim #1754, the Windows-only gaps in skills_install.py: the bare claude argv against a .cmd shim, and the timeout grandchild hang. It needs a native Windows host, so it waits until one is available.

External blockers

Internal dependencies

State

Every fact here is re-derived at resume rather than trusted.

The parked decision queue

Empty. No open issue carries the decision label. This session put five questions to the maintainer and got answers, each recorded on its issue or pull request:

  1. skills_install's two channels disagree: Claude Code loads the checkout in place while the copy holds the promoted revision #1739's default intended revision: origin/main.
  2. skills_install's two channels disagree: Claude Code loads the checkout in place while the copy holds the promoted revision #1739's exit code: the snapshot verdict alone.
  3. The review-loop stop point on Report the Skills Snapshot and the Live Checkout Separately #1755: revert the exit code 2, make the small fixes, file the rest.
  4. Whether to merge and release Promote the Two-Channel Skills Report to Main #1760: merge and release.
  5. Bootstrap registers its temporary tree as the live Claude Code skills source, then deletes it #1756: clone the hub durably.

What the last round did

What not to repeat

  • Don't accept "Claude Code serves the plugin cache" from a reviewer. Two review passes raised it, pointing at installPath in the CLI's plugin state, which names a month-old cache directory. It's wrong: the harness reports a skill's base directory inside the hub checkout, and a loaded skill carried develop-only text that the cache lacks. skills_install's two channels disagree: Claude Code loads the checkout in place while the copy holds the promoted revision #1739's own credit section warned about exactly this trap. Cost: one pass's worth of findings to disprove.
  • Don't add an exit code in a fix round. An exit 2 for "cannot judge", added to answer one finding, contradicted six surfaces that say "re-install when --report exits non-zero". The next pass found that, and the round was spent reverting it. Put a new state in the JSON instead.
  • Don't pass --arg to gh --jq. Pipe to jq instead. The release-run correlation lost one call to this. It's a known trap, already in memory.
  • Don't chain cat >> /dev/null into a script. With no stdin it blocks until the tool times out. Give every command </dev/null in a long compound.

New learnings

  • A skill's text is fixed for the session at load. merge-and-release, loaded after Report the Skills Snapshot and the Live Checkout Separately #1755 was already on develop, still showed the old step 7, so skill content is read once per session rather than on every invocation. Recorded in memory.
  • Every local review pass drew findings until the change stopped moving. There were eight recorded passes with 6, 2, 5, 5, 3, 2, 2, and 0 findings, and the only clean pass was over a one-line comment. That matches the existing memory that new content doesn't converge under review, and the two-round budget is what ended the loop.

Activity

  1. added
    handoffA link in the session handoff chain, one open issue per track
    on Sep 24, 2026
  2. ptr727 commented on Sep 24, 2026

    @ptr727
    OwnerAuthor

    Continued in #1776, round 28 on track default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    handoffA link in the session handoff chain, one open issue per track

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions