@aexol/spectral 0.8.0 → 0.8.5

package/CHANGELOG.md

@@ -1,75 +1,100 @@
 # Changelog
 
-All notable changes to `@aexol/spectral` are documented here.
-Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+All notable changes to `@aexol/spectral` are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.8.4] - 2026-06-02
+
+### Added
+
+- Added `contextWindow` override field to the Built-in UserModels admin form,
+  allowing admins to set a custom context window for built-in models.
+  The field appears between Credits and System Prompt in the edit/create
+  form. Also added to model config export/import and GraphQL selector.
+
+## [0.8.3] - 2026-06-02
+
+### Fixed
+
+- Fixed aggressive context compaction on every turn when using built-in models
+  (e.g. "Aexol Coder"). The `contextWindow` was always `null` for built-in
+  `UserModel` entries because the lookup used pipe-separated keys
+  (`provider|modelId`) but `UserModel.baseModel` stores values with a colon
+  separator (`anthropic:claude-sonnet-4-20250514`). The backend now correctly
+  inherits `contextWindow` from the linked `BaseModel`.
+
 ## [0.7.2] - 2026-05-25
 
 ### Changed
+
 - Version bump for monorepo release
 
 ### Added
+
 - Admin OpenRouter catalog picker in `/studio/admin/models` (Base Models tab):
-  search across 368 models from `https://openrouter.ai/api/v1/models` and add
-  to the whitelist with one click. Picker marks models already present in the
+  search across 368 models from `https://openrouter.ai/api/v1/models` and add to
+  the whitelist with one click. Picker marks models already present in the
   whitelist (disabled add) regardless of their enabled state.
-- `Query.adminOpenRouterCatalog: [OpenRouterModel!]!` — admin-gated, with a
-  1h in-memory TTL cache of the upstream catalog.
-- `Mutation.adminCreateBaseModel(input: BaseModelCreateInput!): BaseModel!`
-  with duplicate guard on `(provider, modelId)`. Defaults `enabled=true`.
+- `Query.adminOpenRouterCatalog: [OpenRouterModel!]!` — admin-gated, with a 1h
+  in-memory TTL cache of the upstream catalog.
+- `Mutation.adminCreateBaseModel(input: BaseModelCreateInput!): BaseModel!` with
+  duplicate guard on `(provider, modelId)`. Defaults `enabled=true`.
 - Verbatim `modelId` routing for `provider="openrouter"` in the backend
   inference proxy: no `${provider}/${modelId}` rebuild — picker-sourced rows
   carry the canonical OR ID and are sent through unchanged. Legacy rebuild
-  fallback is preserved for older naive-provider rows
-  (`provider="deepseek"`, `"google"`, etc.).
+  fallback is preserved for older naive-provider rows (`provider="deepseek"`,
+  `"google"`, etc.).
 - Per-session model selection: choose AI model from a whitelist managed by
   admins. Selection persists per session in localStorage and is sent in the
   `prompt` envelope to apply via pi `setModel()`.
-- New SQLite column `sessions.model_id` for cross-restart recovery of
-  selected model.
-- Synthetic pi providers `spectral-proxy-anthropic` and
-  `spectral-proxy-openai`, registered at `PiBridge` start, that point pi's
-  `ModelRegistry` at the backend's `/v1` proxy. `AuthStorage.inMemory()` and
-  `ModelRegistry.inMemory()` skip on-disk pi credentials in `serve` mode.
-- Backend `/v1/messages` and `/v1/chat/completions` machine-JWT auth branch
-  with raw `modelId` resolution against the `BaseModel` whitelist.
+- New SQLite column `sessions.model_id` for cross-restart recovery of selected
+  model.
+- Synthetic pi providers `spectral-proxy-anthropic` and `spectral-proxy-openai`,
+  registered at `PiBridge` start, that point pi's `ModelRegistry` at the
+  backend's `/v1` proxy. `AuthStorage.inMemory()` and `ModelRegistry.inMemory()`
+  skip on-disk pi credentials in `serve` mode.
+- Backend `/v1/messages` and `/v1/chat/completions` machine-JWT auth branch with
+  raw `modelId` resolution against the `BaseModel` whitelist.
 - TTL-cached `fetchAllowedModels` GraphQL query used by `spectral serve` to
   discover the team's allowed models from the backend at startup.
 - Startup info log on `spectral serve`:
   `✓ Inference routed via backend proxy (N model(s) available)`.
 
 ### Changed
