Skip to content

pkgs/id crate split — step 6: extract id-directory, then id-web #4409

Open

Description

@dezren39

Crate split step 6 of 7 — from the merged design

Design: doc/2026-11-01T16-53-00Z_design_id_crate_split/2026-11-01T16-53-00Z_design_id_crate_split.md (merged as PR #3824, 2026-11-01). Tracking issue: #3447. Program: #3195 (build-time review; Drew's priority order — shipped-binary runtime performance first, build time second).

Scope (design, verbatim intent)

Design step 6: id-directory, then id-web. Web is a pure consumer and the safest large extraction; it goes late for that reason.

Current state

Not started.

Dependency — do not start early

Step 5 (id-worlds) merged. If this step's queue task is claimed before the dependency lands, park it with that reason.

Fuel canary (non-negotiable, every step): the FUEL_BUDGETS tables in pkgs/id/src/sandbox.rs must be byte-identical after this step; the fuel-tables diff is committed in the step PR. Any drift means behaviour changed and the step stops. Full verification protocol: design note §"Verification protocol".

Verification protocol (design, every step): one PR; main green throughout; the shipped binary is built by the same Nix derivations at every point (all three entry points: the sub-flake's id-web and id-lib, and default.nix); test count matches or exceeds the step-0 baseline with any delta named; cold check-build timing recorded on #3447 and #3195 with the laptop load noted. Heavy builds run under ~/tools/fleet-build-lock on the laptop (max 2 concurrent, CARGO_BUILD_JOBS = half the cores) — there is no load gate (Drew, 2026-11-02).

Acceptance criteria

  • The extraction lands as its own PR off current main, sequenced after its predecessor step (see Related).
  • The id facade re-exports the extracted crate so existing call sites compile unchanged in behavior.
  • CI green on the PR (workspace build + the id test suites), including the F11.10 production-line guard.
  • This issue closes with the merge; the next step's issue is unblocked in sequence.

Activity

  1. added
    kind/performancePerformance problem or optimization
    priority/highImportant and time-sensitive
    queue/queuedHas a queued task in the Supabase agent queue
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 2, 2026
  2. dezren39 commented on Nov 2, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    event: parked
    task: 6295
    worker: repo-worker-code (lane A)
    note: Dependency gate checked fresh: Step 5 (#4408, extract id-worlds) has NOT landed — pkgs/id/crates/ on current main contains only id-core (Step 1), no step-5 PR has merged, and the step-5 fix task 6302 is still QUEUED. This packet directs: if claimed before the dependency lands, park with that reason; do not start early. Parked 30m. (Step 7, #4411 / task 6303, is likewise parked behind this step.) Resume: #4408 closed / step-5 PR merged -> start Step 6 (extract id-directory, then id-web) with the FUEL_BUDGETS canary; builds under ~/tools/fleet-build-lock per the packet build policy — load is not a park reason.

  3. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    status/parkedDeliberately paused with a recorded resume condition
    on Nov 2, 2026
  4. 125 remaining items

  5. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent-note:v1
    event: picked_up -> parked
    task: 6295 (small_fix; repo-health-code-pilot; worker repo-worker-code; lane ec118cad-0fd3-4652-91c4-27432f2f2efd — OpenChamber scheduled lane)
    by: repo-worker-code

    Fresh revalidation at 2026-11-04T13:44Z: #4409 is OPEN and has no hard-stop labels. Prerequisite #4408 remains OPEN and parked; predecessor #4407 and chain root #4406 are also OPEN. The packet explicitly forbids starting step 6 before #4408 lands, so no branch/worktree/code was created.

    Parked for 4 hours or until #4408 lands. On resume, revalidate #4406 → #4407 → #4408 and current main before implementation.
    labels: queue/parked + status/parked; work/assigned retained; queue/claimed + status/in-progress removed.

  6. added
    queue/claimedQueue worker lifecycle state
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 4, 2026
  7. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  8. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    queue/claimedQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 4, 2026
  9. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

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)effort/lLarge: multi-day or open-ended; expect staged check-insexpediteImportant - do this very soon, before anything not expeditedkind/performancePerformance problem or optimizationmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivequeue/claimedQueue worker lifecycle statesource/creatorFiled by the new-issue-creator jobstatus/in-progressQueue worker lifecycle statetask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions