indusagi-coding-agent 0.2.4 → 0.2.5

package/dist/types/console/theme/palette.d.ts

@@ -1,77 +0,0 @@
-/**
- * Theme palettes — the console's own re-derived accent ramps.
- *
- * This module owns the two raw {@link ThemePalette} values the console ships
- * with, one per {@link ThemeScheme}. A palette is the *source* nine-stop ramp a
- * scheme is built from: three accent hues (a cool primary, a warm secondary, a
- * muted support tertiary), a three-stop neutral text gradient (ink/body/muted),
- * and the three status hues (affirm/caution/alarm). Everything the console
- * renders is computed from these stops by the token derivation step — no module
- * downstream of here writes a literal hex.
- *
- * The hex values are an original ramp authored for this console. The cool
- * primary is a desaturated spring-green/teal, the warm secondary a tangerine
- * amber, and the support tertiary a soft periwinkle; the neutral gradient is a
- * cool slate. The `daylight` variant re-derives the same roles at higher
- * saturation / lower luminance so they read on a bright terminal background.
- * None of these stops reuse an upstream accent — they were picked fresh against
- * a contrast target for each role.
- */
-import type { ThemePalette, ThemeScheme } from "../contract";
-/**
- * The dark-terminal ramp.
- *
- * Cool spring-teal primary against a cool-slate neutral gradient, with a warm
- * amber secondary for contrast accents and a soft periwinkle support tone.
- */
-export declare const MIDNIGHT_PALETTE: ThemePalette;
-/**
- * The light-terminal ramp.
- *
- * The same role assignments re-derived deeper and more saturated so each hue
- * keeps its contrast against a bright background; the neutral gradient inverts
- * to a dark-on-light slate.
- */
-export declare const DAYLIGHT_PALETTE: ThemePalette;
-/**
- * The "IndusCode Saffron" dark-terminal ramp — the brand scheme.
- *
- * The console's signature look: a warm saffron primary (borders, headings, the
- * brand wordmark) against a cream neutral gradient, with a cool teal secondary
- * for the interactive accents (the prompt caret, chips, bullets) — the two hues
- * the IndusCode masthead is built from. The status hues stay warm-leaning so the
- * whole scheme reads as one saffron identity rather than a recoloured midnight.
- */
-export declare const SAFFRON_PALETTE: ThemePalette;
-/**
- * The dark-terminal color-blind-safe ramp.
- *
- * A clone of {@link MIDNIGHT_PALETTE} that re-derives the three *status* hues so
- * a red-green color-blind user (deuteran/protan, ~8% of men) can tell success
- * from failure without relying on the red-green axis. Success moves off green
- * onto a vivid blue (`affirm → #4aa3ff`); failure stays red but is deepened to a
- * darker tone (`alarm → #c83232`) so it sits well below the bright blue in
- * lightness, and the amber warning is nudged brighter — so the three status
- * tones separate by *lightness*, not hue alone. The three accent hues and the
- * neutral gradient are carried over unchanged from the base midnight ramp — only
- * the status stops move, so the overall look stays the midnight scheme.
- */
-export declare const MIDNIGHT_CB_PALETTE: ThemePalette;
-/**
- * The light-terminal color-blind-safe ramp.
- *
- * The daylight counterpart of {@link MIDNIGHT_CB_PALETTE}: clones
- * {@link DAYLIGHT_PALETTE} and remaps success to a deeper blue tuned for a
- * bright background (`affirm → #1f6fd6`), deepens the red alarm
- * (`alarm → #b02622`) for lightness separation from that blue, and darkens the
- * amber warning so the three status tones stay separable by lightness on a light
- * terminal too.
- */
-export declare const DAYLIGHT_CB_PALETTE: ThemePalette;
-/**
- * The raw ramp for each scheme, keyed by {@link ThemeScheme}.
- *
- * The token derivation step reads from this table; the resolver returns the
- * scheme whose palette it expanded.
- */
-export declare const PALETTES: Readonly<Record<ThemeScheme, ThemePalette>>;

package/dist/types/console/theme/resolve.d.ts

