Skip to content

id: design: local-dev parity for the serverless edition (from #5681) #5866

Open

Description

@dezren39

Summary

Follow-on design ticket from #5681 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.

What this design must settle

Wrangler/Miniflare vs local sqld, fixtures, and the offline developer workflow for serverless storage.

Context from the parent

The parent design decides D1 vs Turso vs both for the serverless (Workers) edition and fixes the storage contract each backend must satisfy. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.

Decision record expected

Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.

Relations

Parent: #5681. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Nov 5, 2026
  2. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  4. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  5. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triage verdict (task 10268, lane code-g, 2026-11-05)

    Verdict: issue #5866 is live, well-scoped, and sits in a complete decomposition — with one real sequencing dependency, recorded below. No defect, no duplicate.

    Verified fresh this run:

    Routing: no follow-up queue task enqueued — the decomposition tickets are the follow-on work and already exist as open issues. Nothing needs Drew for the design to proceed in the order above.

    Issue #5866 stays open for the design work itself.

  6. developing-today commented on Nov 8, 2026

    @developing-today
    Contributor

    agent-note:v1 agent=repo-worker-code state=done task=12353 lane=code-f at=2026-11-08T04:56:00Z

    🤖 Agent note · triage complete

    Verdict: REAL AND CURRENT (verified fresh 2026-11-08, REST reads — the user-token GraphQL limit was already exceeded)

    Conversion: fix packet enqueued as task 12836 (dedupe repo-health:v1:fix:developing-today/code:issue:5866, kind small_fix) scoped to producing and landing that decision record, with the sequencing written into its acceptance. Per the triage doctrine, this triage completion does NOT close issue #5866 — it returns to the queue for real work, and closes only via the landed decision record (merged PR with a closing keyword) or an explicit verified closure.

  7. 14 remaining items

  8. added
    queue/claimedQueue worker lifecycle state
    and removed
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 8, 2026
  9. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · done

  10. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · correction

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)status:to-dotask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions