carrick 0.3.65 → 0.3.66

package/dist/init/run.d.ts

@@ -1,26 +1,22 @@
 import { type ResolvedRepos } from "../auth/read.ts";
+import { type WorkspaceProposal } from "./repos.ts";
+import { type McpOutcome } from "./mcp.ts";
 /**
- * The prompt that makes an agent write this repo's config and setup files.
+ * The one sentence the run ends on.
  *
- * A copy of the `scaffold` MCP tool's own instructions and the dashboard copy
- * beside them (carrick-cloud#800), whose test checks every filename against
- * what the tool returns. It is printed here so the terminal path ends where
- * the dashboard path ends, and it states the sequence the ruling in
- * carrick-cloud#799 fixed: the agent writes a complete `carrick.json` from the
- * proposal this command derived, READS it back against the repo, and then runs
- * the one scan. There is no rehearsal in front of it — `carrick index` is the
- * only scan in the flow (carrick#1008, cloud#832), and a facts-only pass has
- * no user here, so nothing in this copy names one. Keep the two copies in
- * step; the tool's instructions, not this text, decide what gets written.
+ * The scaffold tool carries the instructions — which files to create, how to
+ * seed `carrick.json` from the proposal, whether to run the scan at all
+ * (carrick-cloud#832) — so the terminal names the tool and stops. The copy
+ * that used to stand here was a second statement of the same instructions, and
+ * two copies of a sequence drift.
  *
- * One clause is this side's alone, because only this side knows it: whether
- * the workspace read found a hosted index for these repos. Where there is one,
- * the scan has already run in CI and a laptop scan from a branch would replace
- * that row for everyone in the workspace, so the agent runs no scan at all and
- * checks the config by reading it (carrick#993, cloud half carrick-cloud#805,
- * cloud#832).
+ * The argument is named because the tool's branch turns on it and turns soft
+ * without it: `repo` is what resolves the hosted rows, and with no `repo` the
+ * response keeps its default ending and tells the agent to run the scan — on a
+ * repo CI already indexes, which is the row the whole workspace reads
+ * (carrick-cloud `src/tools/scaffold.ts`, cloud#805 item 1).
  */
-export declare function agentScaffoldPrompt(hosted: boolean): string;
+export declare const SCAFFOLD_SENTENCE = "Run the carrick scaffold tool for this repo, passing its owner/repo as `repo`, and follow what it returns.";
 export type InitOptions = {
     workspace: string;
     /** Require every proposed GitHub repo to belong to this project. */
@@ -35,27 +31,45 @@ export declare function parseArgs(argv: string[], cwd?: string): InitOptions | s
  * The repos a project holds that this folder does not, one line per project.
  *
  * Carrick answers across every repo in a project, so a machine holding half of
- * one gets half the answers, and the connection lines above name only what is
+ * one gets half the answers, and the connection line above names only what is
  * here. `project_repos` is the workspace read's answer to that: the whole
  * membership of every project the requested repos are in (carrick#993 row 18).
  * Capped and counted like the identity lines, because a project can hold two
  * hundred.
  */
 export declare function absentRepos(identity: ResolvedRepos, names: string[], project: string | null): string[];
+/** The repos this run connected, as one line however many there are. */
+export declare function connectedLine(names: string[]): string;
 /**
- * The editor lines, one line per editor that is on the machine.
+ * What the derive found, in the words the workspace stated it in.
  *
- * `--install-extension <id>` resolves the id against that editor's own gallery,
- * and the three editors below read three different ones: VS Code the VS Code
- * Marketplace, Cursor and Windsurf each their own. The extension is published
- * to all three, so the id is a command every one of them can run
- * (carrick#915). Any other editor gets the server's command and no claim about
- * the editor: the per-editor results table in `plugin/TEST-PLAN.md` section 6
- * is still empty.
+ * The manifest kind is the scanner's own `reason` for each repo — "npm
+ * workspaces", "pnpm workspaces", "Deno manifests", "carrick.json", "single
+ * repository", or a `+` join of them (`src/service_derivation.rs`) — and it is
+ * named only where every repo here agrees on one, because a mixed workspace
+ * has no one word for what was found.
+ */
+export declare function packagesFound(plan: WorkspaceProposal): string;
+/** The line that states it, and names where the proposal landed. */
+export declare function packagesLine(plan: WorkspaceProposal): string;
+/**
+ * The one line for the hooks and the MCP connection.
+ *
+ * A client is named only where this run changed something for it: an "already
+ * connected" line is a line about nothing, and a first run prints four of them
+ * (carrick#1026). The hooks are always this repo's, so they are always the
+ * subject.
+ */
+export declare function configuredLine(mcp: McpOutcome[]): string;
+/**
+ * One line per other client this run wrote a file for, naming that file.
  *
- * `onPath` is injected so a test can state each machine.
+ * The path is printed because this command guessed it: a client detected by its
+ * own data directory gets an entry written into its own config file, and a
+ * wrong guess has to be one visible line and one entry to delete (`mcp.ts`).
+ * A client left exactly as it was gets no line at all (carrick#1026).
  */
-export declare function editorLines(onPath: (command: string) => boolean): string[];
+export declare function mcpClientLines(mcp: McpOutcome[]): string[];
 export declare function init(argv: string[]): Promise<number>;
-/** `carrick templates <name>`, so the workflow above is one command. */
+/** `carrick templates <name>`, so a workflow is one command. */
 export declare function templates(argv: string[]): number;