@openrig/cli 0.5.4 → 0.5.6

package/daemon/context-packs/world/install/manifest.yaml

@@ -1,125 +0,0 @@
-# world/install — the OpenRig world install as ONE composable atom graph (OPR.0.5.3.5).
-# COMMITTED SOURCE: projected verbatim into the builtin context-pack root at package time
-# (scripts/generate-context-packs.mjs stamps the version line); validated through the daemon's
-# own manifest parser at build. Atoms are ADDRESSES into the parent files below — never copied
-# prose — so FRESH/HANDOVER/POST-COMPACTION compose the same bytes (mini-req 5 by construction).
-# Order is load-bearing (the walk manifest's rationale: world -> self -> purpose opens the hole
-# the ontology fills; a-competent-turn is the puzzle assembled from pieces already in hand).
-# The POST-COMPACTION selection is the measured 2026-08-21 re-prime: ontology + capability
-# surface + source map + competent-turn (width restore, not identity replay). The +catch-up
-# material (RECAP) is SEAT-SCOPED by Q2-Amendment 1 and joins from the seat tree at compose
-# time: the `recap` atom below is an ADDRESS into the seat tree (seat:RECAP.md, written by the
-# outgoing occupant beside LEARNED) — the pack declares the JOIN, never the bytes. The algebra
-# composes handover-tagged atoms into both HANDOVER and POST-COMPACTION; a missing recap
-# FAILS LOUD, never a silently thinner walk.
-name: world-install
-version: "0.5.4"
-purpose: "The OpenRig world install as one composable content graph: the FRESH onboarding walk, the HANDOVER walk (+ the seat-scoped RECAP joined by address from the seat tree), and the POST-COMPACTION width re-prime all compose from the same eight parent files."
-files:
-  - path: 01-world-from-primitives.md
-    role: world
-    summary: "The gentle first layer: the world built from its primitives."
-  - path: 02-permission-self-sleep.md
-    role: world
-    summary: "The self layer: permission, self, sleep."
-  - path: 03-what-this-is-for.md
-    role: world
-    summary: "The purpose layer: what this world is for."
-  - path: 04-ontology.md
-    role: world
-    summary: "The ontology: identity, ontology, laws, actors — the deep frame (kept LARGE by ruling D2)."
-  - path: 05-harness-power-use.md
-    role: world
-    summary: "Harness power use: what the harness can do when driven well."
-  - path: 06-a-competent-turn.md
-    role: world
-    summary: "A competent turn: the puzzle assembled from the pieces; comes last of the content."
-  - path: what-you-can-do.md
-    role: world
-    summary: "The capability surface: affordance width (the dimension compaction measurably loses)."
-  - path: reference-material.md
-    role: world
-    summary: "The source map: where to look (terrain)."
-atoms:
-  - id: world-from-primitives
-    address: "01-world-from-primitives.md"
-    taxonomy: world
-    situations: [fresh]
-    purpose: depth
-    runtime: any
-    order: 10
-    priority: core
-  - id: permission-self-sleep
-    address: "02-permission-self-sleep.md"
-    taxonomy: world
-    situations: [fresh]
-    purpose: depth
-    runtime: any
-    order: 20
-    priority: core
-  - id: what-this-is-for
-    address: "03-what-this-is-for.md"
-    taxonomy: world
-    situations: [fresh]
-    purpose: depth
-    runtime: any
-    order: 30
-    priority: core
-  - id: ontology
-    address: "04-ontology.md"
-    taxonomy: world
-    regions: [identity, ontology, laws, actors]
-    situations: [fresh, post-compaction]
-    purpose: depth
-    runtime: any
-    order: 40
-    priority: core
-  - id: what-you-can-do
-    address: "what-you-can-do.md"
-    taxonomy: world
-    regions: [affordances]
-    situations: [post-compaction]
-    purpose: width
-    runtime: any
-    order: 42
-    priority: core
-    probe:
-      prompt: "What can I do here?"
-      expect: "The seat uses the installed context surface to recover affordance width; naming a fact or saying that a file exists does not count."
-      expectedPatterns:
-        - 'rig context (?:get|profile)\b'
-  - id: reference-material
-    address: "reference-material.md"
-    taxonomy: world
-    regions: [terrain]
-    situations: [post-compaction]
-    purpose: width
-    runtime: any
-    order: 44
-    priority: core
-  - id: harness-power-use
-    address: "05-harness-power-use.md"
-    taxonomy: world
-    regions: [affordances]
-    situations: [fresh]
-    purpose: width
-    runtime: any
-    order: 50
-    priority: core
-  - id: a-competent-turn
-    address: "06-a-competent-turn.md"
-    taxonomy: world
-    situations: [fresh, post-compaction]
-    purpose: width
-    runtime: any
-    order: 60
-    priority: core
-  - id: recap
-    address: "seat:RECAP.md"
-    taxonomy: lore
-    regions: [history]
-    situations: [handover]
-    purpose: width
-    runtime: any
-    order: 70
-    priority: core

package/daemon/specs/agents/shared/skills/core/attention-queue/SKILL.md

