v0.9.0

All three plugins (product, architect, scalardb) are released together at 0.9.0.

Highlights

This release adds the product → architect integration: product output now feeds the architect pipeline through a documented, traceable contract instead of an ad-hoc handoff.

Added

• /product:design-architecture skill — synthesizes bounded contexts, API layers, the data model and NFRs into a runtime architecture (Mermaid container / critical-path / deployment-scaling views) and runs an evidence-driven technology-fitness assessment over Kong, ScalarDB, ScalarDB Analytics, ScalarDL (Adopt / Conditional / Reject + rationale). A ScalarDB/ScalarDL Adopt bridges to the architect ScalarDB pipeline. The product plugin now has 22 skills.
• Product → architect handoff contract (docs/design.md) — a single source of truth for how product output feeds the architect plugin, resolving previously dangling design.md references across four SKILL/rule files:
  • §1.3 — artifact mapping (per-output ID prefixes → define-requirements deliverables)
  • §1.4 — the by-design gaps product does not supply (physical DB inventory, actor/role/permission)
  • §1.5 — cross-plugin traceability write-back (FEAT-→FR- links, verbatim NFR- reuse)
  • §7 — canonical adaptation-engine spec

Changed

• /architect:define-requirements consumes product output — auto-detects reports/0*_*/, carries product IDs forward, uses tech-stack-fitness.md as the ScalarDB applicability prior, and writes FR-/NFR- nodes back to work/traceability.json.
• /architect:start and /architect:pipeline are product-aware — run handoff detection up front and route to the greenfield path with product reports fed in.
• /product:map-domains emits a coarse per-CTX- consistency hint (Strong/Eventual/TBD) that seeds architect's transaction-consistency classification.
• /architect:review-consistency checks cross-plugin traceability continuity.

Full changelog: CHANGELOG.md · 日本語: CHANGELOG_ja.md