@north-light/crouter 0.3.161 → 0.3.163

package/dist/api/client.d.ts

@@ -10,7 +10,7 @@ import type { NodeConfigPatch } from './dto/config.js';
 import type { AttachEnsureRequest, AttachEnsureResultDTO } from './dto/attach.js';
 import type { EnsureProfileRequest, ProfileDTO } from './dto/profiles.js';
 import type { FilePeekDTO } from './dto/files.js';
-import type { CredentialResultDTO, InstallCredentialRequest } from './dto/modelauth.js';
+import type { CredentialRemovalResultDTO, CredentialResultDTO, InstallCredentialRequest, ModelAuthListDTO } from './dto/modelauth.js';
 import type { CreateHumanBridgeRequest, HumanBridgeResultDTO, HumanConsultResultDTO, HumanDeliverResultDTO, HumanVisualResultDTO } from './dto/human.js';
 import type { CancelInboxTicketRequest, CanceledTicketResultDTO, DeckTicketResultDTO, InboxDeckDTO, InboxListDTO, InboxTicketIdDTO, RespondInboxDeckRequest } from './dto/inbox.js';
 import type { AttentionCountsDTO, AttentionDTO, DashboardDTO, DashboardQuery, HistoryGrepQuery, HistoryGrepResultDTO, HistoryReadQuery, HistoryReadResultDTO, HistorySearchQuery, HistorySearchResultDTO, PruneRequest, PruneResultDTO, RebuildIndexResultDTO, RosterDTO, SnapshotDTO } from './dto/canvas.js';
