Session Handoff [default]: Resynced With Hub 0378c78 and Promoted Without a Release #360

The hub resync is done and promoted. #358 carried hub main at 0378c78 into develop, and promotion #359 took it to main with no release, since only instruction and config files changed. The post-merge audit (run 2026-10-01T17:17:45Z, main@19a2b00) reports 0 defect or letter findings and 4 drifts, down from 42: the registry python type (#356) and three verified timestamp-only intent advisories.

Next steps, in priority order

1. Adopt the Lint-Only Python Profile or Record Why Python Is Not Tracked #356: adopt the lint-only Python profile, or record why Python is not tracked. The carried WORKFLOW.md D1.6 now owes a coverage report per declared Python directory, and the hub registry wants python in Blog's types. Done looks like the profile adopted (tool-config pyproject.toml, directories declared to the hub validator, a suite and coverage per directory, capture/ given tests or left undeclared with a reason) plus the registry type, or a registry driftNote. Which of the two is the maintainer's call, so see the decision queue below. The registry half is a hub pull request, which needs the maintainer's permission in that session.
2. Keep the Override Prose in Step When a Theme Override Row Retires #353: keep the root override prose in step when a row retires. A small themes/README.md edit. Done looks like the retire step naming that prose, or the prose no longer naming individual rows.
3. Drop the Nonexistent i18n Directory From the Repository Layout #357: drop the nonexistent i18n/ link from GOVERNANCE.md "Repository Layout". That section is Blog's own, not a carried one. Done looks like the entry naming only directories the tree holds.

External blockers

• The registry half of Adopt the Lint-Only Python Profile or Record Why Python Is Not Tracked #356 is a write to the hub, a separate repository, so it needs the maintainer's explicit permission in the session that makes it.

Internal dependencies

• Adopt the Lint-Only Python Profile or Record Why Python Is Not Tracked #356 settles before anything else touches .github/actions/validate/action.yml or the validator pin, since adopting the profile rewrites the Python step there.
• Keep the Override Prose in Step When a Theme Override Row Retires #353 and Drop the Nonexistent i18n Directory From the Repository Layout #357 depend on nothing and touch different files from Adopt the Lint-Only Python Profile or Record Why Python Is Not Tracked #356 and from each other.

State

Re-derive all of this.

• main is at Promote Develop to Main: Resync Carried Content With Hub 0378c78 #359's merge commit and develop at Resync Carried Instructions, Skills, and Intent Files With Hub 0378c78 #358's squash commit, with identical content. No pull requests are open.
• Resync Carried Instructions, Skills, and Intent Files With Hub 0378c78 #358's worktree, local branch, and remote branch were removed after GitHub confirmed the merge and both tips matched its head. The primary checkout is on develop, current, and clean, and is the only worktree.
• No release was dispatched. The latest release is 1.0.196, so Promote Develop to Main: Cover Outranked, Moved, and Retired Theme Overrides #354 and Promote Develop to Main: Resync Carried Content With Hub 0378c78 #359 are on main unreleased, by the maintainer's choice both times.
• Hub: a comment on pr_review.py Reads a Copilot File-Table Cell Naming Two Paths as One, Exiting 45 on Full Coverage ProjectTemplate#2251 adds the annotated-duplicate file-table row shape, with the maintainer's permission.

The parked decision queue

One issue carries the decision label, and it is put to the maintainer as this link is written:

1. Adopt the Lint-Only Python Profile or Record Why Python Is Not Tracked #356: adopt the lint-only Python profile (recommended, since the suites already exist and the carried rules assume it), or record a registry driftNote saying why Python is not tracked.

Asked and answered in session this round:

• This session took the resync rather than Keep the Override Prose in Step When a Theme Override Row Retires #353.
• Resync Carried Instructions, Skills, and Intent Files With Hub 0378c78 #358's coverage gate refused a Copilot file table naming all 29 changed files plus an annotated duplicate row. A second round stated no coverage. The maintainer approved the squash merge on a manual diff of the table against the changed files.
• Hub issues: approved. The pr_review.py shape went onto pr_review.py Reads a Copilot File-Table Cell Naming Two Paths as One, Exiting 45 on Full Coverage ProjectTemplate#2251. The .editorconfig "CRLF exceptions" plural was not filed, since hub #1992 made it plural deliberately.
• Promote Develop to Main: Resync Carried Content With Hub 0378c78 #359 was merged with no release, and the branch cleanup was approved.

What the last round did

• Resync Carried Instructions, Skills, and Intent Files With Hub 0378c78 #358 re-vendored 8 stale verbatim regions (AGENTS.md, GOVERNANCE.md) with carry.py apply-sections, refreshed 22 .github/skills files with carry.py apply, and applied the hub's line changes to CODESTYLE.md, WORKFLOW.md, .github/copilot-instructions.md, .editorconfig, and .gitattributes.
• Promote Develop to Main: Resync Carried Content With Hub 0378c78 #359 promoted it.
• Filed Adopt the Lint-Only Python Profile or Record Why Python Is Not Tracked #356 and Drop the Nonexistent i18n Directory From the Repository Layout #357.

What not to repeat

• Re-requesting Copilot to clear an unparseable file table. Round 2 on the same head carried no table and no coverage line, so it cleared nothing and cost a round. Diff the table against the changed files and take it to the maintainer instead, or wait on pr_review.py Reads a Copilot File-Table Cell Naming Two Paths as One, Exiting 45 on Full Coverage ProjectTemplate#2251.
• Treating the three intent advisories as work. .editorconfig-checker.json and version.json are flagged against hub commits that do not touch them, and cspell.json's hub change removes words Blog never carried. Each was verified this round, and none needs an edit.
• Filing the .editorconfig "CRLF exceptions" plural as a defect. Hub #1992 made it plural on purpose, so a carrier's own pin can keep the comment verbatim.
• Backgrounding a wait that checks pr_review.py status's exit code. status exits non-zero to report the gate verdict, so a loop under pipefail reads every pending round as a failure. Judge by the parsed digest line.

New learnings

• None beyond the entries above.