@@ -1,45 +0,0 @@
-/**
- * Theme resolution — assemble the fully-resolved {@link ConsoleTheme} for each
- * scheme and expose the picker entry points.
- *
- * This is the top of the theme engine. It runs the pipeline once per scheme at
- * module load:
- *
- *   palette  ──deriveTokens──▶  tokens  ──themeAdapter──▶  framework adapter
- *      └──────────────────────────┴───────────────────────────┘
- *                          ConsoleTheme
- *
- * The two assembled themes are frozen into {@link THEMES}; {@link resolveTheme}
- * is the single sanctioned way the surface obtains the theme for a scheme name.
- * Because the heavy work (chalk adapter construction) happens here at the
- * config-load boundary, the render path only ever reads an already-built
- * {@link ConsoleTheme} — it never re-derives colours.
- */
-import { type ConsoleTheme, type ThemeScheme } from "../contract";
-/**
- * The built-in themes, fully resolved and keyed by {@link ThemeScheme}.
- *
- * Assembled once at load time from {@link PALETTES}. This is the table the
- * theme picker lists and {@link resolveTheme} reads; it is the console's
- * complete shipped theme set.
- */
-export declare const THEMES: Readonly<Record<ThemeScheme, ConsoleTheme>>;
-/**
- * Resolve a scheme name to its fully-built {@link ConsoleTheme}.
- *
- * The single entry point the surface and the loader use to turn a scheme name
- * (from settings, a slash argument, or the {@link DEFAULT_SCHEME}) into a theme.
- * An unrecognised or absent name falls back to {@link DEFAULT_SCHEME} rather
- * than throwing, so a corrupt preference never blanks the console.
- *
- * @param scheme a candidate scheme name, possibly invalid or undefined
- * @returns the resolved theme for that scheme, or the default theme
- */
-export declare function resolveTheme(scheme?: string | null): ConsoleTheme;
-/**
- * The schemes the console offers, in picker order.
- *
- * Derived from {@link THEMES} so adding a scheme to the table adds it to the
- * picker with no second list to update.
- */
-export declare const THEME_SCHEMES: readonly ThemeScheme[];

package/dist/types/console/theme/theme.test.d.ts

@@ -1,16 +0,0 @@
-/**
- * Theme engine — pure behavioural tests.
- *
- * Four concerns, all exercised without mounting Ink:
- *   1. The two ramps are valid six-digit hex and structurally complete.
- *   2. Token derivation is total and binds every semantic role to a ramp stop.
- *   3. The framework-key projection covers every key the shipped react-ink
- *      components request, sourced from the right token role.
- *   4. The resolver returns the right theme per scheme and falls back to the
- *      default for any unrecognised / missing name, and the assembled
- *      {@link ConsoleTheme} carries a live framework adapter.
- *
- * Clean-room guard: an explicit assertion that no produced hex collides with a
- * known upstream accent, enforced across both ramps and the derived tokens.
- */
-export {};

package/dist/types/console/theme/tokens.d.ts

