Skip to content

id: F12.1 apply wiring — module install + schedules reconciliation #807

Closed

Description

@dezren39

Follow-up to the Phase 12 stack (PR #801, epic #534 D1-019).

What and why

id world apply currently reconciles grants, ceiling and profile against a live world, and id world diff reports drift. The remaining manifest fields are parsed but not yet applied over the wire: a module hash/source (install/compile) and schedules (set/cancel). The model already plans these steps; they need the server-side apply path.

Acceptance

  • id world apply installs (or compiles) the manifest module and applies schedule set/cancel, journaling each step.
  • A manifest naming only a module + schedules applies idempotently.

Acceptance criteria

  • The body's ## Acceptance bullets hold: id world apply installs (or compiles) the manifest module and applies schedule set/cancel, journaling each step.
  • A manifest naming only a module + schedules applies idempotently (second apply is a no-op).
  • id world diff after apply reports no drift for module or schedules.

Activity

  1. added
    kind/featureNew feature or capability request
    priority/lowNice to have; do when convenient
    effort/lLarge: multi-day or open-ended; expect staged check-ins
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 26, 2026
  2. dezren39 commented on Oct 26, 2026

    @dezren39
    MemberAuthor

    Intake review

    Related: Phase 12 stack PR #801 (merged); epic #534 (D1-019); siblings #805 (F12.11) and #806 (F12.13). PR #860 touched world apply reporting for #818, not this wiring. No merged PR resolves this (verified 2026-10-26).

    Notes: The body already had an ## Acceptance list; the criteria above restate it in the standard section so queue/triage tooling can find it. Effort l: server-side apply path for module install/compile plus schedules reconciliation.

    Risks: Apply-path changes are world-mutating; idempotency and journaling are the safety properties to test first.

    Suggested approach: Extend the existing grants/ceiling/profile apply path with module and schedule steps, each journaled, with a diff-after-apply test.

  3. added
    nextOrg Project gate: queued next — orchestrator adds to the board
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Oct 27, 2026
  4. 358 remaining items

  5. added
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Oct 29, 2026
  6. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · parked

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

    @dezren39
    MemberAuthor

    Agent note — verified merge-ready except infra clippy + the merge-queue stall; parked

    Queue task 2661 resumed by Lane B. PR #1820 verified fresh at 569abd29: MERGEABLE, all review threads resolved (7/7), latest Codex summary at this head reports no findings. CI: every check SUCCESS except clippy-lint (and its aggregate nix flake check).

    Lane B re-checked the clippy failure from the run log (run 40894646360, 20:06Z attempt): it is infrastructure, not code — repeated HTTP error 418 downloads with “GitHub Actions Cache throttled Magic Nix Cache” and a Twirp ResourceExhausted rate-limit error. The PR diff does not touch src/tags.rs (the on-main clippy item in #2401). A --failed rerun has been requested (attempt 4 now in progress).

    Resume: when the rerun is green and the merge-queue stall #2403 is fixed, enqueue PR #1820, verify it merges, and complete task 2661.

  9. 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
    on Oct 29, 2026
  10. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · parked

  11. dezren39 commented on Oct 30, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · agent-note:v1 · done — PR merged

    Queue task 2661 completed by Lane C, 2026-10-30T01:04Z. PR #1820 (id(world): wire manifest apply — module install + schedules over the wire) MERGED at 2026-10-30T01:00:10Z, merge commit 17c4a0de5a34b7b919312c4b1fcf7766b3006657, after the merge-queue stall (#2403) was fixed. The PR body says "Closes the apply-wiring gap in #807" (not the auto-close keyword), so this issue is being closed manually with that evidence. The pre-existing clippy debt at src/tags.rs:1484,1499 remains tracked separately in #2401.

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-inskind/featureNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addednextOrg Project gate: queued next — orchestrator adds to the boardpriority/lowNice to have; do when convenient

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions