sso-landing-figma-code-parity

ARCHIVED

The first SSO–Figma linkage established the correct file key, `@figma` tags on major surfaces, and `docs/figma-source.md`. The **landing** experience is still a dense mix of inline UI, nested symbols, and optional Code Connect; without a structured pass, divergences and missed componentization stay invisible. A second pass inventories the landing page first, flags Figma vs code component candidates, and drives small, explicit creations in Figma and/or the prototype so the source of truth stays actionable.

STAGES

  1. proposal05-08
  2. requirements05-08
  3. design05-08predates the Figma as-is + proposed pair
  4. tasks05-08
  5. build—
  6. archived—

CAPABILITY

  • simple-seed-organizer-design-system3 requirements

OUTCOMES — 13 OF 13 DONE, AND NOT MAPPABLE TO A CAPABILITY

This change organises its tasks by workstream rather than as spec scenarios, so progress cannot be split per capability.

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-05-08
    • docs(openspec): archive sso-landing-figma-code-parity (2026-05-08)

History read from a manifest built at 2026-09-30 (09e7bcc).

0 pull requests, found by commits touching the change folder · 1 commit(s) carry no pull request number