@@ -1,62 +0,0 @@
-/**
- * Token derivation — expand a raw {@link ThemePalette} into the semantic
- * {@link ThemeTokens} the console actually renders against.
- *
- * The console body never names a hex or a palette stop; it names a *role*
- * (`signal`, `frame`, `bodyText`, `alarm`, …). This module is the one place the
- * thirteen roles are bound to ramp stops. The mapping is pure and total: every
- * key of {@link ThemeTokens} is assigned exactly once from a {@link ThemePalette}
- * field, so a ramp that is missing a stop fails to type-check rather than
- * producing an undefined colour at render time.
- *
- * Role → stop assignments (identical structure for both schemes; the schemes
- * differ only in the underlying ramp):
- *
- *   - `signal`        ← `primary`    (the dominant accent: focus, selection)
- *   - `frame`         ← `tertiary`   (default structural border lines)
- *   - `quietFrame`    ← `muted`      (de-emphasised separators)
- *   - `promptSurface` ← `secondary`  (the composer's active tint)
- *   - `cardAccent`    ← `secondary`  (row gutters and headers)
- *   - `bodyText`      ← `body`       (default answer foreground)
- *   - `mutedText`     ← `muted`      (timestamps, hints, metadata)
- *   - `inkText`       ← `ink`        (high-contrast text on an accent)
- *   - `notice`        ← `tertiary`   (informational tone)
- *   - `affirm`        ← `affirm`     (success tone)
- *   - `caution`       ← `caution`    (warning tone)
- *   - `alarm`         ← `alarm`      (error/fault tone)
- *   - `pending`       ← `primary`    (busy/in-flight tone)
- *
- * Rich-render roles (markdown / diff / syntax highlighting) are derived from the
- * same nine stops so the rebuild's new styled-transcript / colored-diff /
- * fenced-code surfaces recolour with the scheme and need no extra palette stop:
- *
- *   - `codeInline`      ← `primary`                      (inline code accent)
- *   - `heading`         ← `primary`                      (heading accent)
- *   - `blockquoteBar`   ← `muted`                        (dim quote bar)
- *   - `diffAddedBg`     ← `affirm` darkened toward ink   (added-line tint)
- *   - `diffRemovedBg`   ← `alarm`  darkened toward ink   (removed-line tint)
- *   - `diffAddedText`   ← `affirm`                       (added foreground / `+`)
- *   - `diffRemovedText` ← `alarm`                        (removed foreground / `-`)
- *   - `synKeyword`      ← `primary`                      (keywords)
- *   - `synString`       ← `affirm`                       (strings)
- *   - `synNumber`       ← `caution`                      (numbers)
- *   - `synComment`      ← `muted`                        (comments)
- *   - `synType`         ← `tertiary`                     (types / classes)
- *
- * Deriving the two diff backgrounds (rather than adding raw stops) keeps the
- * {@link ThemePalette} a flat nine-stop ramp while guaranteeing every scheme —
- * including the color-blind variants — gets a legible `+`/`-` tint that tracks
- * its own success/alarm hue.
- */
-import type { ThemePalette, ThemeTokens } from "../contract";
-/**
- * Map a raw accent ramp onto the closed semantic token set.
- *
- * Pure and deterministic: the same palette always yields the same tokens, and
- * the returned object is a fresh frozen value the resolver can cache. The role
- * assignments are shared by both schemes — only the ramp handed in differs.
- *
- * @param palette the raw nine-stop ramp for a scheme
- * @returns the full semantic token map (status + rich-render roles)
- */
-export declare function deriveTokens(palette: ThemePalette): ThemeTokens;

package/dist/types/entry.d.ts

@@ -1,17 +0,0 @@
-#!/usr/bin/env node
-/**
- * Process entry point — the bin the OS launches.
- *
- * Responsibilities, in order:
- *   1. Set `process.title` to the brand's primary bin name so the process is
- *      identifiable in `ps` / activity monitors.
- *   2. Install exactly one console filter that suppresses the transport-layer
- *      `[MCP]` noise the MCP stack emits on stdout/stderr (unless the brand's
- *      debug env var is set, in which case nothing is filtered).
- *   3. Hand the sliced `argv` to {@link boot} and adopt its resolved exit code.
- *
- * The boot call is guarded by an `import.meta` entry check so importing this
- * module (e.g. from a test) does not launch the agent — only running it as the
- * program entry does.
- */
-export {};

package/dist/types/guardrails.d.ts

@@ -1,33 +0,0 @@
-/**
- * Thin guardrails entry — the headless, library-consumable surface of the
- * indusagi coding agent.
- *
- * This barrel re-exports ONLY the deterministic guardrail primitives (the
- * permission rule engine, the bash blocklist, prompt assembly, deck
- * provisioning, and the read-before-edit / checkpoint stores). It deliberately
- * imports from the LEAF modules — never the root `src/index.ts` barrel — so a
- * consumer can pull in the guardrails without dragging in the Ink/React console
- * tree (`export * as consoleUi from "./console"` lives only on the root barrel).
- *
- * Reachable from a published install as `indusagi-coding-agent/guardrails`.
- */
-export { resolveRuleDecision, makeRule, createPermissionGate, READ_ONLY_TOOL_NAMES, EDIT_TOOL_NAMES, } from "./conductor/permissions";
-export type { PermissionRule, PermissionMode, PermissionBehavior, PermissionDecision, } from "./conductor/permissions";
-export { evaluateCatastrophic, bashSubcommandSubjects } from "./conductor/bash-guard";
-export { composeBriefing } from "./briefing/compose";
-export { gatherContextDocs } from "./briefing/context-docs";
-export type { AgentTool, BriefingContext, ContextDoc } from "./briefing/contract";
-export { provisionDeck } from "./capability-deck/provision";
-export { createReadStateStore, READ_STATE_HANDLE_KEY, ReadStateStore } from "./boot/runners/read-state";
-export { createCheckpointStore, CHECKPOINT_HANDLE_KEY, CheckpointStore } from "./boot/runners/checkpoint";
-/**
- * The byte-stable refusal emitted when an edit/write is attempted on a file the
- * agent has not read this session.
- *
- * Surfaced here as the guardrails contract for consumers (e.g. eval fixtures)
- * that assert the refusal verbatim. The literal is intentionally duplicated
- * rather than re-exported because the upstream message lives only as a private
- * module-local const in the framework's read-state gate — it is not part of any
- * public barrel. A reword on either side must update both sites, by design.
- */
-export declare const READ_BEFORE_EDIT_MESSAGE = "File has not been read yet. Read it first before writing to it.";

