id: F12.4 provider registry — capabilities as manifest + provider components #1061

Activity

1. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   source/humanFiled directly by a humanFiled directly by a human

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   on Oct 27, 2026
2. developing-today commented on Oct 27, 2026

   

   developing-todayBot

   on Oct 27, 2026 – with developing.today

   Contributor

   More actions

   CODE-205
3. dezren39

   added

   nextOrg Project gate: queued next — orchestrator adds to the boardOrg Project gate: queued next — orchestrator adds to the board

   effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-ins

   on Oct 27, 2026
4. github-actions

   assigned

   dezren39

   on Oct 27, 2026
5. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   on Nov 1, 2026
6. dezren39 commented on Nov 1, 2026

   

   dezren39

   on Nov 1, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane B shift
   • Session / ID: queue task 2332 (triage)
   • Found via: queue claim
   • Task: Triage id: F12.4 provider registry — capabilities as manifest + provider components #1061 (F12.4 provider registry) against current main: verify the catalog is still hard-coded, check the pinned prerequisite id(world): default ceiling is the whole catalog, so F12.4 registry additions would widen every world #838, and route.
   • Expectation: s — verdict with fresh-HEAD citations, follow-up route recorded, labels synced.
   • Links: queue task 2332
7. dezren39 commented on Nov 1, 2026

   

   dezren39

   on Nov 1, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane B shift
   • Session / ID: queue task 2332 (triage)
   • Found via: queue claim
   • Task: Triage verdict for id: F12.4 provider registry — capabilities as manifest + provider components #1061 (F12.4 provider registry — capabilities as manifest + provider components).
   • Expectation: Verdict with fresh-HEAD citations + follow-up route — both delivered below.
   • Links: slice-1 fix task 4880 (queued, gated on id(world): default ceiling is the whole catalog, so F12.4 registry additions would widen every world #838); packet: hidden_files/packet-1061-code-fix.json

   Triage verdict: CONFIRMED — catalog is hard-coded, no registry exists; route is a gated slice 1

   Evidence (fresh, current main b56ccda5c, 2026-10-31 21:06 CDT, laptop primary origin/main):

   • pkgs/id/src/world_caps.rs (~L85): the capability catalog is a hard-coded pub const CATALOG: &[&str] of 17 names (time.now … RocText); is_known() / catalog_names() read the const directly.
   • grep -rni 'ProviderRegistry|provider_registry|provider manifest|struct Provider' pkgs/id/src → no matches: no manifest type, no registry.
   • The id(world): default ceiling is the whole catalog, so F12.4 registry additions would widen every world #838 hazard is live at the same HEAD: pkgs/id/src/world/core.rs:95 defaults caps_ceiling to catalog_names(); world_caps.rs:129 documents the catalog set as "the default server and world ceiling"; the test at world_caps.rs:868 is literally the_default_ceiling_is_the_whole_catalog.

   Dependency state: prerequisite #838 (priority/high, kind/security) is still OPEN — the pinned "fix first" has not landed. Dependencies F11.10/F11.13 are stated done in the issue; nothing else blocks.

   Route — sliced, because the full F12.4 is effort/l:

   • Slice 1 enqueued as queue task 4880 (kind small_fix, packet packet-1061-code-fix.json), hard-gated on id(world): default ceiling is the whole catalog, so F12.4 registry additions would widen every world #838: at claim, if id(world): default ceiling is the whole catalog, so F12.4 registry additions would widen every world #838 has not landed, block naming the dependency. Slice 1 itself: manifest type (name, version, argument schema, bounds, required scope, default ceiling) + registry populated with the existing 17 capabilities; catalog derived from the registry; ledger, compile gate, and CLI caps reading the registry; zero behavior change, proven by the identical 17-name catalog and the existing pkgs/id tests.
   • Slice 2 (not yet enqueued): the issue's exit proof — a test provider added without editing world.rs, appearing in caps, the ceiling, and the compile gate. Enqueue it when slice 1 lands; filing it now would invite a worker to build it on the hard-coded catalog.

   This issue stays open (tracker for both slices) with queue/queued for task 4880.
8. 112 remaining items

   Load more
9. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 4, 2026
10. dezren39 commented on Nov 4, 2026

    

    dezren39

    on Nov 4, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-a
    • Session / ID: task 8477
    • Found via: queue claim
    • Task: task 8477 (triage for issue id: F12.4 provider registry — capabilities as manifest + provider components #1061) assigned to execution lane opencode; handed off to the laptop claimant — this lane does not work it directly
    • Expectation: claimant launches the bound opencode session; if the lease expires unlaunched, task 8477 returns to the queue
    • Links: issue id: F12.4 provider registry — capabilities as manifest + provider components #1061
11. dezren39 commented on Nov 4, 2026

    

    dezren39

    on Nov 4, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-o
    • Session / ID: task 8477
    • Found via: queue claim
    • Task: Triage of issue id: F12.4 provider registry — capabilities as manifest + provider components #1061 (id F12.4 provider registry) handed off to the opencode execution lane; the laptop claimant launches the bound session.
    • Expectation: Claimant launches the bound opencode session for task 8477; if the lease expires unlaunched, task 8477 returns to the queue. Note task 8477 is at attempt 22 of 24.
    • Links: task 8477 (repo-health-code-pilot queue)
12. dezren39

    added

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

    queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

    on Nov 4, 2026
13. dezren39 commented on Nov 4, 2026

    

    dezren39

    on Nov 4, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-h
    • Session / ID: task 8477
    • Found via: queue claim
    • Task: Handing task 8477 (triage of issue id: F12.4 provider registry — capabilities as manifest + provider components #1061, F12.4 provider registry) to the opencode execution lane; the laptop claimant launches the bound opencode session. Fresh check this shift: issue id: F12.4 provider registry — capabilities as manifest + provider components #1061 is OPEN with claim labels in sync and no hard-stop labels. CAP RISK: task 8477 is at attempt 24/24 — if this lease lapses unbound by the claimant, the task becomes unclaimable without a cap raise.
    • Expectation: effort/l item; done = triage verdict posted on issue id: F12.4 provider registry — capabilities as manifest + provider components #1061 with a routed follow-up.
    • Links: branch queue/8477-1061-provider-registry (laptop worktree preserved)
14. dezren39

    added

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    and removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 5, 2026
15. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: fleet monitor
    • Session / ID: task 8477 (repo-fleet-monitor run 2026-11-05T15:45:48Z)
    • Found via: monitor reconciliation (Duty 1 claim/label divergence repair)
    • Task: Claim evaporated: task 8477 is queued and unclaimed in repo-health-code-pilot, but this issue still carried claimed labels. Labels reset to the truth (queue/queued + status/needs-triage). Checkpoint stage at evaporation: handed_off.
    • Expectation: The next lane claim picks task 8477 up from the queued state and posts a fresh pickup note.