Frontier lane kickoff — Opus 5 + Sol + Fable on @frontier dist-tag

[BaseInfinity]

What

Set up the Frontier lane: bleeding-edge models, opt-in consumers, separate dist-tag.

Lane spec

	Reliable (@latest)	Frontier (@frontier)
Version	1.100.x	2.0.0-frontier.N
Builder	Opus 4.6[1m] max	Opus 5 high
First brain	GPT-5.5 xhigh (→ Sol, see #715)	GPT-5.6 Sol high
Second brain	Fable high	Fable high
Install	npm i agentic-sdlc-wizard	npm i agentic-sdlc-wizard@frontier
Semver	^1.100.0 never picks up 2.x	Explicit opt-in only

Steps

• Branch from v1.100.0: frontier/kickoff
• Bump version to 2.0.0-frontier.0
• Update model pins throughout (Opus 5, Sol, Fable)
• Fix release.yml to accept --tag frontier (release.yml: bare npm publish will steal @latest on frontier tags #713 — blocker)
• Tag and publish with npm publish --tag frontier
• Verify: npm view agentic-sdlc-wizard dist-tags shows both latest and frontier
• Document in README: how to install frontier, what it means, how to switch back

Blocked by

• release.yml: bare npm publish will steal @latest on frontier tags #713 — release.yml must support dist-tag parameter before first frontier publish

Related

• Two flavors: Workhorse (opus-4-6[1m] + GPT-5.5, escalate to Fable/5.6 when hard) and Frontier (Opus 5 + Fable + Sol) #707 — the two-flavor design this implements
• Set the Opus 4.6 line in stone: name the fallback, prove it with a canary, and cut release/opus-4.6 only if the canary says to #689 — the Opus 4.6 line-in-stone work (Reliable side)
• Cut and publish v2.0.0 — the release itself, which no issue on this milestone covers #673 — v2.0.0 graduation criteria (frontier → latest promotion requires proven consumption)