package/dist/types/index.d.ts

@@ -1,24 +0,0 @@
-/**
- * Package root barrel — the public library surface of the indusagi coding agent.
- *
- * The terminal binary is `entry.ts` (the `indus` / `indusagi` bin). This barrel
- * exposes each subsystem as a namespace for embedding or testing. The agent
- * depends only on the `indusagi` framework package.
- */
-export * as boot from "./boot";
-export * as workspace from "./workspace";
-export * as conductor from "./conductor";
-export * as windowBudget from "./window-budget";
-export * as capabilityDeck from "./capability-deck";
-export * as runtimeBridge from "./runtime-bridge";
-export * as addons from "./addons";
-export * as consoleUi from "./console";
-export * as channels from "./channels";
-export * as briefing from "./briefing";
-export * as transcriptExport from "./transcript-export";
-export * as launch from "./launch";
-export * as insight from "./insight";
-export * as kit from "./kit";
-export * as settings from "./settings";
-export * as sessions from "./sessions";
-export { VERSION } from "./workspace";

package/dist/types/insight/channel.d.ts

@@ -1,45 +0,0 @@
-/**
- * Signal channel — the in-memory pipe between the recorder and the sinks.
- *
- * The recorder *pushes* {@link Signal}s the instant a probe opens, updates, or
- * closes; a {@link Sink} *pulls* a {@link SignalStream} (an
- * `AsyncIterable<Signal>`) and drains it at its own pace. A
- * {@link SignalChannel} bridges those two models: it is an unbounded
- * push-to-pull queue with back-pressure expressed by pull latency.
- *
- * Mechanics: when a consumer is parked in `next()` awaiting a value, an emitted
- * signal resolves its promise immediately (no buffering). When no consumer is
- * waiting, the signal is appended to an internal buffer and handed out in FIFO
- * order on the next pull. Closing the channel makes the iterator finish once the
- * buffer drains. The channel multiplexes: every call to {@link stream} returns an
- * independent iterator, and each emitted signal is fanned out to all of them, so
- * the console, file, and network sinks can each drain the same trail.
- */
-import { SignalEmit, SignalStream } from "./contract";
-/**
- * A fan-out push-to-pull pipe of {@link Signal}s.
- *
- * The recorder holds the {@link SignalChannel.emit} end; each sink holds a
- * {@link SignalStream} obtained from {@link SignalChannel.stream}. Producers
- * never block: emitting onto a channel with no parked consumer just buffers.
- */
-export interface SignalChannel {
-    /** Push one signal to every attached subscriber. A no-op once closed. */
-    readonly emit: SignalEmit;
-    /** Attach a new independent consumer; returns its pull-model stream. */
-    stream(): SignalStream;
-    /** How many subscribers are currently attached. */
-    readonly size: number;
-    /** Whether {@link close} has been called. */
-    readonly closed: boolean;
-    /** Finish every attached stream once its buffer drains. Idempotent. */
-    close(): void;
-}
-/**
- * Create a fresh, empty {@link SignalChannel}.
- *
- * The returned channel starts with no subscribers; call {@link SignalChannel.stream}
- * once per sink before emitting if those sinks must observe the first signal.
- * (A subscriber only receives signals emitted after it attaches.)
- */
-export declare function createChannel(): SignalChannel;