@usenaive-sdk/cli 0.15.0 → 1.0.0

package/dist/lib/teams-catalog.d.ts

@@ -1,141 +0,0 @@
-/**
- * THE ONE DECLARATION SITE for the `naive teams` surface (06 §1.4).
- *
- * Two design notes shipped two `teams` command sets and neither was a superset of
- * the other. Two hand-written lists is exactly the drift a one-declaration rule
- * exists to catch, so both are deleted and the union is declared once, here, as
- * DATA. `commands/teams.ts` builds the commander tree by walking this array; it
- * writes no subcommand of its own. A row added here is a working command, and a
- * command that is not a row here does not exist.
- *
- * ── WHY THIS IS A .ts FILE IN THIS PACKAGE AND NOT A GENERATED ARTIFACT ─────
- *
- * 06 §1.4 puts the declaration in `@usenaive/agent-contract/capabilities` and has
- * a generator emit `packages/cli/src/generated/teams-commands.ts` from it, so the
- * CLI subcommand, the MCP tool, the REST path and the openapi operation are all
- * one statement. MEASURED: there is no `packages/agent-contract` directory in
- * this tree and no generator to run, and this task owns `packages/cli` only. A
- * hand-written file that IMITATES a generated one — committed under `generated/`,
- * with nothing that regenerates it — is worse than an honest source file: the
- * next person edits it and their edit is silently the truth.
- *
- * So this is the honest intermediate: ONE declaration, inside the package that
- * consumes it, shaped so a future generator emits exactly this array. The fields
- * a generator would need and the CLI does not (`action`, `rest`, `mcp`,
- * `because`, `fenced`, `write`) are carried anyway, so the day the contract
- * package exists this file is deleted rather than reconciled.
- *
- * ── WHY IT MUST BE ONE LIST AND NOT 28 `.command()` CALLS ───────────────────
- *
- * `src/index.ts` calls `findUnknownSubcommand` BEFORE `parseAsync` and hard-fails
- * on an unrecognised subcommand even with `--help` appended. A subcommand list
- * that can drift from the thing that answers it therefore makes VALID commands
- * fail with `cli_outdated`, rather than degrading. One array, walked once, cannot
- * drift from itself.
- */
-/** Where a flag's value goes on the wire. `client` never leaves the process. */
-export type FlagIn = "query" | "body" | "path" | "client";
-export interface FlagSpec {
-    /** Commander syntax, verbatim: `--status <status>` or `--follow`. */
-    readonly flag: string;
-    /** The key commander puts on the options object. */
-    readonly key: string;
-    readonly describe: string;
-    readonly in: FlagIn;
-    /** Wire field name. Defaults to `key`. */
-    readonly field?: string;
-    /** `requiredOption` rather than `option` — see `--because` below. */
-    readonly required?: boolean;
-    /** Parse the value as an integer before sending it. */
-    readonly int?: boolean;
-    /**
-     * A boolean flag that SELECTS a value for a shared wire field instead of
-     * sending its own name as a field.
-     *
-     * `--allow` is not a field this API has. The field is `decision` and `--allow`
-     * is one of its two values (`POST …/approvals/:id/decide` throws
-     * `invalid_input: decision must be "approve" or "deny"` on anything else). The
-     * first spelling of this catalog declared `--allow` and `--deny` as ordinary
-     * body flags, so the CLI sent `{"allow":true,"because":"…"}` and the one
-     * mounted write on the whole `/v1/teams` surface could not be invoked at all.
-     *
-     * A flag declaring `value` MUST also declare `field`; flags sharing a `field`
-     * form a mutually exclusive group, and `selectorGroups()` derives that group
-     * rather than listing it, so a third value cannot be added without joining the
-     * exclusion.
-     */
-    readonly value?: string;
-}
-export interface ArgSpec {
-    /** Commander syntax, verbatim: `<team>` or `[channel]`. */
-    readonly arg: string;
-    /** The bare name, for path substitution and body keys. */
-    readonly name: string;
-    readonly describe: string;
-    readonly in: "path" | "body";
-    /** Wire field name. Defaults to `name`. */
-    readonly field?: string;
-}
-export interface TeamOp {
-    /** The subcommand name under `naive teams`. */
-    readonly cli: string;
-    readonly describe: string;
-    /** The governance ActionId this op is evaluated as. */
-    readonly action: string;
-    readonly method: "GET" | "POST" | "DELETE";
-    /** `{name}` placeholders are filled from `{team}`, `{tenant}` and path args. */
-    readonly path: string;
-    /** Does this op need `--tenant`? True for all 28 except `list` (R-4). */
-    readonly tenant: boolean;
-    /** Does it pass through the write fence? Printed in `--help`, not enforced here. */
-    readonly fenced: boolean;
-    readonly write: boolean;
-    /** The MCP tool name, or `false` with a mandatory `because`. */
-    readonly mcp: string | false;
-    readonly because?: string;
-    readonly args: readonly ArgSpec[];
-    readonly flags: readonly FlagSpec[];
-    /** Reads a stream rather than a JSON body. Exactly one op does. */
-    readonly streams?: true;
-}
-export declare const TEAM_OPS: readonly TeamOp[];
-export declare class TeamOpError extends Error {
-}
-/** Every `{placeholder}` this op's path expects. */
-export declare function pathPlaceholders(op: TeamOp): string[];
-/**
- * Fill the path. Every value is `encodeURIComponent`'d — a team name or a card id
- * that contains a slash must not be able to reach a different route, and an
- * absent value is an error rather than the literal string "undefined" in a URL.
- */
-export declare function buildPath(op: TeamOp, values: Readonly<Record<string, string | undefined>>): string;
-/** The query string, including its leading `?`, or `""`. */
-export declare function buildQuery(op: TeamOp, opts: Readonly<Record<string, unknown>>): string;
-/**
- * The request body: positional args declared `in: "body"`, then flags declared
- * `in: "body"`. A GET has no body at all — a GET that carries one is a request
- * some proxy will strip and some server will ignore, which is a silent wrong
- * answer rather than an error.
- */
-export declare function buildBody(op: TeamOp, args: Readonly<Record<string, unknown>>, opts: Readonly<Record<string, unknown>>): Record<string, unknown> | undefined;
-/**
- * The mutually exclusive selector groups on this op, keyed by the wire field
- * they share. DERIVED from the flags rather than listed, so a third member added
- * to a group joins the exclusion without anyone remembering to widen a list.
- */
-export declare function selectorGroups(op: TeamOp): Map<string, FlagSpec[]>;
-/**
- * Refuse an ambiguous or absent decision BEFORE the request leaves the process.
- *
- * A selector group is a CHOICE: exactly one member must be given. Neither branch
- * can be left to the server. `--allow --deny` would otherwise resolve by flag
- * order in this file — an approval decided by declaration order — and giving
- * neither would send a body with no `decision`, which `settle` (whose openapi
- * marks nothing required) would accept as a well-formed request that settles an
- * effect no particular way.
- */
-export declare function assertSelectors(op: TeamOp, opts: Readonly<Record<string, unknown>>): void;
-/** `failOnTerminal` -> `fail_on_terminal`. Flags are camelCase in commander and
- *  snake_case on this API's wire; converting in one place keeps the two apart. */
-export declare function snake(key: string): string;
-export declare function findOp(cli: string): TeamOp | undefined;