Skip to content

Session Handoff [default]: KiCadLibrary Standup Finished as 2.1.49, LF Conversion Ordered and Released as 2.0.810 #2328

Closed

Description

@ptr727

Next steps, in priority order

Re-read each issue and pull request rather than trusting these summaries.

  1. Hub follow-ups, each its own small pull request:

    Done means each merged to develop and promoted.

  2. The six repositories from Session Handoff [default]: Table Carry, Quota Safety and install-tools Shipped to Develop, Defined-Moments Review Gate #2278 Ready #2281: EspDinIoT, DevKitCIoT, HomeAssistant-Config, PhotoCleaner, AudioCleaner and HolidayLights. Audit each one before choosing a procedure. Each needs a fresh write grant.

    • EspDinIoT, DevKitCIoT, AudioCleaner and HolidayLights still need the LF conversion, per docs/eol-lf-rollout.md "Per-Repo Conversion", which now states the trigger and the ordered steps. Their checklist rows say what each one lacks.
    • The conversion lands first, as its own pull request, then the resync or standup is based on develop.
  3. KiCadLibrary's hooks rollout box. docs/pre-commit-hooks-rollout.md ticks a box only once a committed hub audit records parity.hooks operational. KiCadLibrary's .pre-commit-config.yaml is on main (ptr727/KiCadLibrary#70), so a hub-side audit report under reports/ is what unblocks the tick.

  4. Carried from Session Handoff [default]: configure.sh Refuses Unknown Arguments, Released as 2.0.805 #2289: the rest of Every CLI Script Answers --help and Refuses Unknown Arguments Before Writing #2285, Audit Cross-Checks No Python Dependabot Ecosystem, and KiCadLibrary's requirements-dev.txt Is Untracked #2286's audit check, Run the Whole Test Suite Before a Push, Not the Modules a Change Touches #2280, Fix STANDUP.md's Prerequisite Item That Says Mechanisms Declare Environments #2270, and the items Session Handoff [default]: Table Carry, Quota Safety and install-tools Shipped to Develop, Defined-Moments Review Gate #2278 Ready #2281 carried from Session Handoff [default]: Fork Handoff Chains Released as 2.0.799, #2268 Fix on Develop #2273.

External blockers

Internal dependencies

State

The parked decision queue

Zero issues carry the decision label in ProjectTemplate or KiCadLibrary. This round's questions were asked as they came up and answered:

What the last round did

What not to repeat

  • Ticking a rollout box from a reading of the downstream config. docs/pre-commit-hooks-rollout.md requires a committed hub audit, and the local review caught a tick that skipped it. Read each tracker's own maintenance rule before ticking, since the trackers differ:

    • reusable-workflows.md ticks on the stub plus a clean interface audit.
    • The hooks tracker needs a committed report.
  • New procedure prose took 7 strict-review rounds and 4 Copilot findings, about 20 findings in all. Every round found defects in the previous round's fix, and almost every claim needed an empirical check:

    • git diff versus --cached
    • --renormalize touching only the index
    • git worktree add refusing a branch that is already checked out
    • attribute precedence per property
    • editorconfig-checker under insert_final_newline = false.

    Verify each git or tool claim in a scratch repository before writing it, and budget the escalations up front.

  • Trusting pr_review.py wait right after a close-and-reopen. It returned on the superseded run's failure (pr_review.py Counts a Check Run a Rerun on the Same Head Superseded #2327). Watch the new run with gh run watch instead.

  • An unquoted heredoc around Python holding backticks. The shell ran them as commands and the edit failed silently. Quote the delimiter (<<'PYEOF').

New learnings

Activity

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

    @ptr727
    OwnerAuthor

    Update after this link was written: the KiCadLibrary secrets blocker is cleared.

  3. ptr727 commented on Oct 4, 2026

    @ptr727
    OwnerAuthor

    Re-ranked by the maintainer: work these first, ahead of the body's step 1.

    These are the hub issues the homeassistant-purpleair session filed while reconciling its release model with the fleet's. The maintainer's direction to that repo was to follow the fleet standard, and to file an issue only where it is genuinely special or has found a real bug. The purpleair session gave a verdict on each one (asked on 2026-10-04). It judged the older ones from their titles and its handoff ptr727/homeassistant-purpleair#403, so re-read each body before acting.

    Real fleet bugs in hub tasks and snippets:

    Stale or defective canonical prose:

    Tooling bugs:

    Process gaps and requests:

    Candidate to close: #2312, "Settle the D4.7 Dispatch Window". The purpleair session thinks it is a reconciliation question rather than a bug. Check whether current WORKFLOW.md D4.7 already settles it. If it does, close it with the quote. If it does not, fix the text.

    Not hub work, recorded for context:

    The rest of the body's next steps follow these, in the same order.

  4. ptr727 commented on Oct 4, 2026

    @ptr727
    OwnerAuthor

    Continued in #2350, round 48 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