Context
This is the lane-selection part of #14230's existing contributor journey. Following CONTRIBUTING.md on 7 November still names 13.2 as the next release and links closed milestone 9; current ROADMAP.md names 13.4 and its live milestone. The starter-label routes currently lead to held work, while the guide promises “there is always a way in” and offers no question route at that step. These are observations about the documented route, not a claim about how outside contributors arrive or why they leave.
The Problem
A reader who has launched the engine needs a current release context and a next step when the listed tickets are already claimed or unsuitable. Merely replacing a release number leaves that second gap.
The Architectural Reality
CONTRIBUTING.md §3 owns the route. ROADMAP.md owns current release scope and links its milestone; GitHub's existing Q&A category (q-a, public URL returned 200) owns the question door. No runtime or issue-assignment service change is needed. Prescription checked: CONTRIBUTING.md owns this guidance; changing the claim responder or Skills would not correct the stale release pointer and missing question route.
Design authority: #14230 facet 3 calls for wiring the existing Q&A door into a try-a-lane contribution path; #19105 requires linking the roadmap rather than copying its facts.
The prior decisions remain binding: #19201 rejected filtering these lists as a collision fix; #19194 deliberately permits unassigned PRs and retains first-approve-worthy semantics. Both stay unchanged.
The Fix
Update this one guide section as a complete return route: follow the roadmap for release scope, retain the first-time/returning progression and existing claim policy, link Q&A when listed work is held or unsuitable, and require a new issue for a genuinely new problem rather than for finding existing work.
| Target surface |
Source of authority |
Behavior |
Fallback |
Docs |
Evidence |
| Release pointer |
ROADMAP.md |
Follow its current milestone |
The roadmap remains the durable entry |
CONTRIBUTING.md §3 |
Read current roadmap and rendered link |
| Starter-list return route |
#14230 facet 3 |
Existing label lists and first-time progression remain |
Existing Q&A category when nothing fits |
CONTRIBUTING.md §3 item 1 |
Live queries/category and rendered first step |
| Claim and new-issue wording |
#19194, #19201, #18999 |
Keep claim paragraph and label URLs; new problems still need approval |
Existing responder/maintainer path |
CONTRIBUTING.md §3 items 2–3 |
Base-relative comparison |
Acceptance Criteria
Out of Scope
Starter-issue curation or reassignment; the retired #18985 event; claim-bot behavior; Skills audience/private-tool compatibility; instruction-file defaults and maintainer-home loading. Those remaining onboarding obligations stay on #14230.
Avoided Traps
The initial uncommitted draft repeated #19201's rejected list filter and weakened #19194's claim rule. The closed-state sweep caught both; those draft changes were removed before publication. A fixed 13.4 link would repeat the next-release drift, so the guide follows the existing roadmap instead.
Related
Parent: #14230. Closed #19105 delivered the September roadmap pointer, not today's release context. Closed #18999 owns the delivered setup loop; #18985's event ACs remain retired.
Live latest-open + closed sweep: latest 20 open plus closed CONTRIBUTING/lane/good-first searches, including #19105/#18999/#19201/#19194/#19202 bodies and decisions, read at 06:14–06:16 UTC on 7 November; no open equivalent. A2A all-state in-flight scan found only my existing #14230 claim. MC symptom sweep found claim/progression history. Own-assignment sweep: #14230 is the parent; the other four open assignments are different surfaces. Complete file census of 19 open PRs found no CONTRIBUTING.md overlap.
Ownership: Euclid is already implementing this return-route slice under #14230; self-assigned for this leaf. This is not a new curated starter slot.
Decision Record impact: none
Origin Session ID: f2ae0cfb-5a79-458d-9fa6-ffdca5470395
Retrieval Hint: "CONTRIBUTING next release stale milestone starter work already claimed Q&A return route"
Context
This is the lane-selection part of #14230's existing contributor journey. Following
CONTRIBUTING.mdon 7 November still names 13.2 as the next release and links closed milestone 9; currentROADMAP.mdnames 13.4 and its live milestone. The starter-label routes currently lead to held work, while the guide promises “there is always a way in” and offers no question route at that step. These are observations about the documented route, not a claim about how outside contributors arrive or why they leave.The Problem
A reader who has launched the engine needs a current release context and a next step when the listed tickets are already claimed or unsuitable. Merely replacing a release number leaves that second gap.
The Architectural Reality
CONTRIBUTING.md§3 owns the route.ROADMAP.mdowns current release scope and links its milestone; GitHub's existing Q&A category (q-a, public URL returned 200) owns the question door. No runtime or issue-assignment service change is needed. Prescription checked:CONTRIBUTING.mdowns this guidance; changing the claim responder or Skills would not correct the stale release pointer and missing question route.Design authority: #14230 facet 3 calls for wiring the existing Q&A door into a try-a-lane contribution path; #19105 requires linking the roadmap rather than copying its facts.
The prior decisions remain binding: #19201 rejected filtering these lists as a collision fix; #19194 deliberately permits unassigned PRs and retains first-approve-worthy semantics. Both stay unchanged.
The Fix
Update this one guide section as a complete return route: follow the roadmap for release scope, retain the first-time/returning progression and existing claim policy, link Q&A when listed work is held or unsuitable, and require a new issue for a genuinely new problem rather than for finding existing work.
ROADMAP.mdCONTRIBUTING.md§3CONTRIBUTING.md§3 item 1CONTRIBUTING.md§3 items 2–3Acceptance Criteria
ROADMAP.mdfor the current release/milestone instead of fixing 13.2/milestone 9 in its prose.Out of Scope
Starter-issue curation or reassignment; the retired #18985 event; claim-bot behavior; Skills audience/private-tool compatibility; instruction-file defaults and maintainer-home loading. Those remaining onboarding obligations stay on #14230.
Avoided Traps
The initial uncommitted draft repeated #19201's rejected list filter and weakened #19194's claim rule. The closed-state sweep caught both; those draft changes were removed before publication. A fixed 13.4 link would repeat the next-release drift, so the guide follows the existing roadmap instead.
Related
Parent: #14230. Closed #19105 delivered the September roadmap pointer, not today's release context. Closed #18999 owns the delivered setup loop; #18985's event ACs remain retired.
Live latest-open + closed sweep: latest 20 open plus closed CONTRIBUTING/lane/good-first searches, including #19105/#18999/#19201/#19194/#19202 bodies and decisions, read at 06:14–06:16 UTC on 7 November; no open equivalent. A2A all-state in-flight scan found only my existing #14230 claim. MC symptom sweep found claim/progression history. Own-assignment sweep: #14230 is the parent; the other four open assignments are different surfaces. Complete file census of 19 open PRs found no
CONTRIBUTING.mdoverlap.Ownership: Euclid is already implementing this return-route slice under #14230; self-assigned for this leaf. This is not a new curated starter slot.
Decision Record impact: none Origin Session ID: f2ae0cfb-5a79-458d-9fa6-ffdca5470395 Retrieval Hint: "CONTRIBUTING next release stale milestone starter work already claimed Q&A return route"