seed-packet-crud-and-custom-fields

ARCHIVED

The seed packet entry flow captures what's printed on a packet, but there's no way to control which canonical fields are relevant to a specific packet, and no structured place to record the user's own observations or corrections to printed instructions. Right now, personal knowledge lives in the single `notes` blob alongside AI-extracted packet content, with no distinction between "what the packet says" and "what I actually do."

STAGES

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

CAPABILITIES — 4 IN ONE CHANGE

  • seed-field-visibility4 requirements
  • seed-instruction-annotations4 requirements
  • seed-personal-notes4 requirements
  • simple-seed-organizer-design-system3 requirements

OUTCOMES — 34 OF 37 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-21 · 1 pull request
    • #168chore(openspec): archive merged hub and snap-issue changes

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

1 pull request, found by commits touching the change folder