@@ -139,7 +139,9 @@ export declare class CrtrClient {
     /** Delete one profile by exact id or unique name (`DELETE /v1/profiles/:name`,
      *  idempotent — a miss is success). */
     deleteProfile(name: string): Promise<void>;
+    listModelAuth(): Promise<ModelAuthListDTO>;
     installCredential(provider: string, req: InstallCredentialRequest): Promise<CredentialResultDTO>;
+    removeCredential(provider: string): Promise<CredentialRemovalResultDTO>;
     /** Create a terminal `kind:'human'` bridge node with NO broker engine
      *  (`spawnNode` server-side). Distinct from `createNode` (which launches a
      *  broker) precisely because a human bridge must never have one. */

package/dist/api/client.js

@@ -252,9 +252,15 @@ export class CrtrClient {
         await this.request('DELETE', routes.profile(name));
     }
     // ---- Model auth --------------------------------------------------------
+    listModelAuth() {
+        return this.request('GET', routes.modelAuths());
+    }
     installCredential(provider, req) {
         return this.request('PUT', routes.modelAuth(provider), req);
     }
+    removeCredential(provider) {
+        return this.request('DELETE', routes.modelAuth(provider));
+    }
     // ---- Human bridge + completion-handler forwarding (spec §6.5) ----------
     /** Create a terminal `kind:'human'` bridge node with NO broker engine
      *  (`spawnNode` server-side). Distinct from `createNode` (which launches a

package/dist/api/dto/modelauth.d.ts

@@ -39,3 +39,35 @@ export interface CredentialResultDTO {
     managed: boolean;
     account_id?: string;
 }
+/** One managed-pool account, projected without credential material. Timestamps are
+ * ISO strings so remote consumers do not need to understand pi's epoch-ms storage. */
+export interface ManagedAccountStatusDTO {
+    label: string;
+    expires_at: string;
+    rate_limited_until: string;
+    auth_failure?: 'invalid_grant';
+    account_id?: string;
+}
+/** A provider's sanitized credential state. Managed providers are always listed
+ * (even with no accounts); non-managed providers appear only when auth.json has
+ * an API-key or OAuth credential for them. */
+export type ModelAuthProviderStatusDTO = {
+    provider: string;
+    managed: true;
+    configured: boolean;
+    accounts: ManagedAccountStatusDTO[];
+} | {
+    provider: string;
+    managed: false;
+    configured: true;
+    kind: 'api_key' | 'oauth';
+};
+/** `GET /v1/model-auth` — credential-presence projection for every known provider. */
+export interface ModelAuthListDTO {
+    providers: ModelAuthProviderStatusDTO[];
+}
+/** `DELETE /v1/model-auth/{provider}` — all user credentials removed for one provider. */
+export interface CredentialRemovalResultDTO {
+    provider: string;
+    removed_accounts: number;
+}

package/dist/api/dto/modelauth.js

@@ -1,3 +1,4 @@
 // Model-auth DTOs (spec §7.6). `PUT /v1/model-auth/{provider}` installs/rotates
-// already-obtained credential material; interactive collection stays client-side.
+// already-obtained credential material; `GET /v1/model-auth` exposes only sanitized
+// connection state; interactive collection stays client-side.
 export {};

package/dist/api/routes.d.ts

@@ -59,6 +59,7 @@ export declare const routes: {
     readonly humanInboxCancel: (ticketId: string) => string;
     readonly profiles: () => string;
     readonly profile: (name: string) => string;
+    readonly modelAuths: () => string;
     readonly modelAuth: (provider: string) => string;
     readonly filePeek: () => string;
 };

package/dist/api/routes.js

@@ -85,6 +85,7 @@ export const routes = {
     profiles: () => `${V}/profiles`,
     profile: (name) => `${V}/profiles/${name}`,
     // Model auth
+    modelAuths: () => `${V}/model-auth`,
     modelAuth: (provider) => `${V}/model-auth/${provider}`,
     // Host file read (browser file-peek panel). The absolute path rides as a
     // `path` query param, not a path segment — it is not a single safe segment.

package/dist/builtin-memory/00-runtime-base.md

@@ -9,6 +9,7 @@ rationale: >-
   "Say what actually happens" exists because an approval request called a root a person had created an "attended root" — an invented category with no referent in the product, which forced Silas to halt the decision and ask what the term meant (2026-07-28). Agents coin taxonomies to compress a distinction; the reader pays by decoding a word that names nothing real.
 
   "Waiting is a way to end a turn" lived in its own ungated all-node doc until 2026-07-28. Same gate, same audience, never independently readable — so the split bought no routing and cost a stub cross-reference in this file pointing at a section spliced a few hundred tokens later. Split it back out only if it ever needs a gate of its own.
+lint-ignore: length
 ---
 
 You are a **node** in a live agent graph (the crtr canvas). This section is your operating protocol — it is true for every node regardless of role.

package/dist/builtin-memory/04-orchestration-kernel.md

@@ -6,6 +6,7 @@ file-read-visibility: none
 gate: {mode: orchestrator}
 rationale: >-
   Two observed orchestration failures set this kernel's stopping rules. A sole-writer feature lane produced a 5-deep 1:1 developer/orchestrator chain by repeatedly delegating the whole assignment; separately, the kernel's “idle capacity,” “maximum agents,” and “when in doubt, more rigor” objective helped produce review-only subtrees as large as 87 nodes and five levels deep. Coordination must optimize new evidence toward the goal rather than node count or process length.
+lint-ignore: length
 ---
 
 ## You are an orchestrator

package/dist/builtin-memory/init.md

@@ -0,0 +1,38 @@
+---
+kind: knowledge
+when-and-why-to-read: When bootstrapping a project's memory store — the user invoked /init or a workspace has no .crouter/memory/INDEX.md front door — this knowledge should be read because a lean routed front door gives every future agent in that workspace its operating contract for a fraction of the standing context cost an unstructured guidance dump would charge each session forever.
+short-form: "Bootstrap a project memory store: survey the repo, then author a lean INDEX front door plus a linked dev doc — commands, map, non-default rules, pointers — and lint. Depth splits into linked docs; every always-loaded line must earn its keep."
+system-prompt-visibility: none
+file-read-visibility: none
+slash: true
+rationale: Unguided agents bootstrap project memory badly in both directions — either no front door at all, or a monolithic CLAUDE.md-style manual (copied README, generic framework advice, exhaustive command catalogs) that taxes every future session and decays. Distilled 2026-07-31 from ecosystem research across Anthropic/OpenAI/Cursor/GitHub guidance and production AGENTS.md files — the strongest evidence being Sentry's consolidation postmortem (critical commands buried in nested files got missed) and Anthropic's under-200-line target with adherence falling as always-loaded files grow.
+---
+
+# /init — bootstrap this project's memory store
+
+Give this workspace its memory front door: a root INDEX every future agent boots with when the project mounts, plus a small graph of linked docs carrying the depth. The front door is an operating contract and routing layer, never a manual — every line it carries is paid by every session here forever, so a line earns its place only by changing behavior: a fact every task needs, a non-obvious hazard, or a rule an agent would otherwise get wrong.
+
+## 1. Survey before writing
+
+Learn the project from its own artifacts: README, package manifests and lockfiles, build/CI config, scripts, existing CLAUDE.md/AGENTS.md or docs. Extract the real commands (setup, run, build, targeted test, full verification) and RUN the important ones — record only commands you have seen work, with any required ordering, environment, or package-manager constraint. Note the architecture in a few sentences: major components, dependency direction, where generated or externally-owned code lives. Collect the conventions that differ from what a competent agent would assume — those deviations are the highest-value lines you will write.
+
+## 2. Read the contract, then author the front door
+
+Run `crtr memory write -h` first — it carries the substrate frontmatter contract and the exact root-INDEX shape, including the workspace-mount route that `crtr memory lint` validates. Then author the INDEX with these sections, total well under the length lint's cap:
+
+- **Project in one paragraph** — purpose, major components, dependency direction.
+- **Common commands** — the 3–8 commands most changes need, copyable, verified.
+- **Where to work** — a task-to-path map; mark generated or externally-owned areas.
+- **Non-default rules and gotchas** — only high-impact deviations from defaults. Skip anything a formatter, linter, or typechecker already enforces; point at the check instead.
+- **Done** — the minimum credible gate for an ordinary change.
+- **Pointers** — a `[[link]]` per deeper doc with a one-clause read trigger (e.g. "debugging the daemon → the dev doc").
+
+Exclude generic language/framework advice, copied docs or style guides, volatile version detail, rare edge cases, and multi-step procedures — depth belongs behind links, not in the standing load.
+
+## 3. Split depth into linked docs
+
+Author `dev` alongside the INDEX by default: validated setup/run/build/test/debug commands with required order and environment, targeted-vs-full verification, and common failure modes. Add `architecture` only when the tree cannot be understood from the INDEX's brief map, and a conventions/gotchas doc only once real project-specific rules outgrow a few INDEX bullets — never pre-populate generic security or style manuals. These reference docs take `none` visibility on both axes; the INDEX's links are how they are found, so they cost nothing until followed.
+
+## 4. Validate
+
+Run `crtr memory lint` — it strict-parses the store, checks the INDEX front-door contract, and fails on dangling links or over-length bodies. Fix findings rather than suppressing them. The store is a living contract: when commands, architecture, or conventions change, rewrite the affected doc in place and delete superseded guidance — an always-loaded line that has stopped being true is worse than no line at all.

package/dist/builtin-memory/wedged-child-on-runaway-bash.md

@@ -2,8 +2,8 @@
 kind: knowledge
 when-and-why-to-read: When a node is marked wedged or remains active without progress while its inbox accumulates, this reference should be read so recovery restores progress without losing context or killing the wrong process.
 short-form: a child stuck mid-turn (runaway bash, or a stalled broker with no subprocess) is AUTO-DETECTED by the daemon (⚠ wedged + a doctrine wake) — kill the subprocess if one exists; if none, the daemon SIGTERM-kicks the broker and automatically starts a fresh recovery cycle
-system-prompt-visibility: none
-file-read-visibility: preview
+system-prompt-visibility: preview
+file-read-visibility: none
 ---
 
 A base node can wedge INDEFINITELY on a single runaway bash command (classic: `grep -rln "..." /` — a recursive grep from filesystem root that scans all of disk and never returns; also any unbounded find/scan over `/` or a network mount). The node's pi turn is blocked waiting on the bash call, so it never `push`es and never finishes.

package/dist/builtin-pi-packages/pi-crtr-extensions/README.md

@@ -32,7 +32,6 @@ directory's `node_modules/`.
 | Extension | What it does |
 |-----------|--------------|
 | `claude-plugin-commands.ts` | Surfaces commands and skills from `~/.claude`, the cwd, every project in the selected crouter profile, and installed plugins as pi slash commands with arg/shell-block execution. Writes shims to `~/.pi/agent/.plugin-command-shims/`. Skips any name pi already serves natively from `~/.pi/agent/prompts/` (e.g. crtr exports a slash command to both `~/.claude/commands` and `~/.pi/agent/prompts`), so the shim never collides with the native prompt. |
-| `crouter-help.ts` | Help integration for the `crtr` CLI. |
 | `provider-rotation.ts` | Subscription credential rotation across Anthropic / OpenAI-Codex: does its own OAuth login/refresh, rotates on rate-limits, falls back across the model ladder. Registers `/provider-sub <provider> <list\|add\|select\|rm>`. |
 | `crtr-commands/` | Auto-generates a slash command per `crtr` CLI node. The tree is derived in-process from crtr's own `buildRoot()` (no subprocesses, no cache on disk); `filters.json` controls which nodes are exposed. |
 | `sysprompt-window.ts` | Registers `/sysprompt`, which runs `crtr sys sysprompt --window` without injecting the prompt into context. |