Session Handoff [auto-1899]: Reconcile VSCode-Server-DotNetCore in the Hub After Its Resync #3125

Next steps, in priority order

1. Bring the hub's records for VSCode-Server-DotNetCore up to its resynced state, per Reconcile VSCode-Server-DotNetCore in the Hub After Its Resync #1899. That repository's resync is merged to its develop and promoted to its main, its ground-truth branch, which now carries only the merge-bot-pull-request.yml, publish-release.yml, and test-pull-request.yml stubs. Re-check that live before editing. Done looks like a single pull request to develop carrying Closes on promotion: #1899 that:
   • deletes the stale driftNotes entry for VSCode-Server-DotNetCore in registry/repos.json, the one saying a separate publish-docker-readme-task serves the Hub overview, after confirming its main publish-release.yml calls the hub's publish-docker-readme-task.yml and keeps no local copy,
   • ticks the VSCode-Server-DotNetCore items still open in docs/reusable-workflows.md (Stage 4 "vanilla Docker only", plus the get-version-task.yml and publish-docker-readme-task.yml items), each only where the live main evidence holds and with that evidence named the way the ticked items beside them name theirs, and regenerates reports/workflow-reuse.md in the same change,
   • re-runs spec/audit.py VSCode-Server-DotNetCore against main and commits the refreshed reports/vscode-server-dotnetcore/audit.md.
2. Report what Reconcile VSCode-Server-DotNetCore in the Hub After Its Resync #1899 says about Carry the code-review skill bootstrap to seven repos whose Copilot reviews never state coverage #1815 on Carry the code-review skill bootstrap to seven repos whose Copilot reviews never state coverage #1815 itself: a comment noting that this repository's coverage symptom is gone, with the evidence Reconcile VSCode-Server-DotNetCore in the Hub After Its Resync #1899 cites. Carry the code-review skill bootstrap to seven repos whose Copilot reviews never state coverage #1815 stays open, since it covers other repositories.

External blockers

None known. An audit finding that turns out to need a change in VSCode-Server-DotNetCore itself is that repository's work, not this lane's, so file it there rather than editing it.

Internal dependencies

• The ticks and the regenerated report depend on the live main read in step 1, since an item is ticked from evidence rather than from Reconcile VSCode-Server-DotNetCore in the Hub After Its Resync #1899's account of it.

State

• No branch, worktree, or pull request exists for this lane yet.
• Reconcile VSCode-Server-DotNetCore in the Hub After Its Resync #1899 has no comments, no open pull request names it, and nothing in origin/main..origin/develop names it.
• reports/vscode-server-dotnetcore/ was last refreshed before the resync.
• Re-derive all of this, plus VSCode-Server-DotNetCore's main and develop heads, before acting.

The parked decision queue

Zero parked decisions.

What the last round did

The unattended picker created this lane for #1899.

What not to repeat

Nothing yet.

New learnings

None yet.