+
 - Soft-remove a model from the whitelist by reusing the existing per-row
-  `Switch` toggle (no separate Remove button). Disabled rows remain visible
-  in the admin table and can be re-enabled with the same Switch.
-- Available models are now read from a backend-managed `BaseModel` table
-  (synced from https://models.dev/api.json by admins) instead of a
-  hardcoded frontend whitelist.
-- `spectral serve` inference now routes through the backend proxy
-  (centralized API keys) instead of reading `~/.pi/agent/auth.json`. CLI
-  machines no longer need provider API keys locally; the backend manages
-  them. The per-machine machine JWT carries auth, and the per-team
-  `BaseModel` whitelist gates which models can be used.
+  `Switch` toggle (no separate Remove button). Disabled rows remain visible in
+  the admin table and can be re-enabled with the same Switch.
+- Available models are now read from a backend-managed `BaseModel` table (synced
+  from https://models.dev/api.json by admins) instead of a hardcoded frontend
+  whitelist.
+- `spectral serve` inference now routes through the backend proxy (centralized
+  API keys) instead of reading `~/.pi/agent/auth.json`. CLI machines no longer
+  need provider API keys locally; the backend manages them. The per-machine
+  machine JWT carries auth, and the per-team `BaseModel` whitelist gates which
+  models can be used.
 
 ### Fixed
+
 - Admin "Add from OpenRouter" picker GraphQL syntax error
-  (`Expected Name, found String "modalities"`). Mutations
-  `adminCreateBaseModel` and `adminUpdateBaseModel` now pass their input
-  objects via Zeus `$()` variables instead of inline serialization,
-  so nested array fields (`modalities`, `supportedParameters`) parse
-  correctly server-side.
+  (`Expected Name, found String "modalities"`). Mutations `adminCreateBaseModel`
+  and `adminUpdateBaseModel` now pass their input objects via Zeus `$()`
+  variables instead of inline serialization, so nested array fields
+  (`modalities`, `supportedParameters`) parse correctly server-side.
 
 ### Removed
-- Hardcoded `landing/config/model-whitelist.ts` allowlist (replaced by
-  the DB-backed whitelist).
+
+- Hardcoded `landing/config/model-whitelist.ts` allowlist (replaced by the
+  DB-backed whitelist).
 
 ### Migration
+
 - `spectral` (CLI / TUI subprocess mode): no change — still uses local
   `~/.pi/agent/auth.json`.
-- `spectral serve`: ensure the backend has the relevant provider keys
-  configured (`ANTHROPIC_API_KEY`, `OPENROUTER_API_KEY`, etc.). Local
+- `spectral serve`: ensure the backend has the relevant provider keys configured
+  (`ANTHROPIC_API_KEY`, `OPENROUTER_API_KEY`, etc.). Local
   `~/.pi/agent/auth.json` is ignored when running `serve`.
 
 ## [0.1.0] — 2026-04-29
@@ -77,35 +102,37 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 Initial release.
 
 ### Added
+
 - `spectral login` — interactive authentication. Verifies the team API key
   against the Aexol MCP backend before persisting credentials to
   `~/.spectral/config.json` (mode `0600`).
 - `spectral logout` — removes stored credentials. Idempotent.
-- `spectral serve` — always-on agent that connects this machine to the
-  Aexol relay over a single long-lived WebSocket.
-  - Registers a machine identity with your team on first run; reuses the
-    issued JWT on subsequent runs.
+- `spectral serve` — always-on agent that connects this machine to the Aexol
+  relay over a single long-lived WebSocket.
+  - Registers a machine identity with your team on first run; reuses the issued
+    JWT on subsequent runs.
   - Reconnects automatically with exponential backoff.
-  - Graceful shutdown on `SIGINT` / `SIGTERM`: drains in-flight responses
-    and closes the relay cleanly before exiting.
+  - Graceful shutdown on `SIGINT` / `SIGTERM`: drains in-flight responses and
+    closes the relay cleanly before exiting.
   - `--machine-name <name>` overrides the default `os.hostname()`.
 - Browser-driven sessions through the Aexol web UI:
   - Machine picker for switching between paired devices.
-  - Multi-tab sync of project and session lifecycle changes (create,
-    rename, delete) via a per-machine meta channel.
+  - Multi-tab sync of project and session lifecycle changes (create, rename,
+    delete) via a per-machine meta channel.
   - Stuck-turn watchdog re-enables the composer after 60s of silence.
 - Local-first storage: projects, sessions, and messages live in a SQLite
   database at `~/.spectral/sessions.db`. They never leave the machine.
-- Bundled Aexol MCP extension auto-loaded for the local TUI path so
-  `spectral` (no subcommand) acts as a fully-configured pi session.
-- Plain pi pass-through: any flag that isn't a Spectral subcommand is
-  forwarded verbatim to `pi`.
+- Bundled Aexol MCP extension auto-loaded for the local TUI path so `spectral`
+  (no subcommand) acts as a fully-configured pi session.
+- Plain pi pass-through: any flag that isn't a Spectral subcommand is forwarded
+  verbatim to `pi`.
 
 ### Notes
-- Backend storage is identity + machine metadata only. Message content,
-  code, and model API keys never leave your machine.
-- One SQLite database per machine — switching machines in the browser
-  shows a different project list, by design.
-- Pi auth tokens (Anthropic, OpenAI, Cerebras, Google, custom endpoints)
-  are managed by pi itself in `~/.pi/agent/auth.json` and are not read or
+
+- Backend storage is identity + machine metadata only. Message content, code,
+  and model API keys never leave your machine.
+- One SQLite database per machine — switching machines in the browser shows a
+  different project list, by design.
+- Pi auth tokens (Anthropic, OpenAI, Cerebras, Google, custom endpoints) are
+  managed by pi itself in `~/.pi/agent/auth.json` and are not read or
   transmitted by Spectral.

package/README.md

@@ -4,10 +4,10 @@
 
 ## What is Spectral?
 
-Spectral is the always-on coding agent for [Aexol](https://aexol.com). You install
-it on every machine you want to code on, run `spectral serve`, and your devices
-appear in the Aexol web UI as live agents you can drive from any browser tab — no
-port forwarding, no SSH, no exposing localhost.
+Spectral is the always-on coding agent for [Aexol](https://aexol.com). You
+install it on every machine you want to code on, run `spectral serve`, and your
+devices appear in the Aexol web UI as live agents you can drive from any browser
+tab — no port forwarding, no SSH, no exposing localhost.
 
 Under the hood, Spectral is a thin branded wrapper around
 [pi](https://www.npmjs.com/package/@mariozechner/pi-coding-agent) by Mario
@@ -33,9 +33,9 @@ Requires Node.js **20 or newer**.
    spectral login
    ```
 
-   You'll be prompted for your Aexol MCP URL (defaults to `https://api.aexol.ai/mcp`)
-   and a team API key (`sk-aexol-team-…`). Credentials are written to
-   `~/.spectral/config.json` with mode `0600`.
+   You'll be prompted for your Aexol MCP URL (defaults to
+   `https://api.aexol.ai/mcp`) and a team API key (`sk-aexol-team-…`).
+   Credentials are written to `~/.spectral/config.json` with mode `0600`.
 
 2. **Start the agent**
 
@@ -59,44 +59,44 @@ Aexol MCP extension auto-loaded.
 
 ## Commands
 
-| Command            | Description                                                                   |
-|--------------------|-------------------------------------------------------------------------------|
-| `spectral`         | Local TUI. Forwards all flags to pi; loads the bundled Aexol MCP extension.   |
-| `spectral login`   | Interactive auth. Verifies the key against the MCP backend and stores it.     |
-| `spectral logout`  | Removes `~/.spectral/config.json`. Idempotent.                                |
-| `spectral serve`   | Connect this machine to the Aexol relay. Stays up; survives reconnects.       |
+| Command              | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| `spectral`           | Local TUI. Forwards all flags to pi; loads the bundled Aexol MCP extension. |
+| `spectral login`     | Interactive auth. Verifies the key against the MCP backend and stores it.   |
+| `spectral logout`    | Removes `~/.spectral/config.json`. Idempotent.                              |
+| `spectral serve`     | Connect this machine to the Aexol relay. Stays up; survives reconnects.     |
 | `spectral --version` | Print version.                                                              |
-| `spectral --help`  | Print Spectral header, then pi's full help.                                   |
+| `spectral --help`    | Print Spectral header, then pi's full help.                                 |
 
 ### `spectral serve` flags
 
-| Flag                       | Description                                                       |
-|----------------------------|-------------------------------------------------------------------|
-| `--machine-name <name>`    | Override the display name (default: `os.hostname()`).             |
+| Flag                    | Description                                           |
+| ----------------------- | ----------------------------------------------------- |
+| `--machine-name <name>` | Override the display name (default: `os.hostname()`). |
 
-Anything that isn't a Spectral subcommand is forwarded verbatim to pi, so any
-pi flag you know works. Example: `spectral -p "summarize this repo"`.
+Anything that isn't a Spectral subcommand is forwarded verbatim to pi, so any pi
+flag you know works. Example: `spectral -p "summarize this repo"`.
 
 ## How it works
 
 ```
-   ┌────────────────┐         ┌─────────────────┐         ┌────────────────┐
-   │  Browser tab   │────────▶│  Aexol backend  │◀────────│  spectral serve │
-   │ (Aexol web UI) │  WSS    │     (relay)     │   WSS   │ (your machine)  │
-   └────────────────┘         └─────────────────┘         └────────────────┘
-                                       │
-                              identity + routing only
-                              (no message content, no code)
+┌────────────────┐         ┌─────────────────┐         ┌────────────────┐
+│  Browser tab   │────────▶│  Aexol backend  │◀────────│  spectral serve │
+│ (Aexol web UI) │  WSS    │     (relay)     │   WSS   │ (your machine)  │
+└────────────────┘         └─────────────────┘         └────────────────┘
+                                    │
+                           identity + routing only
+                           (no message content, no code)
 ```
 
 - Your machine runs `spectral serve` and registers with the relay using a
   machine JWT issued at first run.
-- Browser sessions for that machine open a WebSocket to the backend. The
-  backend forwards every frame to your machine and back — it never reads or
-  stores message content.
-- All your local state — projects, sessions, messages, pi auth tokens —
-  lives on the device. The backend only knows machine identity (id, display
-  name, hostname, last-seen) and team membership.
+- Browser sessions for that machine open a WebSocket to the backend. The backend
+  forwards every frame to your machine and back — it never reads or stores
+  message content.
+- All your local state — projects, sessions, messages, pi auth tokens — lives on
+  the device. The backend only knows machine identity (id, display name,
+  hostname, last-seen) and team membership.
 
 ## How inference is routed
 
@@ -116,88 +116,86 @@ direct call to provider              backend uses centralized API keys
                                      scoped to team's BaseModel whitelist
 ```
 
-- **`spectral` (CLI subprocess mode)** — pi runs as a normal subprocess and
-  uses whatever provider keys you've stored locally in `~/.pi/agent/auth.json`
+- **`spectral` (CLI subprocess mode)** — pi runs as a normal subprocess and uses
+  whatever provider keys you've stored locally in `~/.pi/agent/auth.json`
   (Anthropic, OpenAI, Cerebras, Google, custom OpenAI-compatible endpoints).
-  Spectral never reads or transmits these. This is the classic local-only
-  flow.
+  Spectral never reads or transmits these. This is the classic local-only flow.
 - **`spectral serve` (relay mode)** — pi runs in-process inside the serve
   daemon. All inference traffic is proxied through the Aexol backend's
   `/v1/messages` and `/v1/chat/completions` endpoints, authenticated with the
   per-machine machine JWT. The backend holds the upstream provider keys and
   enforces a per-team `BaseModel` whitelist server-side. The local
-  `~/.pi/agent/auth.json` is **not read** in this mode (`AuthStorage.inMemory()`).
+  `~/.pi/agent/auth.json` is **not read** in this mode
+  (`AuthStorage.inMemory()`).
 
-Why two paths? `spectral serve` is designed for shared / managed machines
-where the team controls which models are usable and operators don't want
-provider keys sitting on every box. `spectral` (no subcommand) is the
-unmanaged TUI path and behaves like a vanilla pi install.
+Why two paths? `spectral serve` is designed for shared / managed machines where
+the team controls which models are usable and operators don't want provider keys
+sitting on every box. `spectral` (no subcommand) is the unmanaged TUI path and
+behaves like a vanilla pi install.
 
 ## Configuration
 
-| Path / variable                           | Purpose                                                |
-|-------------------------------------------|--------------------------------------------------------|
-| `~/.spectral/config.json`                 | Aexol MCP URL + team API key. Created by `spectral login`. Mode `0600`. |
-| `~/.spectral/machine.json`                | Machine identity + relay JWT. Created on first `spectral serve`.        |
-| `~/.spectral/sessions.db`                 | Local SQLite for projects, sessions, messages.         |
-| `SPECTRAL_CONFIG_DIR`                     | Override the directory above.                          |
-| `SPECTRAL_MCP_URL`                        | Override the MCP URL at login time.                    |
-| `SPECTRAL_BACKEND_URL`                    | Override the backend HTTP base for `spectral serve`.   |
-| `SPECTRAL_RELAY_URL`                      | Override the derived relay WebSocket URL.              |
-
-Pi's own auth state for the local TUI path (Anthropic, OpenAI, etc.) lives
-in `~/.pi/agent/auth.json` on the same machine. Spectral never reads it and
-never sends it anywhere. Note that `spectral serve` does **not** use this
-file — it routes inference through the backend proxy instead (see
+| Path / variable            | Purpose                                                                 |
+| -------------------------- | ----------------------------------------------------------------------- |
+| `~/.spectral/config.json`  | Aexol MCP URL + team API key. Created by `spectral login`. Mode `0600`. |
+| `~/.spectral/machine.json` | Machine identity + relay JWT. Created on first `spectral serve`.        |
+| `~/.spectral/sessions.db`  | Local SQLite for projects, sessions, messages.                          |
+| `SPECTRAL_CONFIG_DIR`      | Override the directory above.                                           |
+| `SPECTRAL_MCP_URL`         | Override the MCP URL at login time.                                     |
+| `SPECTRAL_BACKEND_URL`     | Override the backend HTTP base for `spectral serve`.                    |
+| `SPECTRAL_RELAY_URL`       | Override the derived relay WebSocket URL.                               |
+
+Pi's own auth state for the local TUI path (Anthropic, OpenAI, etc.) lives in
+`~/.pi/agent/auth.json` on the same machine. Spectral never reads it and never
+sends it anywhere. Note that `spectral serve` does **not** use this file — it
+routes inference through the backend proxy instead (see
 [How inference is routed](#how-inference-is-routed)).
 
 ## Multiple machines
 
 You can run `spectral serve` on as many machines as you like under one team —
-each gets its own machine identity and its own SQLite. The browser picker
-lists all of them; switching machines shows that machine's project list and
-session history. Switching is a hard context change: the previous selection
-is cleared so you don't accidentally talk to the wrong device.
+each gets its own machine identity and its own SQLite. The browser picker lists
+all of them; switching machines shows that machine's project list and session
+history. Switching is a hard context change: the previous selection is cleared
+so you don't accidentally talk to the wrong device.
 
 ## Troubleshooting
 
-- **My machine isn't showing up in the browser picker.**
-  Make sure `spectral serve` is still running (it logs reconnect attempts to
-  stderr). If `spectral login` was run a long time ago and the team key was
-  rotated, re-run `spectral login`.
+- **My machine isn't showing up in the browser picker.** Make sure
+  `spectral serve` is still running (it logs reconnect attempts to stderr). If
+  `spectral login` was run a long time ago and the team key was rotated, re-run
+  `spectral login`.
 
-- **WebSocket keeps disconnecting.**
-  The relay client reconnects automatically with exponential backoff. Brief
-  network blips are expected and handled. If the backoff loop is constant,
-  check that your team API key is still valid and that your network allows
-  outbound WebSocket connections to the configured backend.
+- **WebSocket keeps disconnecting.** The relay client reconnects automatically
+  with exponential backoff. Brief network blips are expected and handled. If the
+  backoff loop is constant, check that your team API key is still valid and that
+  your network allows outbound WebSocket connections to the configured backend.
 
-- **`better-sqlite3` errors on first `spectral serve`.**
-  This usually means the native module didn't compile during install. Try
+- **`better-sqlite3` errors on first `spectral serve`.** This usually means the
+  native module didn't compile during install. Try
   `cd ~/.spectral && npm rebuild better-sqlite3`, or reinstall Spectral after
   ensuring you have a working C/C++ toolchain (`make`, a C compiler, Python).
 
-- **I want to revoke a machine.**
-  Stop `spectral serve` on that device. Machine revocation from the Aexol UI
-  is on the roadmap; today the most reliable approach is to rotate the team
-  API key, which invalidates every machine's relay JWT for that team.
+- **I want to revoke a machine.** Stop `spectral serve` on that device. Machine
+  revocation from the Aexol UI is on the roadmap; today the most reliable
+  approach is to rotate the team API key, which invalidates every machine's
+  relay JWT for that team.
 
 ## Privacy & data
 
 - **Model API keys**:
   - For `spectral` (CLI / TUI mode): live ONLY on the machine, in pi's own
     `~/.pi/agent/auth.json`. Never read or transmitted by Spectral.
-  - For `spectral serve` (relay mode): live on the **backend**, not the
-    machine. The local machine holds only its machine JWT; provider keys
-    are managed centrally and scoped to the team's `BaseModel` whitelist.
+  - For `spectral serve` (relay mode): live on the **backend**, not the machine.
+    The local machine holds only its machine JWT; provider keys are managed
+    centrally and scoped to the team's `BaseModel` whitelist.
 - **Code, messages, file contents, generated artifacts** live ONLY on the
   machine, in `~/.spectral/sessions.db` and the working directory you point
   `spectral serve` at.
 - **The backend stores**: machine identity (id, display name, hostname,
   last-seen timestamps), the relay JWT issued at registration, and team
-  membership. For `spectral serve`, it also holds the centralized provider
-  API keys used to fulfil inference requests on behalf of authorized
-  machines.
+  membership. For `spectral serve`, it also holds the centralized provider API
+  keys used to fulfil inference requests on behalf of authorized machines.
 - **The backend does not store**: prompts, responses, tool calls, files,
   artifacts, or any other message-channel content.
 
@@ -209,5 +207,5 @@ MIT — see [LICENSE](./LICENSE).
 
 - Website: <https://aexol.com>
 - Source is currently hosted in an internal Aexol repository; public mirror TBD.
-- Issues: please file them with your Aexol contact (a public issue tracker
-  is not yet available).
+- Issues: please file them with your Aexol contact (a public issue tracker is
+  not yet available).

package/dist/agent/agents.d.ts

@@ -0,0 +1,37 @@
+/**
+ * Agent discovery and configuration for the subagent delegation extension.
+ *
+ * Agent definitions are markdown files with YAML frontmatter:
+ *
+ *   ---
+ *   name: my-agent
+ *   description: What this agent does
+ *   tools: read, grep, find, ls
+ *   model: claude-haiku-4-5
+ *   ---
+ *   System prompt for the agent goes here.
+ *
+ * Locations:
+ *   ~/.spectral/agent/agents/*.md     — User-level (always loaded)
+ *   .spectral/agents/*.md             — Project-level (opt-in via agentScope)
+ */
+export type AgentScope = "user" | "project" | "both";
+export interface AgentConfig {
+    name: string;
+    description: string;
+    tools?: string[];
+    model?: string;
+    systemPrompt: string;
+    source: "user" | "project";
+    filePath: string;
+}
+export interface AgentDiscoveryResult {
+    agents: AgentConfig[];
+    projectAgentsDir: string | null;
+}
+export declare function discoverAgents(cwd: string, scope: AgentScope): AgentDiscoveryResult;
+export declare function formatAgentList(agents: AgentConfig[], maxItems: number): {
+    text: string;
+    remaining: number;
+};
+//# sourceMappingURL=agents.d.ts.map

package/dist/agent/agents.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"agents.d.ts","sourceRoot":"","sources":["../../src/agent/agents.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAMH,MAAM,MAAM,UAAU,GAAG,MAAM,GAAG,SAAS,GAAG,MAAM,CAAC;AAErD,MAAM,WAAW,WAAW;IAC1B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;IACjB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,YAAY,EAAE,MAAM,CAAC;IACrB,MAAM,EAAE,MAAM,GAAG,SAAS,CAAC;IAC3B,QAAQ,EAAE,MAAM,CAAC;CAClB;AAED,MAAM,WAAW,oBAAoB;IACnC,MAAM,EAAE,WAAW,EAAE,CAAC;IACtB,gBAAgB,EAAE,MAAM,GAAG,IAAI,CAAC;CACjC;AAyED,wBAAgB,cAAc,CAAC,GAAG,EAAE,MAAM,EAAE,KAAK,EAAE,UAAU,GAAG,oBAAoB,CAoBnF;AAED,wBAAgB,eAAe,CAC7B,MAAM,EAAE,WAAW,EAAE,EACrB,QAAQ,EAAE,MAAM,GACf;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,SAAS,EAAE,MAAM,CAAA;CAAE,CAQrC"}

package/dist/agent/index.d.ts

@@ -0,0 +1,29 @@
+/**
+ * Subagent Delegation Extension for Spectral
+ *
+ * Registers a `subagent` tool that allows the coding agent to delegate tasks
+ * to specialized sub-agents running in-process via `agentLoop()`.
+ *
+ * Each subagent invocation runs with its own fresh AgentContext (isolated
+ * context window), keeping the main conversation lean and focused.
+ *
+ * Three execution modes:
+ *   - Single:   { agent: "name", task: "..." }
+ *   - Parallel: { tasks: [{ agent, task }, ...] }  (max 8, 4 concurrent)
+ *   - Chain:    { chain: [{ agent, task: "... {previous} ..." }, ...] }
+ *
+ * Agent definitions live as markdown files with YAML frontmatter:
+ *   - ~/.spectral/agent/agents/*.md    (user-level, always loaded)
+ *   - .spectral/agents/*.md            (project-level, opt-in via agentScope)
+ *
+ * Subagents use an in-process `agentLoop()` for:
+ *   - Clean context isolation (fresh messages array)
+ *   - Combined system prompt (main agent + subagent-specific instructions)
+ *   - Tool filtering (only the tools specified in agent config)
+ *   - Model selection (session model preferred, agent-configured as fallback)
+ *   - Signal propagation (abort passthrough)
+ *   - Access to observational memory via the recall tool
+ */
+import { type ExtensionAPI } from "../sdk/coding-agent/index.js";
+export default function subagentExtension(pi: ExtensionAPI): void;
+//# sourceMappingURL=index.d.ts.map

package/dist/agent/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/agent/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AAWH,OAAO,EACN,KAAK,YAAY,EAEjB,MAAM,8BAA8B,CAAC;AAqetC,MAAM,CAAC,OAAO,UAAU,iBAAiB,CAAC,EAAE,EAAE,YAAY,GAAG,IAAI,CAqThE"}

package/dist/cli.d.ts

@@ -0,0 +1,17 @@
+#!/usr/bin/env node
+/**
+ * @aexol/spectral — Coding agent that never sleeps
+ *
+ * Headless CLI wrapper — no TUI mode supported.
+ *
+ * Subcommand routing:
+ *  - `spectral login`  → interactive auth flow (writes ~/.spectral/config.json)
+ *  - `spectral logout` → deletes ~/.spectral/config.json
+ *  - `spectral serve`  → start the Aexol relay WebSocket server (headless)
+ *  - `spectral bind`   → link directory to an Aexol Studio project
+ *  - `spectral unbind` → remove Aexol Studio project binding
+ *  - `spectral --version` / `--help` → branded short-circuits, no auth needed.
+ *  - anything else → error with usage hint.
+ */
+export {};
+//# sourceMappingURL=cli.d.ts.map

package/dist/cli.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";AACA;;;;;;;;;;;;;GAaG"}

package/dist/commands/bind.d.ts

@@ -0,0 +1,12 @@
+/**
+ * `spectral bind` — link the current directory to an Aexol Studio project.
+ *
+ * Usage:
+ *   spectral bind <project-id> [--team-id <id>] [--name <name>] [--force]
+ *
+ * Writes `.aexol/aexol.jsonc` so that `spectral` knows which Studio project
+ * this repository belongs to. By default it refuses to overwrite an existing
+ * binding; pass `--force` to rebind.
+ */
+export declare function runBind(args: string[]): Promise<void>;
+//# sourceMappingURL=bind.d.ts.map

package/dist/commands/bind.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"bind.d.ts","sourceRoot":"","sources":["../../src/commands/bind.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAUH,wBAAsB,OAAO,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAyF3D"}

package/dist/commands/login-oauth.d.ts

@@ -0,0 +1,15 @@
+/**
+ * OAuth login for CLI machine ownership (called from interactive `spectral login`).
+ *
+ * Flow:
+ *   1. Start a temporary HTTP server on a random localhost port.
+ *   2. Open the browser to `https://aexol.ai/cli-auth?port=<PORT>`.
+ *   3. Wait for the browser to redirect to `http://localhost:<PORT>?token=<JWT>`.
+ *   4. Save the token to `~/.spectral/config.json` as `userJwt`.
+ *   5. Shutdown the HTTP server and exit.
+ *
+ * On failure (timeout, network error, user closes browser), the server shuts
+ * down after a configurable timeout (default 120s).
+ */
+export declare function runLoginOAuth(): Promise<void>;
+//# sourceMappingURL=login-oauth.d.ts.map

package/dist/commands/login-oauth.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"login-oauth.d.ts","sourceRoot":"","sources":["../../src/commands/login-oauth.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAsEH,wBAAsB,aAAa,IAAI,OAAO,CAAC,IAAI,CAAC,CA4EnD"}

package/dist/commands/login.d.ts

@@ -0,0 +1,37 @@
+/**
+ * `spectral login` — interactive authentication against the Aexol MCP backend.
+ *
+ * Flow:
+ *   1. Choose auth method: Team API key or OAuth (browser).
+ *   2a. API key: prompt for team API key (masked input). Verify the
+ *       sk-aexol-team- prefix locally so we don't send obviously-wrong
+ *       credentials. The API URL is taken from env or the hard default.
+ *   2b. OAuth: open browser for Aexol Studio authorization.
+ *   3. Verify reachability + auth by calling tools/list against the URL.
+ *   4. On success: persist to ~/.spectral/config.json (mode 0600).
+ *
+ * Exits non-zero on any failure so shell scripts can detect it.
+ *
+ * NOTE: pure logic lives in `performLogin` — the interactive `runLogin`
+ * wrapper delegates to it after collecting prompts. Tests target
+ * `performLogin` directly so we don't have to drive `@inquirer/prompts`.
+ */
+export interface PerformLoginOptions {
+    apiUrl: string;
+    teamApiKey: string;
+}
+export interface PerformLoginResult {
+    toolCount: number;
+}
+/**
+ * Pure login logic. Throws `Error` with one of these stable message prefixes:
+ *   - "Invalid API key prefix"  — local validation failed
+ *   - "Invalid token"           — server returned 401/403
+ *   - "Authentication failed"   — server rejected the request (other 4xx/5xx)
+ *   - "Could not reach"         — network error (DNS, refused connection, timeout)
+ *
+ * Tests assert on these substrings.
+ */
+export declare function performLogin(opts: PerformLoginOptions): Promise<PerformLoginResult>;
+export declare function runLogin(): Promise<void>;
+//# sourceMappingURL=login.d.ts.map

package/dist/commands/login.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"login.d.ts","sourceRoot":"","sources":["../../src/commands/login.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAgBH,MAAM,WAAW,mBAAmB;IAClC,MAAM,EAAE,MAAM,CAAC;IACf,UAAU,EAAE,MAAM,CAAC;CACpB;AAED,MAAM,WAAW,kBAAkB;IACjC,SAAS,EAAE,MAAM,CAAC;CACnB;AAED;;;;;;;;GAQG;AACH,wBAAsB,YAAY,CAAC,IAAI,EAAE,mBAAmB,GAAG,OAAO,CAAC,kBAAkB,CAAC,CAqCzF;AAED,wBAAsB,QAAQ,IAAI,OAAO,CAAC,IAAI,CAAC,CAyE9C"}

package/dist/commands/logout.d.ts

@@ -0,0 +1,8 @@
+/**
+ * `spectral logout` — remove the persisted Aexol credentials.
+ *
+ * Idempotent: missing config is not an error. Always exits 0 unless the
+ * filesystem itself misbehaves (in which case we surface the OS error).
+ */
+export declare function runLogout(): Promise<void>;
+//# sourceMappingURL=logout.d.ts.map

package/dist/commands/logout.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"logout.d.ts","sourceRoot":"","sources":["../../src/commands/logout.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAMH,wBAAsB,SAAS,IAAI,OAAO,CAAC,IAAI,CAAC,CAa/C"}