@@ -1,264 +0,0 @@
----
-name: attention-queue
-description: Coordination primitive for OpenRig. Per-agent queue files tracking in-flight work with explicit state transitions + handoff semantics + cross-agent composition. Prevents memory-loss drops; surfaces stalls mechanically; closes the feedback loop on handed-off work. Applied liberally by every agent on every kernel-supervised rig; composed views serve human attention, orch pod-load, rig pending-work.
-status: L4-insight
-authored-by: advisor-peer-observer@your-rig
-date: 2026-04-13
-cited-captures:
-  - improvements-inbox.md 2026-04-13T12:54:50Z — broadcast primitive RSI (same batching-by-theme cluster)
-  - Mission 4 cmux stall (2026-04-13 midday) — packet-design + queue-for-cross-rig coordination
-metadata:
-  cli_surfaces_referenced:
-    - chatroom
-    - send
-  openrig:
-    stage: factory-approved
-    sibling_skills:
-      - queue-handoff
-      - workflow-runtime
-      - watchdog
-      - refocus
-      - looping-workflows
-      - intake-routing
-      - human-in-the-loop
-      - dispatching-parallel-agents
-      - subagent-driven-development
-      - control-plane-capabilities
-      - status-not-chat-orchestrator
-      - control-plane-queue
-      - control-plane-watchdog
-      - control-plane-workflows
-      - control-plane-delivery-loop
-      - control-plane-rollout-manager
----
-
-# Attention queue
-
-Use this skill when coordinating work that must survive compaction, cross-agent handoffs, or multi-hour stall detection. Applies when you'd otherwise narrate status to chat or rely on memory for pending items.
-
-## Live protocol override
-
-Current live routing protocol:
-
-- **Known target / explicit owner that should wake now**: `rigx queue handoff <destination> "<body>" --type handoff --urgency soon`
-- **Passive durable assignment without wake-up**: `rigx queue create <destination> "<body>" --type handoff --urgency soon`
-- **Ambiguous or raw intake**: `rigx stream emit "<body>" ...`
-- **Direct dialogue / urgent 1:1 conversation**: `rig send ...`
-- **Summoned 3+ party roundtable**: `rig chatroom ...`
-
-Do not cargo-cult the earlier "stream everything with `--destination`" prototype shape into the
-live control-plane. Stream is now the ambiguous-intake lane, not the universal lane.
-
-## Core shape (minimum-viable discipline)
-
-1. **Author a queue file at** `substrate/shared-docs/rigs/<your-rig>/state/<your-pod>/<your-member>.queue.md`. Same per-pod directory as your session log.
-2. **Every known-target hot-potato work handoff** should arrive via `rigx queue handoff`, not via `rig send`. Use `rigx queue create` only when you intentionally want a passive durable item without wake-up.
-3. **State transitions** (start → promote; finish → complete; stuck → block; hand off → handoff; completed handed-off work notifies source → handoff-complete) are appended to the entry body with timestamp. Never in-place rewrites.
-4. **Cross-rig reads permitted; cross-rig writes forbidden.** Pod-as-authority-boundary doctrine.
-
-### Live command surface note
-
-When the queue control-plane wrapper is installed, treat queue identity as command-resolved, not
-seat-name-guessed:
-
-- `rigx queue whoami` resolves the durable queue that belongs to your current seat
-- `rigx queue list --mine` shows your queue without guessing from member name
-
-This matters for continuity successors such as `lead2` or `lead5`, which may intentionally share
-the canonical `lead.queue.md` file instead of owning a separate `lead2.queue.md` or `lead5.queue.md`.
-
-Known-target direct handoff on the live wrapper:
-
-```bash
-rigx queue handoff orch-lead5@your-rig "Need PM shaping on queue attention loop" --type handoff --urgency soon
-```
-
-Passive durable write without wake-up:
-
-```bash
-rigx queue create orch-lead5@your-rig "Need PM shaping on queue attention loop" --type handoff --urgency soon
-```
-
-## Six operations
-
-| Op | Effect |
-|---|---|
-| append | New entry (state=pending) on inbound request |
-| promote | state=in-progress when you start work |
-| complete | state=done with optional result |
-| block | state=blocked + blocked-on=<id or condition> |
-| handoff | state=handed-off + handed-off-to=<target>/<new-id>; send rig-send with `[queue-handoff:]` prefix to target |
-| handoff-complete | target signals source that handed-off work finished (closes feedback loop) |
-| escalate | walk authority chain when blocked past tier threshold |
-| defer / drop | push-to-later or drop-with-rationale |
-
-## When is something a queue handoff?
-
-**Queue handoff** (`rigx queue handoff`):
-- Asks a known recipient to do new work
-- Transfers ownership of pending work
-- Names a deliverable + acceptance criteria
-
-**NOT a queue handoff**:
-- Wake-ping `1`
-- PSA / broadcast / status update
-- Ack / courtesy notification / diagnostic ping / reply to question
-- Raw idea or bug where you do not yet know the right owner
-
-If you do not know the correct owner, emit to stream instead of guessing.
-
-## Tier-based ack + notification rules
-
-- **human-gate tier** (gated items; human-watching): mandatory ack on handoff; mandatory notification on completion
-- **agent-coordination tier** (standard inter-agent work): recommended ack + notification
-- **internal-self tier** (your own to-dos): optional
-
-## Read discipline
-
-- Read your own queue at turn start before picking up new work
-- Orchestrators read pod-member queues on wake cadence (`1` ping)
-- Advisor-pod reads cross-rig queues for composed views + human-attention
-- Past-threshold blocked entries surface during sweeps; execute escalate op if you can't self-unblock
-
-Recommended turn-start queue commands on the live wrapper:
-
-```bash
-rigx queue whoami
-rigx queue list --mine
-```
-
-### Resume-from-idle state sweep
-
-Agents returning from idle-standby (supervisor-wake-only pings; no substantive dispatch during the window) MUST sweep adjacent state before pulling new work. Minimum sweep:
-
-- Supervisor-log tail (~200 lines) at `rigs/kernel/state/supervisor-log.md`
-- human-attention.md at `substrate/shared-docs/human-attention.md`
-- Any doctrine-decisions added since last-active (`rigs/kernel/state/doctrine-decisions/`)
-- Partner queue files at `rigs/kernel/state/<pod>/<peer-member>.queue.md` (peer load-tracking for pairs)
-- **Fleet-changes-feed** at `substrate/shared-docs/fleet-changes-feed.md` (pull-native rollout surface; catches any fleet-wide doctrine / skill / convention / operational changes that landed during idle; filter by scope = fleet-wide + your rig/pod)
-
-**Trigger:** first active turn after ≥3 consecutive wake-only cycles OR on peer HA-check request. Sweep before responding to HA-check so the response is grounded in current reality, not stale memory.
-
-**Rationale:** own-queue-at-turn-start catches own-queue drift; adjacent-state drift is a separate failure class that requires its own read discipline. Composable with own-queue sweep (both at same reading point); adds ~2-5 minutes of read time; cheap insurance against peer-driven HA-check round-trips.
-
-**Worked example (genesis):** advisor-co-observer@your-rig after ~2h idle-standing-by on 2026-04-13 — 5-of-7 HA-check items out-of-sync when peer queried. Rule addition would have caught the drift pre-query via adjacent sweep on wake-to-active transition.
-
-## Status-not-chat corollary
-
-Your chat pane is for operational work + ad-hoc human exchanges. Your STATUS lives in queue files + composed views. If you finish work + hit a gate-requiring next-action, do NOT narrate to chat + idle-wait. Queue-handoff to advisor-pod with `tier: human-gate`. The operator doesn't watch agent panes; they watch human-attention.md (composed from human-gate queue entries).
-
-## Composed views (4 layers)
-
-- **Pod-load view** — who's loaded / blocked (orch reads)
-- **Rig pending-work** — cross-pod roll-up
-- **Fleet cross-rig** — host-wide
-- **human-attention** — human-gate-tier items across all queues (advisor-pod composes)
-
-v0: manual regen by orchestrators + advisor-pod.
-v0.5: terminal-node watch scripts auto-regen.
-v1: generative UI consuming structured queue data.
-
-## Codex-sandbox proxy-write pattern (sanctioned workaround)
-
-Codex members whose sandbox blocks substrate writes can still participate via proxy-write:
-- Codex authors content locally (e.g., `/tmp/<rig>-attention-queue/<member>.queue.md`)
-- Claude counterpart physically writes to substrate with sha256-verified integrity check
-- Subsequent state transitions via `[queue-update: <id> <new-state> <reason>]` rig-send from Codex to Claude-writer
-- Authorship preserved; only write-access delegated. Distinct from peer-injection (which is forbidden).
-
-## Escalation mechanics
-
-When entry stays blocked past tier threshold AND agent can't self-unblock:
-
-1. Identify escalation target per authority chain:
-   - Pod member → pod orchestrator
-   - Pod orch → rig orch-lead
-   - Rig orch-lead → kernel orch-lead OR advisor-pod (if human-gate)
-   - Skip-levels allowed when agent KNOWS correct target
-2. Create new entry in escalation-target's queue with `escalated-from: <source-id>`; state=pending; priority elevated
-3. Send handoff-shape rig-send: `[queue-escalate: <new-id>] <title> — blocked <Nh> on <reason>`
-4. Update own entry: state=escalated; escalated-to=<target>/<new-id>; transitions-log appended
-
-Threshold guidance: 1h human-gate / 4h agent-coordination / 24h internal-self. Rigs may tighten.
-
-## Task-close RSI-check (flywheel trigger)
-
-Every `complete` op on substantive work reflects briefly: "what did we learn? is this worth filing as L2 capture to improvements-inbox?"
-
-Two outcomes; both leave evidence in the transition trail:
-
-- **Novel observation worth filing:** append L2 capture entry to `rigs/kernel/state/improvements-inbox.md` per the v1 queue template (`state: pending` + transition trail started). Transition line in your own queue: `<ts> — RSI-check: filed <capture-id>`.
-- **Nothing novel:** transition line in your own queue: `<ts> — RSI-check: none`.
-
-Applies to substantive work-streams. Does NOT apply to:
-- Wake-pings (`1`) — not a work-stream
-- Trivial status updates — nothing to reflect on
-- Pure acks / routing-map updates — no work done
-
-Rationale: task-close is the deterministic interval that makes recursive-self-improvement mechanical rather than ad-hoc. Pattern named in skill-maturity-convention.md §"Task-close RSI-check discipline".
-
-## Push vs pull — when to use rig-send vs queue-write
-
-Not every communication belongs in the receiver's chat pane. The discipline mirrors status-not-chat: most inter-agent signals can flow through queue files (pull) rather than rig-sends (push). Reduces noise; respects receiver's attention cycle.
-
-**Sender's test:** *Does my message need the receiver's attention within their next turn cycle?*
-- **Yes → push** via `rig send` (lands in chat; receiver processes on next turn)
-- **No → pull** via queue-write (write to own queue OR receiver's queue via handoff; receiver sweeps at cadence)
-
-### Push (rig-send to chat) when:
-
-- Receiver needs info NOW to unblock their work
-- Question requires specific answer to proceed
-- Handoff is past ack-threshold + tier=human-gate (mandatory-ack window)
-- Blocker surfacing (can't self-unblock; need help from target)
-- human-gate item needing surface to advisor-pod
-- Destructive or time-critical coordination
-
-### Pull (queue-write only) when:
-
-- Status update / adoption signal / cascade-complete ack
-- Non-urgent ack (within tier threshold)
-- Information that can batch in receiver's curator sweep
-- Broadcast-receipt confirmation (receiver's cadence catches it)
-- Observed patterns or captures with no time pressure
-- Resync material for HA peers (they sweep on resume-from-idle)
-
-### Why this matters
-
-Push-as-default floods the receiver's chat pane with status that could be pulled. Today's rollout volume proved this: during attention-queue + EMM cascades, most acks arrived as push (rig-sends) when they could have been pull (queue-writes). Receiver (advisor-pod) had to process each ping; most were status signals needing no action.
-
-Pull-over-push is the queue primitive's whole point. Status lives in queue files; readers sweep at cadence; only genuine unblockers + gate-surfaces push to chat.
-
-### Worked example
-
-orch-lead@your-rig ack'd attention-queue cascade:
-- **Push version (what happened):** `rig send advisor-peer-observer@your-rig "[queue-handoff-ack: ...] ... cascaded to 8 pod members ..."` → lands in my chat; I read immediately; process the status
-- **Pull version (what should happen):** write ack-receipt to `rigs/openrig-build/state/orch/lead.queue.md` as state-transition on their adoption entry; I sweep their queue on my curator cadence; pick up the ack without chat-ping
-
-Ack-receipts for status are pull-native. Handoff-complete notifications for human-gate items stay push (they close feedback loops on time-sensitive work).
-
-### Corollary — orchestrator-to-advisor cadence
-
-Orchestrators writing to their own queue files lets advisor-pod read without being interrupted. The curator-sweep pattern (advisor reads pod queues on their cadence) is the canonical pull mechanism. Push only when time-matters.
-
-## Anti-patterns (don't do these)
-
-- **Chat-as-status** — narrating status/gates to your chat pane + idle-waiting. Use queue + human-attention instead.
-- **Duplicate-storage** — writing the same fact in queue + session-log + chat + mission-control. Queue is authoritative for in-flight state.
-- **Peer-injection** — writing directly to another agent's queue without their authorship. Only handoff op moves work cross-queue.
-- **Silent drops** — don't leave items in pending forever without state transitions. defer or drop with rationale.
-- **Global queue** — don't try to make one queue for everyone. Per-agent primary; compose for views.
-
-## Maturity status
-
-**L4-insight** per skill-maturity-convention. Applied liberally across the host; evolving via observation. Feedback loop: RSI filings reshape this skill; demotion valid if convention reveals wrong shape; promotion to L5-canon requires architect+reviewer pair-review per HOST-TOPOLOGY §7 SOP.
-
-Rollout date: 2026-04-13 host-wide adoption. 48h observation cycle active; RSI with learnings due ~2026-04-15.
-
-## Related
-
-- Spec (full reference): the internal attention-queue spec
-- Skill-maturity convention: `substrate/shared-docs/skill-maturity-convention.md`
-- Config-wrapper-code loop doctrine: `config-wrapper-code-loop` skill
-- HOST-TOPOLOGY §4 context-sharing patterns — attention queue is a new pattern here
-- SUBSTRATE-CONVENTIONS §7 HA session logs — queue lives in same per-pod directory

package/dist/lib/scope-templates/mission-brief.md

@@ -1,20 +0,0 @@
-# {{mission_name}} — Brief
-<optional one-line italic TL;DR>
-
-## What & why
-<orientation, read-first: what this mission delivers + why it matters. MANDATORY.>
-
-## Building
-<what is actively in flight right now — brief-altitude, a few bullets, NOT the PROGRESS task list>
-
-## Progress
-<how far: a high-altitude phase/wave rollup. Points at PROGRESS.md for active/next detail.>
-
-## Proven
-<what has landed WITH proof — brief-altitude proof gauge. Points at the Proof tab / per-slice proof/.>
-
-## Needs you
-<open decisions + reviews waiting on the human/founder — the "never have to ask for status" section. Empty = nothing blocked on you.>
-
-## Pointers
-→ MISSION_NOTES.md (continuity / restore) · → PROGRESS.md (active / next) · other key links

package/dist/lib/scope-templates/mission-notes.md

@@ -1,102 +0,0 @@
----
-mission: {{mission_id}}
-name: {{mission_name}}
-status: active
-authored: {{created_date}}
-last-updated: {{created_date}}
----
-
-# Mission Notes — {{mission_name}}
-
-> Read the frontmatter `last-updated` first. If stale relative to runtime,
-> treat this file as `provisional` and re-verify before relying on it.
-> Pointer-first by design — index durable canonical artifacts; don't duplicate
-> them (duplication is the stale-breadcrumb failure mode this convention
-> exists to kill).
-
-## §1. Top-of-mind context
-
-(Current most-load-bearing state — gates, open scope-decisions, in-flight
-surprises. Updated by anyone when material changes. Keep to 5-15 lines.)
-
-## §2. Active workstreams + drivers + tips
-
-(Per-workstream rows. THIS SECTION IS THE MISSION CODEMAP. Each row:
-state / driver / branch+tip-SHA / latest blocker or ACK.)
-
-- (workstream-id) — state — driver — tip-SHA — blocker/ACK
-
-## §3. Open scope-decisions
-
-(Labeled gates the operator owns. Per gate: where the gate is, what's needed,
-who routed.)
-
-- OQ-1: (decision needed) — gate at <artifact-path> — surfaced by <seat>
-
-## §4. Slice inventory
-
-(Full table of slices on this mission.)
-
-| # | slice | state | driver | blocker |
-|---|---|---|---|---|
-
-## §5. Pending dispatches
-
-(Next-go items waiting on driver availability or convergence. Immediately-ready
-set, not full backlog.)
-
-## §6. Ledgers
-
-(Mission-specific shared ledgers: release version + tag, SC counts, cumulative
-deltas, etc.)
-
-## §7. Banked memories that apply here
-
-(Bulleted: banked-feedback / banked-project memories load-bearing on restore
-for this mission. Ones learned during this mission go into the same list.)
-
-## §8. Convention pointers
-
-(Which banked conventions this mission inherits. Cross-reference each by path.
-This section is the principles/conventions inheritance surface for the mission.)
-
-- `conventions/mission-notes/README.md` — this convention (apply on every restore)
-
-## §9. Reconstruction protocol
-
-(Commands to run after compaction or for onboarding. Refresh as the mission's
-restore-needs evolve.)
-
-1. `rig whoami --json` — confirm seat identity
-2. Read this file's §1 + your §A-§X section + this §9
-3. Read `missions/{{mission_id}}/README.md` for mission scope
-4. Read `missions/{{mission_id}}/PROGRESS.md` for delivery state
-5. `rig queue list --mine --full --json` — triage your durable inbox from full
-   bodies; use `rig queue show <id> --full --json` for individual items. Never
-   use the bare compact queue list for triage.
-6. Optionally check `rig transcript <your-session> --tail 100` as secondary
-   evidence. It may be unavailable or incomplete for some runtimes; little or
-   no output does not prove the session was quiet.
-7. State "restored from {{mission_id}}; resumed at <action>" before acting
-
-## §10. What NOT to reconstruct
-
-(Explicit pruning — completed slices / merged commits / closed ACK packets are
-recoverable on demand and don't need to be in working memory. Name them to
-free attention.)
-
-## §A. <first-seat>@<rig> notes
-
-(First seat's notes. Pattern: append cont.N entries with date + state of the
-world from this seat's perspective. Latest = truth. Other seats READ but
-don't modify.)
-
-DONE {{created_date}} (cont.0 — mission scaffolded):
-- Mission scaffolded via `rig scope mission create`. Template applied; this
-  file is the seed state. First substantive cont.1 entry follows when work
-  begins.
-
-## §B / §C / ... — per-seat sections
-
-(Each additional seat adds an h2 ## §X section under their own header as they
-join. Section pattern matches §A.)

package/dist/slack/config.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"config.d.ts","sourceRoot":"","sources":["../../src/slack/config.ts"],"names":[],"mappings":"AAWA,MAAM,WAAW,oBAAoB;IACnC,OAAO,EAAE,OAAO,CAAC;IACjB,kFAAkF;IAClF,kBAAkB,EAAE,MAAM,CAAC;IAC3B,8EAA8E;IAC9E,QAAQ,EAAE,MAAM,CAAC;IACjB,gGAAgG;IAChG,oBAAoB,EAAE,MAAM,EAAE,CAAC;IAC/B,mFAAmF;IACnF,WAAW,EAAE,MAAM,CAAC;IACpB,mFAAmF;IACnF,OAAO,EAAE,MAAM,GAAG,IAAI,CAAC;IACvB,+FAA+F;IAC/F,cAAc,EAAE,MAAM,EAAE,CAAC;IACzB,+EAA+E;IAC/E,cAAc,EAAE,MAAM,GAAG,IAAI,CAAC;IAC9B;;;;;OAKG;IACH,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;CACzB;AAED,eAAO,MAAM,cAAc,EAAE,oBAU5B,CAAC;AAEF,wBAAgB,aAAa,CAAC,IAAI,CAAC,EAAE,MAAM,GAAG,MAAM,CAEnD;AAED,wBAAgB,UAAU,CAAC,IAAI,CAAC,EAAE,MAAM,GAAG,oBAAoB,CAQ9D;AAED,wBAAgB,UAAU,CAAC,GAAG,EAAE,oBAAoB,EAAE,IAAI,CAAC,EAAE,MAAM,GAAG,MAAM,CAK3E;AAED,wBAAgB,gBAAgB,CAAC,IAAI,CAAC,EAAE,MAAM,GAAG,OAAO,CAEvD;AAED,MAAM,WAAW,aAAa;IAC5B,EAAE,EAAE,OAAO,CAAC;IACZ,KAAK,EAAE,MAAM,CAAC;IACd,MAAM,EAAE,MAAM,CAAC;CAChB;AAED;;;;GAIG;AACH,wBAAgB,eAAe,CAAC,GAAG,EAAE,oBAAoB,EAAE,UAAU,EAAE,OAAO,EAAE,WAAW,EAAE,OAAO,EAAE,WAAW,EAAE,OAAO,GAAG,aAAa,EAAE,CAU3I"}

package/dist/slack/config.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"config.js","sourceRoot":"","sources":["../../src/slack/config.ts"],"names":[],"mappings":"AAAA,4EAA4E;AAC5E,EAAE;AACF,yEAAyE;AACzE,6EAA6E;AAC7E,8EAA8E;AAC9E,4EAA4E;AAC5E,mFAAmF;AACnF,OAAO,EAAE,MAAM,SAAS,CAAC;AACzB,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,cAAc,EAAE,MAAM,sBAAsB,CAAC;AA2BtD,MAAM,CAAC,MAAM,cAAc,GAAyB;IAClD,OAAO,EAAE,KAAK;IACd,kBAAkB,EAAE,uBAAuB;IAC3C,QAAQ,EAAE,eAAe;IACzB,oBAAoB,EAAE,EAAE;IACxB,WAAW,EAAE,SAAS;IACtB,OAAO,EAAE,IAAI;IACb,cAAc,EAAE,CAAC,YAAY,EAAE,kBAAkB,EAAE,eAAe,CAAC;IACnE,cAAc,EAAE,IAAI;IACpB,QAAQ,EAAE,IAAI;CACf,CAAC;AAEF,MAAM,UAAU,aAAa,CAAC,IAAa;IACzC,OAAO,IAAI,CAAC,IAAI,CAAC,IAAI,IAAI,cAAc,EAAE,EAAE,sBAAsB,CAAC,CAAC;AACrE,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,IAAa;IACtC,MAAM,CAAC,GAAG,aAAa,CAAC,IAAI,CAAC,CAAC;IAC9B,IAAI,CAAC;QACH,MAAM,GAAG,GAAG,IAAI,CAAC,KAAK,CAAC,EAAE,CAAC,YAAY,CAAC,CAAC,EAAE,MAAM,CAAC,CAAkC,CAAC;QACpF,OAAO,EAAE,GAAG,cAAc,EAAE,GAAG,GAAG,EAAE,CAAC;IACvC,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,EAAE,GAAG,cAAc,EAAE,CAAC;IAC/B,CAAC;AACH,CAAC;AAED,MAAM,UAAU,UAAU,CAAC,GAAyB,EAAE,IAAa;IACjE,MAAM,CAAC,GAAG,aAAa,CAAC,IAAI,CAAC,CAAC;IAC9B,EAAE,CAAC,SAAS,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;IACnD,EAAE,CAAC,aAAa,CAAC,CAAC,EAAE,IAAI,CAAC,SAAS,CAAC,GAAG,EAAE,IAAI,EAAE,CAAC,CAAC,GAAG,IAAI,CAAC,CAAC;IACzD,OAAO,CAAC,CAAC;AACX,CAAC;AAED,MAAM,UAAU,gBAAgB,CAAC,IAAa;IAC5C,OAAO,EAAE,CAAC,UAAU,CAAC,aAAa,CAAC,IAAI,CAAC,CAAC,CAAC;AAC5C,CAAC;AAQD;;;;GAIG;AACH,MAAM,UAAU,eAAe,CAAC,GAAyB,EAAE,UAAmB,EAAE,WAAoB,EAAE,WAAoB;IACxH,OAAO;QACL,EAAE,EAAE,EAAE,GAAG,CAAC,cAAc,KAAK,IAAI,IAAI,UAAU,IAAI,WAAW,EAAE,KAAK,EAAE,gBAAgB,EAAE,MAAM,EAAE,GAAG,CAAC,cAAc,CAAC,CAAC,CAAC,YAAY,GAAG,CAAC,cAAc,EAAE,CAAC,CAAC,CAAC,eAAe,EAAE;QAC1K,EAAE,EAAE,EAAE,UAAU,EAAE,KAAK,EAAE,kBAAkB,EAAE,MAAM,EAAE,UAAU,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,qCAAqC,EAAE;QACtH,EAAE,EAAE,EAAE,WAAW,EAAE,KAAK,EAAE,WAAW,EAAE,MAAM,EAAE,WAAW,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,6CAA6C,EAAE;QACzH,EAAE,EAAE,EAAE,WAAW,EAAE,KAAK,EAAE,yBAAyB,EAAE,MAAM,EAAE,WAAW,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,gCAAgC,EAAE;QAC1H,EAAE,EAAE,EAAE,GAAG,CAAC,OAAO,KAAK,IAAI,EAAE,KAAK,EAAE,SAAS,EAAE,MAAM,EAAE,GAAG,CAAC,OAAO,IAAI,OAAO,EAAE;QAC9E,EAAE,EAAE,EAAE,OAAO,CAAC,GAAG,CAAC,kBAAkB,CAAC,EAAE,KAAK,EAAE,qBAAqB,EAAE,MAAM,EAAE,GAAG,CAAC,kBAAkB,EAAE;QACrG,EAAE,EAAE,EAAE,GAAG,CAAC,OAAO,EAAE,KAAK,EAAE,SAAS,EAAE,MAAM,EAAE,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,6BAA6B,EAAE;KACnG,CAAC;AACJ,CAAC"}

package/dist/slack/connector-server.d.ts

@@ -1,31 +0,0 @@
-import { type Server } from "node:net";
-import type { SeenStore } from "./state-store.js";
-import type { OutboundDecision } from "@openrig/daemon/gateway-protocol";
-/** The platform delivery outcome for one decision. */
-export type DeliveryOutcome = {
-    ok: true;
-} | {
-    ok: false;
-    class: string;
-    detail?: string;
-};
-export type DeliverFn = (decision: OutboundDecision) => Promise<DeliveryOutcome>;
-export interface ConnectorServerDeps {
-    socketPath: string;
-    /** Advertised in the CapabilityDescriptor — the gateway refuses any op not listed here (proof-9). */
-    connectorId: string;
-    platform: string;
-    ops: string[];
-    deliver: DeliverFn;
-    /** decisionId dedup (SeenStore keyed by decisionId) — idempotent redelivery. */
-    delivered: SeenStore;
-    log?: (msg: string) => void;
-}
-export interface ConnectorServer {
-    server: Server;
-    close(): Promise<void>;
-}
-/** Start the connector socket server. Each dialing gateway is greeted with the CapabilityDescriptor,
- *  then its OutboundDecision frames are delivered + acked (ack-after-delivery). Returns a handle. */
-export declare function startConnectorServer(deps: ConnectorServerDeps): Promise<ConnectorServer>;
-//# sourceMappingURL=connector-server.d.ts.map

package/dist/slack/connector-server.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"connector-server.d.ts","sourceRoot":"","sources":["../../src/slack/connector-server.ts"],"names":[],"mappings":"AAcA,OAAO,EAAgB,KAAK,MAAM,EAAe,MAAM,UAAU,CAAC;AAClE,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,kBAAkB,CAAC;AAClD,OAAO,KAAK,EAEV,gBAAgB,EAGjB,MAAM,kCAAkC,CAAC;AAE1C,sDAAsD;AACtD,MAAM,MAAM,eAAe,GAAG;IAAE,EAAE,EAAE,IAAI,CAAA;CAAE,GAAG;IAAE,EAAE,EAAE,KAAK,CAAC;IAAC,KAAK,EAAE,MAAM,CAAC;IAAC,MAAM,CAAC,EAAE,MAAM,CAAA;CAAE,CAAC;AAC3F,MAAM,MAAM,SAAS,GAAG,CAAC,QAAQ,EAAE,gBAAgB,KAAK,OAAO,CAAC,eAAe,CAAC,CAAC;AAEjF,MAAM,WAAW,mBAAmB;IAClC,UAAU,EAAE,MAAM,CAAC;IACnB,qGAAqG;IACrG,WAAW,EAAE,MAAM,CAAC;IACpB,QAAQ,EAAE,MAAM,CAAC;IACjB,GAAG,EAAE,MAAM,EAAE,CAAC;IACd,OAAO,EAAE,SAAS,CAAC;IACnB,gFAAgF;IAChF,SAAS,EAAE,SAAS,CAAC;IACrB,GAAG,CAAC,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,IAAI,CAAC;CAC7B;AAED,MAAM,WAAW,eAAe;IAC9B,MAAM,EAAE,MAAM,CAAC;IACf,KAAK,IAAI,OAAO,CAAC,IAAI,CAAC,CAAC;CACxB;AAOD;qGACqG;AACrG,wBAAsB,oBAAoB,CAAC,IAAI,EAAE,mBAAmB,GAAG,OAAO,CAAC,eAAe,CAAC,CAsD9F"}

package/dist/slack/connector-server.js

@@ -1,108 +0,0 @@
-// M1 A5 — the Slack CONNECTOR as a unix-socket SERVER. The hardened slice-11 relay evolves:
-// the gateway (daemon-spawned) now OWNS the outbound decision (queue poll + entity-admission)
-// and DIALS this connector; the connector owns platform delivery (Slack) and acks AFTER it.
-//
-// Ack-after-delivery (proof-1): a decision is delivered on the SHIPPED postWebhook path, and an
-// ok:true ack is sent ONLY after a 2xx — the decisionId is recorded delivered BEFORE the ack, so
-// a gateway replay of an already-delivered decision is de-duplicated and RE-ACKED without a
-// double-post. A failed delivery sends ok:false{class} and is NOT recorded → the gateway retains
-// it in its dispatch buffer and replays (no loss). This is the connector-side mirror of the
-// gateway dispatch buffer — the two stores are DISTINCT and never merged.
-//
-// The wire codec is the ONE canonical daemon definition (lane rule: import via the narrow
-// @openrig/daemon/gateway-protocol subpath; runtime codec is lazy-imported per house precedent).
-import { createServer } from "node:net";
-/** Start the connector socket server. Each dialing gateway is greeted with the CapabilityDescriptor,
- *  then its OutboundDecision frames are delivered + acked (ack-after-delivery). Returns a handle. */
-export async function startConnectorServer(deps) {
-    const log = deps.log ?? (() => { });
-    const { decodeGatewayMessage, encodeGatewayMessage } = (await import("@openrig/daemon/gateway-protocol"));
-    const descriptor = {
-        kind: "capability",
-        connectorId: deps.connectorId,
-        platform: deps.platform,
-        protocolVersion: 1,
-        ops: deps.ops,
-    };
-    const sockets = new Set();
-    const server = createServer((sock) => {
-        sockets.add(sock);
-        sock.setEncoding("utf8");
-        sock.on("error", () => { });
-        sock.on("close", () => sockets.delete(sock));
-        sock.write(encodeGatewayMessage(descriptor)); // greet: advertise capabilities
-        let acc = "";
-        sock.on("data", (chunk) => {
-            acc += chunk;
-            let nl;
-            while ((nl = acc.indexOf("\n")) >= 0) {
-                const frame = acc.slice(0, nl);
-                acc = acc.slice(nl + 1);
-                if (frame.length === 0)
-                    continue;
-                const decoded = decodeGatewayMessage(frame);
-                if (!decoded.ok) {
-                    log(`connector: refused frame: ${decoded.error}`);
-                    continue;
-                } // LOUD, no partials
-                const msg = decoded.message;
-                if (msg.kind === "outbound_decision") {
-                    void handleDecision(msg, sock, deps, encodeGatewayMessage, log);
-                }
-                // capability/ack are gateway-inbound only; the connector ignores them.
-            }
-        });
-    });
-    await new Promise((resolve, reject) => {
-        server.on("error", reject);
-        server.listen(deps.socketPath, () => resolve());
-    });
-    log(`connector ${deps.connectorId} listening on ${deps.socketPath}`);
-    return {
-        server,
-        close: () => new Promise((resolve) => {
-            for (const s of sockets) {
-                try {
-                    s.destroy();
-                }
-                catch { /* best-effort */ }
-            }
-            server.close(() => resolve());
-        }),
-    };
-}
-async function handleDecision(decision, sock, deps, encode, log) {
-    const ackOk = { kind: "ack", decisionId: decision.decisionId, ok: true };
-    // Idempotent redelivery: an already-delivered decisionId is RE-ACKED without re-posting.
-    if (deps.delivered.load().has(decision.decisionId)) {
-        log(`connector: decision ${decision.decisionId} already delivered — re-ack, no re-post`);
-        safeWrite(sock, encode(ackOk));
-        return;
-    }
-    let outcome;
-    try {
-        outcome = await deps.deliver(decision);
-    }
-    catch (e) {
-        outcome = { ok: false, class: "delivery-threw", detail: e.message };
-    }
-    if (outcome.ok) {
-        // Record delivered BEFORE the ack: a crash after this point re-acks via dedup (no double-post);
-        // a crash before it replays + re-delivers (at-least-once, byte-identical dup) — never a drop.
-        deps.delivered.mark(decision.decisionId, "delivered");
-        safeWrite(sock, encode(ackOk));
-        log(`connector: delivered + acked ${decision.decisionId}`);
-    }
-    else {
-        const ackFail = { kind: "ack", decisionId: decision.decisionId, ok: false, failed: { class: outcome.class, detail: outcome.detail } };
-        safeWrite(sock, encode(ackFail)); // NOT recorded → gateway retains + replays
-        log(`connector: delivery FAILED ${decision.decisionId} (${outcome.class}) — ack ok:false, gateway will replay`);
-    }
-}
-function safeWrite(sock, data) {
-    try {
-        sock.write(data);
-    }
-    catch { /* the gateway re-dials + replays on a dropped socket */ }
-}
-//# sourceMappingURL=connector-server.js.map