feat(onboarding): rewrite overture score Stages 1-2

[jeonghun-jj-lee]

Summary

Implements #435 — rewrites the overture score from a 6-stage QOC-specific interview to a 2-stage generic orientation + intent capture.

Changes

• scores/overture/SCORE.md rewritten (v1 → v2):

  • Stage 1 (orientation): Introduces Amicode as a general agentic coding and research studio — not solely QOC. Collects name naturally. No experience-level branching.
  • Stage 2 (intent): Multi-select (multiple: true) with exactly 3 options: "General coding and software development", "Research", "Exploring". Intent recorded as slug array on profile entity.
  • Old stages (platforms, environment, devices, goals, handoff) removed — they move to later slices.

• opencode-plugin/onboarding.ts: ENTITY_FIELDS.profile extended with "intent" field

• Golden parity files regenerated (compile-chained.md, router-section.md)

• Existing tests updated: compiler test and overture_routing test reference the new stage id (orientation not identity)

Tests

18 new tests in test/scores/overture_rewrite.test.ts:

• Score loads and compiles (standalone + chained)
• New stage structure verified (orientation, intent; old stages absent)
• Content assertions: general framing, no experience branching, multi-select
• Intent entity field accepted by sanitizePayload/appendOnboardingEvent
• Resume logic instructions present

Closes #435

Summary by CodeRabbit

• New Features

  • Streamlined onboarding into orientation and intent steps.
  • Users can provide their name and select multiple intents.
  • Onboarding now transitions directly into a normal session after intent selection.
  • Updated guidance supports research, general users, and developers.
  • Estimated onboarding time is now 2–3 minutes.

• Bug Fixes

  • Improved intent handling, persistence, resuming, and onboarding transitions.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4bc4b772-9647-4940-b439-551bbf3515c5

📥 Commits

Reviewing files that changed from the base of the PR and between 13fbffc and a5a7784.

📒 Files selected for processing (7)

• packages/extension/opencode-plugin/onboarding.ts
• packages/extension/scores/overture/SCORE.md
• packages/extension/test/scores/compiler.test.ts
• packages/extension/test/scores/golden/compile-chained.md
• packages/extension/test/scores/golden/router-section.md
• packages/extension/test/scores/overture_rewrite.test.ts
• packages/extension/test/scores/overture_routing.test.ts

---

📝 Walkthrough

Walkthrough

Overture now uses orientation and multi-select intent stages. It records name and intent profile data, completes onboarding after intent, and defers research-specific questions to the pulse-designer flow. Tests cover compilation, routing, resume behavior, sanitization, and event persistence.

Changes

Overture onboarding flow

Layer / File(s)	Summary
Orientation and intent definition packages/extension/scores/overture/SCORE.md, packages/extension/opencode-plugin/onboarding.ts	Overture v2 collects a name and normalized multi-select intent values. Profile onboarding retains intent, then completes onboarding before normal session continuation.
Chained compilation and routing packages/extension/test/scores/golden/compile-chained.md, packages/extension/test/scores/compiler.test.ts, packages/extension/test/scores/golden/router-section.md, packages/extension/test/scores/overture_routing.test.ts	Golden outputs and routing expectations use the orientation and intent stages with updated entry-card content.
Overture behavior validation packages/extension/test/scores/overture_rewrite.test.ts	Tests cover score discovery, stage content, question protocol, resume behavior, intent sanitization, event persistence, and standalone or chained compilation.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related issues

• #438 — The rewrite replaces the planned environment, device, goals, and handoff stages with orientation and intent.

Suggested reviewers: aarontrowbridge

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jeonghun-jj-lee/435-overture-score-rewrite

---

_{Comment @coderabbitai help to get the list of available commands.}