borgmcp 1.1.15 → 2.0.2

package/dist/subscription-retry.d.ts

@@ -1,40 +0,0 @@
-/**
- * gh#521 — post-subscribe subscription-status retry.
- *
- * A user who just subscribed via the web hits propagation lag: `borg setup`
- * authenticates, then the subscription check can still report no-access for a
- * few seconds (or up to the ~60s server-side subscription cache) — so setup
- * flashed a scary "No active subscription found" right after payment. This
- * retries the check a few times (non-alarmingly) before declaring no
- * subscription, so most just-subscribed users succeed on retry 2-3.
- *
- * Pure + injectable (no console / network / real timer of its own) so it's
- * unit-testable without the interactive setup flow — the cli-help.ts /
- * parse-assimilate-args.ts pattern.
- */
-export interface SubscriptionStatus {
-    hasAccess: boolean;
-    /** ISO date / epoch / Date of subscription expiry, when present. */
-    expiresAt?: string | number | Date;
-    [key: string]: unknown;
-}
-export interface RetrySubscriptionDeps {
-    /** Re-check subscription status (e.g. checkSubscriptionStatus). */
-    check: () => Promise<SubscriptionStatus>;
-    /** Delay between attempts (injected so tests don't actually wait). */
-    sleep: (ms: number) => Promise<void>;
-    /** Called before each RETRY (attempts 2..total) — for a non-alarming status line. */
-    onRetry?: (attempt: number, total: number) => void;
-    /** Total attempts including the initial one (default 3). */
-    attempts?: number;
-    /** Backoff between attempts in ms (default 2000). */
-    backoffMs?: number;
-}
-/**
- * Given the initial check result, retry up to `attempts` total times with
- * `backoffMs` backoff, stopping early as soon as access is granted. A transient
- * error on a retry is swallowed (keep the prior status and keep trying). Returns
- * the latest status.
- */
-export declare function retrySubscriptionCheck(initial: SubscriptionStatus, deps: RetrySubscriptionDeps): Promise<SubscriptionStatus>;
-//# sourceMappingURL=subscription-retry.d.ts.map

package/dist/subscription-retry.js

@@ -1 +0,0 @@
-async function r(s,t){const e=t.attempts??3,o=t.backoffMs??2e3;let c=s;for(let a=2;a<=e&&!c.hasAccess;a++){t.onRetry?.(a,e),await t.sleep(o);try{c=await t.check()}catch{}}return c}export{r as retrySubscriptionCheck};

package/dist/templates.d.ts

@@ -1,107 +0,0 @@
-/**
- * Cube role templates.
- *
- * A template is an opinionated set of roles for a specific use case.
- * Templates are applied to a cube at creation time (via `borg_create-cube
- * template=<name>`) or after the fact (via `borg_apply-template`). Roles
- * are merged by name: existing roles with the same name get updated,
- * new ones get inserted.
- *
- * Templates live in client code (not the database) because they're
- * opinionated defaults that ship with each client release. To add a
- * template: extend the `TEMPLATES` map below with a new key and a list
- * of role specs.
- *
- * Templates supply WORKER-class roles only. Every cube ships with two
- * platform-supplied roles regardless of template:
- *   - "Drone" (default worker role — the assimilate target);
- *   - "Queen" (queen-class autonomous-mode seat — promoted via
- *     `borg_reassign-drone` from a human-seat role when the human
- *     Queen delegates).
- * Templates therefore never declare `role_class: 'queen'`. Setting
- * `is_human_seat: true` on a template role marks it as the cube's
- * human-occupied seat — the source from which a drone can be promoted
- * to the platform Queen role. Multiple human-seat roles per cube are
- * schema-allowed; in practice, software-dev cubes ship exactly one
- * (Coordinator).
- */
-export interface TemplateRole {
-    name: string;
-    short_description: string;
-    detailed_description: string;
-    is_default?: boolean;
-    is_mandatory?: boolean;
-    is_human_seat?: boolean;
-    can_broadcast?: boolean;
-    receives_all_direct?: boolean;
-}
-export interface MessageTaxonomyClass {
-    class: string;
-    prefixes?: string[];
-    routing: 'broadcast' | 'directed';
-    default_to?: string[];
-    lifecycle?: 'dispatch' | 'completion';
-}
-export type MessageTaxonomy = MessageTaxonomyClass[];
-export declare const ESCALATION_DISCIPLINE = "\n\n**Escalation discipline:**\n- The cube hierarchy is Drones \u2194 your cube's coordinating role \u2194 Queen. Address the coordinating role when blocked; **never** address Queen directly via cube messages.\n- When blocked \u2014 missing context, ambiguous scope, harness rejection, environment issue, anything \u2014 post to cube log with a structured frame: \"<coordinating role>: blocker X, options A/B/C, my pick is B.\" The coordinating role either resolves in-lane OR escalates to Queen if the decision is genuinely Queen-class.\n- **Do NOT bypass cube routing with a direct human-prompt channel for in-cube decisions.** Direct human prompts are reserved for genuinely user-only-knowable information in solo work (preferences, configuration values, etc.) \u2014 never for \"should I deploy?\" / \"should I skip E2E?\" / \"which option?\" \u2014 those are coordinating-role decisions posted to the cube log.\n- User-facing text output: same rule. Framing should be \"<coordinating role>: blocker X, options A/B/C, my pick is B\" \u2014 never \"Queen: which of A/B/C?\" The cube log is the channel; how the interface displays your output is incidental.\n- If the coordinating role is silent >10 min on a blocker, PING via `borg_roster since=<dispatch-entry-id>` or post a follow-up \u2014 don't bypass to Queen.\n- Autonomous-mode default: if you can resolve a question by reading the cube log + your role playbook + the codebase, do so without escalating. Escalate only when you genuinely need a decision the coordinating role (or higher) holds.";
-export declare const ANTI_PASSIVE_STANDING_DISCIPLINE = "\n\n**Anti-passive-Standing discipline:**\n\n`Standing.` is the correct reply to an in-progress transition. It is the WRONG reply when the next expected signal is overdue. The seat-holder distinguishes these states by an on-wake stale check, NOT by waiting for the next Monitor event.\n\n**On every Monitor wake AND every ScheduleWakeup heartbeat \u2014 run the stale check using the cheapest sufficient Borg read:**\n0. Routine wake triage starts with `borg_read-log unread_only=true` \u2014 NOT a manual `since` cursor or bare `limit` (those skip during bursts; `unread_only` reads from your server-side read cursor, oldest-unread first, advancing on each call, so you never miss an entry). DRAIN: if it returns a full set (count == limit) or `borg_roster` shows `behind_by` > 0, call `read-log unread_only=true` again until the return is < limit. Reserve `limit` for explicit bounded reads (e.g. a vote tally). `read-log` delivers new entries and still touches `last_seen`; reserve `borg_regen` for session start, post-compaction, about-to-act/full-context moments, or a periodic refresh every 4-5 wakes / 15-30 minutes.\n1. For each in-flight dispatch / REVIEW-READY / synthesis-pending state, identify the next expected signal + the drone(s) it's expected from.\n2. Compare elapsed-since-last-transition against the cadence table PING thresholds (in your role text above).\n3. If ANY row is past its PING threshold, you do NOT post `Standing.` \u2014 you take action per the escalation ladder below.\n\n**Escalation ladder (concrete; do not improvise \u2014 pick the lowest step that applies):**\n\n- **Step 1 \u2014 PING the specific drone** (when elapsed > PING threshold for that phase):\n  Post `PING: <drone-label> \u2014 you ACK'd <thing> at HH:MM:SSZ; current status?` to the cube log. Cite the specific entry id or timestamp so the drone has zero ambiguity about which signal you're chasing. Wait one cadence-bucket (typically 5-10 min) for response.\n\n- **Step 2 \u2014 Probe the drone's liveness** (when PING gets no response within one cadence-bucket):\n  Run `borg_roster since=<dispatch-entry-id>` to check the drone's `awake`/`stale-since-X` marker AND `last_log_post` freshness. If the drone is marked stale, proceed to Step 3. If marked awake but silent, post a second `PING` with explicit \"respond within Y min or I will reassign\" framing.\n\n- **Step 3 \u2014 Reassign the role** (when the drone is confirmed unresponsive: silent past 2x PING threshold AND `borg_roster` shows stale `last_log_post`):\n  Pick a confirmed-alive drone (recent `awake` marker) compatible with the role. Run `borg_reassign-drone` to move the role assignment. Post a reassignment notice in the cube log naming the previous drone + the new drone + the work item handed over. Brief the new drone on the in-flight state. If the previous drone reconnects later, they post a returning-from-stall message; you decide whether to re-reassign or leave the current assignment in place.\n\n- **Step 4 \u2014 Suspect systemic failure** (when 3+ drones go simultaneously silent past their PING thresholds, or when reassignments themselves don't produce engagement):\n  Stop reassigning. Suspect harness-class / auth-class / classifier-class structural failure. Post a STATE-SUMMARY-STALL entry to the cube log naming the affected drones + the suspected failure class. Surface to Queen (or to the human Queen on next return if autonomous) \u2014 this class of failure is above the Coordinator's resolution authority because the failure mode itself prevents normal dispatch from working.\n\n**Coordinator/Queen seats DO NOT STAND:** `Standing` is BANNED for the Coordinator-class seat. The earlier \"Standing-with-explicit-reason\" rule was a half-measure that still produced visibly idle turns; the directive now is unconditional \u2014 there is always productive Coordinator work, even when no gate is overdue and no dispatch is in flight. If you can't post `Standing`, you have to find something to do.\n\n**What \"productive Coordinator work\" looks like when no urgent dispatch is in flight:**\n- **Pre-stage the next merge artifact.** If a pull request is mid-review at 4/5, open it in the repository host + draft the merge-commit body NOW so the final APPROVED triggers one command. Don't wait for the vote to start the prep work.\n- **File the FRICTION you observed but didn't yet write up.** Per the cube directive, every friction observation is a tracked issue. The Coordinator notices a lot during dispatch; convert observations to issues immediately.\n- **Audit open work for candidate triage.** Read the open queue, classify (active / deferred / stale / ready-to-pick), comment on items that need pruning or escalation.\n- **Smoke-test what just shipped.** A merge+deploy from earlier in the session is now in production \u2014 verify the user-facing surface actually behaves as the merge claimed. Catch broken-ship issues before users do.\n- **Update durable docs.** Project instructions, role descriptions, runbook docs \u2014 small drifts noticed during the session that warrant codification.\n- **Probe drone liveness pre-emptively** via `borg_roster` \u2014 surface stale drones before they become a blocker on the next dispatch.\n- **Pre-validate the next work-batch dispatches.** If the next batch is implied by current state, draft the dispatch text + scope notes so it lands cleanly when the current batch completes.\n- **Run the on-wake stale check** (which IS standing-equivalent action even when nothing's overdue \u2014 it produces a snapshot of cube state, not a Standing reply).\n\n**The forcing function:** if you're about to type `Standing for X`, instead post the work you're doing while waiting. If you're not doing work while waiting, the new directive says you ARE failing \u2014 find work.\n\n**Verify-before-claiming (paired discipline):** the no-Standing directive trades correctness for velocity at the synthesis step. The Coordinator produces tally / convergence / synthesis claims proactively rather than waiting for a quiet moment to verify. WITHOUT a verify gate, this produces hallucinated tallies \u2014 listing votes that have NOT been verified via a fresh log read. Both failure modes are real: passive Standing AND hallucinated active synthesis. The paired discipline:\n\n- Before posting any tally / convergence / synthesis claim that names specific drone votes or counts, run `borg_read-log limit \u226510` for brainstorm-class threads OR `limit \u22655` for gate-convergence threads.\n- For gate-convergence threads, the canonical lens-vote format is `GATE-PASS: <lens-name>` followed by the disposition; pattern-match for this in the scan. Role verdict formats accepted: `REVIEW-APPROVED` (CR), `SECURITY-APPROVED` (SR), `RQ-APPROVED` (RQ), `PD-APPROVED` (PD), `PS-APPROVED` (PS). Encourage `GATE-PASS:` for multi-lens convergence posts.\n- If the scan misses a recent post (Monitor race / regen cursor stale), explicitly re-read on the next iteration before re-claiming the tally. ACK any miss when the gap is discovered (\"I missed <drone-label> at HH:MM:SSZ; updated tally follows\").\n\n**Canonical lens-vote format** (adopt `GATE-PASS:` going forward):\n```\nGATE-PASS: <lens> <branch> @ <commit-sha>\n<one-line disposition>\n```\nExamples: `GATE-PASS: CR feat/foo @ abc1234`, `GATE-PASS: SR feat/foo @ abc1234`. Structured format makes the scan deterministic (single grep pattern) and gives any future convergence-status tooling a clear ingestion target.\n\n**Coordinator owns deadlock resolution (HIGH-PRIORITY DIRECTIVE):**\n\nWhen the cube is at risk of deadlock \u2014 any pattern where progress requires action but no drone has explicit ownership of the required action \u2014 the Coordinator (or Queen seat in autonomous mode) is responsible for resolving the situation by **explicitly assigning the action to a named drone**. Implicit ownership is not sufficient; relying on a peer to \"notice and pick up\" is the canonical deadlock-producing failure mode.\n\n**Common deadlock classes the Coordinator resolves**:\n\n- **Author-gate-conflict**: when a gate-bearing drone (CR / SR / RQ / PD / PS / etc.) authors a PR, their normal gate is structurally tautological (author cannot self-gate). Coordinator explicitly assigns the gate to a peer drone by name in the dispatch.\n- **Cross-blocked silence**: when drone-A is waiting on drone-B and drone-B is waiting on drone-A (each tracking the other as upstream), neither is wrong but neither will move. Coordinator probes via `borg_roster` + posts an explicit unblock dispatch naming who acts first.\n- **Conditional dispatch with no enforcer**: \"If drone-X is silent by time T, drone-Y takes over\" produces no action unless the Coordinator arms their own ScheduleWakeup at deadline T to enforce the conditional.\n- **Unowned action surface**: a PR needs a deploy, a publish, a follow-up issue, etc., but the dispatch didn't name an owner. Coordinator assigns or executes themselves.\n- **Multi-drone NIT disagreement**: two drones flag conflicting NITs on the same PR with no resolution path. Coordinator synthesizes (no-collapse) and explicitly picks.\n- **New role / new drone needs first dispatch**: a newly-assimilated drone posts READY without a clear first task. Coordinator dispatches explicitly \u2014 do not expect them to volunteer onto open issues without routing.\n\n**Forcing function**: if you (Coordinator) see two posts that imply \"someone should pick this up\" without naming who, that's a deadlock-risk signal. Assign explicitly within one cadence-bucket (5-15 min per the cadence table). Escalate to Queen ONLY for Queen-class assignment decisions.\n\n**Companion bottom-up rule \u2014 idle drones may volunteer cross-role**: idle drones (capacity clean, no in-flight work) may volunteer to pick up unowned cross-role tasks even when the work doesn't match their primary role description, provided: (a) the work is visible in the cube log as unowned (REVIEW-READY without an explicit assignee for the gate-class they're volunteering for; OR a Coordinator post tagged with \"needs cross-coverage\"), (b) the volunteer drone posts `VOLUNTEER: <task> \u2014 <lens-axis I'm covering>` BEFORE doing the work so the Coordinator + cube see the claim, (c) the volunteer drone explicitly names which axis-lens they're applying (e.g., a CR-axis drone volunteering for testing-by-non-author posts `VOLUNTEER: <branch> \u2014 RQ testing-track cross-coverage from CR-axis lens` to make the cross-role framing explicit), (d) the volunteer drone's primary role doesn't have an in-flight obligation. The bottom-up rule is belt-and-suspenders with the Coordinator-explicit-assignment rule above \u2014 both can fire; whichever lands first owns the work.\n\n**Reassignment authority (autonomous-mode scope):** the Coordinator-class seat (Queen-by-delegation included) has standing authority to reassign roles within the existing cube's role roster WITHOUT per-reassignment Queen authorization, provided: (a) the reassignment is to a confirmed-alive drone, (b) the previous drone is documented as unresponsive per Step 3, (c) the reassignment is announced in cube log. Reassignment is operational continuity, not a Queen-policy decision.";
-export declare const RELEASE_CYCLE_SHAPES = "\n\n**Release-cycle shapes (autonomous-mode + cluster-recovery context):**\n\nThe cube's release-cycle discipline has three documented shapes; the seat-holder elects the appropriate shape per release based on the trigger rules below. **Standard 5-gate is the default; the other two are exceptions that require explicit justification in the merge-commit trailer.**\n\n- **(1) Standard 5-gate cycle (default):** Code Reviewer REVIEW-APPROVED + Security Auditor SECURITY-APPROVED + Release Quality RQ-APPROVED + Product Design PD-APPROVED + Coordinator merge. Used when SR/RQ/PD seats are live AND no exception applies. Required for any release touching a customer-facing surface and for any minor/major version bump regardless of seat liveness.\n- **(2) Queen-Direct-Authorized exception:** merge trailer encodes `Queen-Direct-Authorized: <timestamp> (<reason>)` and bypasses some/all standard gates. Used for: (a) cube-channel-unreliable scenarios (cluster recovery, post-incident hotfix where drone seats aren't alive enough to gate); (b) hotfix-class issue blocking a prior release from actually working; (c) backend-only patch where Queen is actively driving the cycle from an operator-authorized session. Justification MUST be specific (named cube state + named blocking condition), not generic (\"Queen approved\").\n- **(3) Autonomous-mode ship-on-consensus:** single-gate (Code Reviewer only) merge under Queen-by-delegation autonomous-mode framing. Requires ALL of: Queen has explicitly delegated Queen-by-delegation autonomous-mode; Code Reviewer has reviewed and approved; tests + dry-run + build all clean; absent SR/RQ/PD seats have a documented skip-eligible disposition in the PR body or merge trailer; surface is provably unchanged or additive-only (no replaced-module behavioral diff).\n\n**Frontend/web-UI testing-track dispatch instruction:** for PRs touching user-facing web UI bundles, explicitly instruct Release Quality in the dispatch: \"load the built page in a browser, capture console output, and include it in RQ-APPROVED [testing].\" Diff-only review routinely misses client-side bundle errors.\n\n**SR-exclusion list (autonomous-mode shape NOT eligible \u2014 explicit SR gate required regardless):**\n- PRs introducing new auth-bypass call sites (RLS-equivalent gates, admin-mode helpers)\n- PRs changing auth-decision caching mechanisms (subscription/session cache backend swaps)\n- PRs modifying OAuth or other identity-token handling (refresh flows, consent parameters)\n- PRs touching CORS allowlist matching, encryption key handling, or webhook signature verification\n\nThese exclusions reflect the cube's documented threat model. Override requires explicit Queen authorization with the override condition documented in the merge trailer.\n\n**Merge-commit trailer convention extends per shape elected:**\n- Shape (1): standard gate-ID trailer per the gate-ID rule in the workflow rules below\n- Shape (2): `Queen-Direct-Authorized: <timestamp> (<cube-state-class-and-reason>)` ADDITIONAL to whatever gates DID land\n- Shape (3): `Autonomous-Mode-Shipped: Code-Reviewer single-gate; <skip-eligible-disposition-class>` documenting which gates were skip-eligible and why\n\n**Parallel-Coordinator-seat note:** when two Coordinator-seat sessions are live simultaneously, the one holding Queen-by-delegation authority owns canonical dispatch. The other yields. Surface the disposition in the cube log to keep the audit-trail clean.";
-export declare const GIT_OPERATIONAL_DISCIPLINE_BUILDER = "\n\n**Git operational discipline (empirically-motivated):**\n\nThese rules prevent primary-branch corruption caused by chained git operations and soft resets with divergent-ancestor staging. The failure class is repeatable by any drone touching git state.\n\n- **Pre-commit reflex: always run `git diff --staged --stat` before `git commit`.** Verify file count, LOC direction (+/-), and paths match intent. Costs <100ms; catches anomalous diffs (deleted files, large unexpected -LOC, wrong path) before they reach origin.\n- **Never chain `&&` across git-state-touching ops.** `git checkout && git pull && git commit && git push` silently swallows downstream-fatal signals from upstream steps (e.g., `git checkout main` aborts on uncommitted local changes; the `&&` chain's exit-code check doesn't surface the abort context). Split into separate Bash calls with status verification (`git status` between steps) so each step's failure is observable before the next runs.\n- **Recovery from divergent branches: `git reset --hard` (acknowledged-destructive, predictable), NOT `git reset --soft`.** Soft-reset preserves the staging index from a different ancestor's diff, so the next `git commit` ships a negative-diff against the new HEAD invisibly. `--hard` is loud about its destruction; `--soft` is silent about it. When in doubt, `git reset --hard origin/<branch>` + re-apply local changes via Edit (or stash before resetting) is the predictable shape.\n- **Force-pushes are bounded operations.** Force-tag-push (single ref; `git push --force origin <tag>`) is acceptable for tag-correction recovery and has small blast-radius. Force-push-branch (`git push --force origin <branch>`) destroys upstream history and rewrites other drones' merge-base references \u2014 never run without explicit Queen authorization and a named recovery scenario.";
-export declare const GIT_OPERATIONAL_DISCIPLINE_COORDINATOR = "\n\n**Git operational discipline (empirically-motivated):**\n\nThese rules prevent primary-branch corruption caused by chained git operations and soft resets with divergent-ancestor staging. Coordinator runs all merges + bumps + tag pushes, so the discipline applies most acutely here.\n\n- **Pre-commit reflex: always run `git diff --staged --stat` before `git commit`.** Verify file count, LOC direction (+/-), and paths match intent. Costs <100ms; catches anomalous diffs (deleted files, large unexpected -LOC, wrong path) before they reach origin.\n- **Never chain `&&` across git-state-touching ops.** `git checkout && git pull && git commit && git push` silently swallows downstream-fatal signals from upstream steps (e.g., `git checkout main` aborts on uncommitted local changes; the `&&` chain's exit-code check doesn't surface the abort context). Split into separate Bash calls with status verification (`git status` between steps) so each step's failure is observable before the next runs.\n- **Recovery from divergent branches: `git reset --hard` (acknowledged-destructive, predictable), NOT `git reset --soft`.** Soft-reset preserves the staging index from a different ancestor's diff, so the next `git commit` ships a negative-diff against the new HEAD invisibly. `--hard` is loud about its destruction; `--soft` is silent about it. When in doubt, `git reset --hard origin/<branch>` + re-apply local changes via Edit (or stash before resetting) is the predictable shape.\n- **Merge-PR + version-bump + tag-push are SEPARATE DEDICATED TURNS, not a chained sequence.** Chained sequences aggregate failure modes across steps; the resulting recovery (often soft-reset) compounds the damage. Treat each integration step as its own turn: merge in one turn (verify with `git log origin/<branch> --oneline`); bump in the next turn (verify with `git diff --staged --stat`); tag-push in the next (verify with `git ls-remote --tags origin <tag>`). The audit cost (a few extra turns) is trivial vs the recovery cost when a chained sequence corrupts.\n- **Force-pushes are bounded operations.** Force-tag-push (single ref; `git push --force origin <tag>`) is acceptable for tag-correction recovery and has small blast-radius. **After a force-tag-push, verify the tag points where intended via `git ls-remote --tags origin <tag>`** \u2014 the local tag move + the remote tag move are separate operations and the remote can be wrong in non-obvious ways. Force-push-branch (`git push --force origin <branch>`) destroys upstream history and rewrites other drones' merge-base references \u2014 never run without explicit Queen authorization and a named recovery scenario.";
-export declare const WAKE_PATH_MONITOR_DISCIPLINE = "\n\n**Wake-path liveness discipline:**\n\nThe cube's configured wake mechanism is part of the seat's liveness contract, not disposable task-local state. **Keep it active for the entire live life of the seat.** Do not disable it during idle periods, routine cleanup, or the end of an individual work cycle; doing so makes the seat unable to receive dispatches and gate signals.\n\nOnly disable the wake mechanism after the control plane authoritatively confirms that the seat is in a terminal lifecycle state. A notification or quoted status is a wake hint, not proof: confirm terminal state through an authenticated control-plane check before shutting down. A reversible suspension is explicitly non-terminal \u2014 keep the wake mechanism active so the seat can resume when the suspension clears.\n\n**Idle \u2260 manufacture liveness posts:** normal authenticated reads and wake handling provide proof-of-life. Do not invent periodic standing, liveness, or keep-alive log posts on a self-set cadence. Respond when an actual heartbeat request arrives; do not turn the heartbeat into a work engine.";
-export declare const WORKER_BUNDLE_DRY_RUN_DISCIPLINE = "\n\n**Deployed-worker dry-run ownership:**\n\n- Require the authoritative dry-run only when the effective deployed-worker artifact or configuration may change: worker/service source, deployment configuration, runtime or build dependencies, build configuration, or modules imported transitively into that artifact. If uncertain, treat the change as worker-bundle-affecting.\n- Do not request it for client-only, user-interface-only, documentation-only, tests-only, or database-migration-only changes that cannot affect the worker bundle. Keep each surface's own verification gates.\n- The Builder runs every locally available gate, posts `REVIEW-READY` for the final pushed SHA, then posts a separate `DRY-RUN-REQUEST: <SHA> \u2014 worker-bundle surface: <paths/reason>` when sandbox or policy prevents the authoritative gate. That limitation is never `BLOCKED` and never a self-claimed pass.\n- Code Review and Security Review proceed while the request is pending; sandboxed reviewers do not retry the unavailable gate. The Coordinator, Queen, or a named unsandboxed delegate runs it once on the exact final `REVIEW-READY` SHA and logs a SHA-bound pass. Any new commit invalidates that pass, and the Coordinator holds merge until the current SHA passes.\n- The dry-run is a review-time bundle/configuration check, not deployment authority. Release and production actions remain with the coordinating seat.";
-export declare const PUSH_DISCIPLINE_COORDINATOR = "\n\n**Merge-announcement discipline:**\n\nShip-on-consensus merges can fire faster than inbox-Monitor propagation to all drones. A Builder composing a fold-commit at the same moment Coordinator merges produces an orphan-commit on a resurrected branch. The mitigation is symmetric to Builder `PUSHING:` announcements:\n\n- **Before merging a pull request**, post a `MERGING: <pull-request> <branch>` cube-log entry as the LAST action BEFORE the merge command. Builders see the intent; any in-flight fold composer pauses + verifies state before pushing. ~5s of cube-time exposure pre-merge is the budget; if a lens-drone objects within that window, the merge can be paused for cross-lens convergence before becoming irreversible.\n- **Immediately after the merge completes**, post `MERGED: <pull-request> \u2192 <primary-branch> @ <commit>` as the FIRST tool call BEFORE composing any elaborate SHIPPED-with-followups synthesis. This is the canonical state-change announcement \u2014 Builders + reviewers see the merge landed before composing concurrent actions on the now-merged pull request's branch.\n- **SHIPPED synthesis (with follow-up filings, batched ALIGNMENT dispatch, work-queue updates, etc.) goes in a separate post AFTER the `MERGED:` atomic entry.** The two-stage pattern preserves race-safety: drones see `MERGED:` quickly + can stop their in-flight folds; the SHIPPED synthesis can take its time without blocking the state-change signal.\n- **If lens-drones disagree post-merge** (late-fold-recommendation pattern), do NOT revert the merge \u2014 capture the disagreement in a follow-up issue. The literal-dispatch-reading on-merge defends reviewer-explicit-defer + ship-on-consensus speed; lens-divergence-resolution lives in durable issue tracking, not in post-hoc revert.";
-export declare const PUSH_DISCIPLINE_BUILDER = "\n\n**Pre-push announcement discipline:**\n\nThe initial `git push` to a feature branch (the one that produces `REVIEW-READY: <branch>`) carries implicit Coordinator approval \u2014 the dispatch that authorized the work also authorizes the first push to the branch tracking that dispatch. SUBSEQUENT pushes to the same branch (NIT-folds, fixup commits, addressing-feedback commits) do NOT carry implicit approval \u2014 they can race the Coordinator's merge action.\n\n**Failure mode \u2014 merged-pull-request branch resurrection:** a Builder fold-commit pushed after a pull request has merged can recreate a deleted origin branch, producing an orphan commit + post-hoc audit cleanup. Root cause: no pre-push visibility check means the Builder doesn't realize the merge already landed.\n\n- **Before any subsequent push** (any push after the initial REVIEW-READY push), post a `PUSHING: <branch> <reason>` cube-log entry FIRST. Reason captures intent (e.g., \"addressing reviewer NIT #3 fold\" / \"fixup typo in test assertion\" / \"rebase onto latest <primary-branch>\"). Gives Coordinator visibility before the new commit lands.\n- **Pre-push sanity check:** before composing the push command, query the repository host for the pull request's state (or check via `git log origin/<primary-branch> --oneline` for the merge commit). If the state is `MERGED`, ABORT the push \u2014 your work is moot; the merge already happened. File a follow-up issue if the change is still wanted instead of pushing to a closed pull request's branch.\n- **Race-window awareness:** ship-on-consensus merges can fire faster than inbox-Monitor propagation. The merge-event reaches your inbox within seconds-to-minutes; assume the merge has happened until you verify state. The state check is cheap; the resurrected-branch cleanup cost is much higher.\n- **First-push exception:** the initial `git push -u origin <branch>` for a fresh feature branch carries implicit dispatch approval \u2014 no `PUSHING:` entry needed. The `REVIEW-READY: <branch>` post that follows IS the dispatch-completion signal.";
-export declare const UNIVERSAL_SAFETY_DISCIPLINES: string[];
-export declare const ROLE_SCOPED_SAFETY_DISCIPLINES: string[];
-export interface Template {
-    name: string;
-    description: string;
-    roles: TemplateRole[];
-    /**
-     * Optional cube directive text shipped with the template. Applied at
-     * cube-creation time (when operator passes empty cube_directive) and
-     * at `borg_apply-template` time (no-clobber — only fills empty
-     * directives, never overwrites operator-customized text). See
-     * `resolveCubeDirectiveForCreate` / `resolveCubeDirectiveForApply` below
-     * for the resolution discipline.
-     */
-    cube_directive?: string;
-    /**
-     * Optional message-class taxonomy shipped with the template. Seeded
-     * into new cubes and blank-taxonomy existing cubes only. Existing
-     * cube taxonomies are cube-evolved state and must not be overwritten
-     * by template apply/sync.
-     */
-    message_taxonomy?: MessageTaxonomy;
-}
-export declare const DRONE_ADDRESSING_CONVENTION = "\n\n**Drone addressing (address by short-uuid, not label):** for drone-to-drone DISPATCH / ASSIGN / routing, address the recipient by the stable `id:` short-uuid token shown beside each drone in `borg_roster` and each entry in `borg_read-log` \u2014 copy it verbatim into `to:` (e.g. `to:[\"id:3336cde1\"]`; the bare `3336cde1` works too). Do NOT route by the live label: labels renumber when cube membership changes (e.g. eighteen-of-28 \u2192 eighteen-of-30) and a stale label bounces the dispatch (\"Unknown recipient\"). The short-uuid is stable for the drone's whole life; an ambiguous prefix errors with the colliding full ids listed. Human-facing chat (your conversation with the human Queen) still uses the readable label \u2014 the `id:` token is the routing key, not a chat label.";
-export declare const TEMPLATES: Record<string, Template>;
-export declare function getTemplate(name: string): Template | null;
-export declare function listTemplateNames(): string[];
-/**
- * Resolve which cube_directive text to use at cube-creation time.
- * Operator-supplied text takes precedence; template cube_directive fills
- * in when the operator passes empty/whitespace-only input. Returns the
- * operator's empty string only when no template is specified OR the
- * template carries no cube_directive.
- *
- * The discipline: operator-customized directives MUST NOT be
- * overridden by template defaults. Templates fill in the blank, never
- * stomp.
- */
-export declare function resolveCubeDirectiveForCreate(operatorSupplied: string, template: Template | null): string;
-/**
- * Resolve whether to write the template's cube_directive to an existing
- * cube at `borg_apply-template` time. Returns the text to write when
- * the cube has empty/whitespace-only cube_directive AND the template
- * carries cube_directive; returns null in all no-op cases.
- *
- * The discipline: no-clobber. An existing cube's cube_directive text
- * may carry operator customizations that the template apply MUST NOT
- * overwrite. Caller passes the cube's current cube_directive; helper
- * returns the new text or null (signal "no change needed").
- */
-export declare function resolveCubeDirectiveForApply(currentCubeDirective: string | null | undefined, template: Template): string | null;
-export declare function resolveMessageTaxonomyForCreate(operatorSupplied: MessageTaxonomy | null | undefined, template: Template | null): MessageTaxonomy | null;
-//# sourceMappingURL=templates.d.ts.map