@taskless/cli-nightly 0.11.0-20260820055459x599d3f3

package/dist/prompts/index.d.ts

@@ -0,0 +1,61 @@
+import { type RecipeOptions } from "./recipes.js";
+/**
+ * Public entry for `@taskless/cli/prompts`.
+ *
+ * Everything here renders through the same embedded recipe text and the same
+ * render path `taskless agent <topic>` serves, so the two surfaces cannot emit
+ * different guidance. Nothing in this graph reaches the CLI runtime: no citty
+ * command tree, no telemetry, no filesystem or network, so a Worker can import
+ * it without dragging the CLI in behind it.
+ */
+/**
+ * Topics exported as public API. Hand-maintained rather than derived from the
+ * recipe files, because an exported name is a promise held for a major version
+ * and a new `help/*.txt` must not be able to publish one by existing. The
+ * completeness check in `test/prompts.test.ts` asserts this list plus
+ * {@link INTERNAL_TOPICS} accounts for every canonical recipe on disk.
+ *
+ * The list starts at what a consumer has actually asked for and grows on
+ * demand. It is the authoring recipe for each engine a rule can be routed to,
+ * so a consumer that can decide a rule belongs to an engine can also reach the
+ * procedure for writing one. Exporting a chooser without its destinations
+ * reproduces, for the platform generator, the dead end this surface exists to
+ * remove.
+ *
+ * `engine-selection` used to be exported alongside them. It no longer exists:
+ * the criterion it carried now lives in `route`, stated once. `route` is not
+ * exported yet because it still contains local mechanics (`taskless detect`,
+ * on-device authoring) a Worker cannot run; until it is, a consumer gets each
+ * destination's own scope from these three and adjudicates genuinely ambiguous
+ * calls itself.
+ */
+export declare const TOPICS: readonly ["create-sg-rule", "create-vale-rule", "create-runtime-rule"];
+/**
+ * Recipes deliberately withheld from the export, recorded so they stay visible
+ * decisions rather than oversights. Two groups:
+ *
+ * - Command recipes (`auth` … `update`) walk an agent through running a CLI
+ *   subcommand on a developer's machine. There is no caller for them outside
+ *   the CLI that hosts those commands.
+ * - Authoring recipes are unreachable server-side: `route` picks an authoring
+ *   destination before the service is involved, `create-remote-rule` states
+ *   the boundary from the client's side, `detect` documents a CLI subprocess a
+ *   Worker cannot spawn, `create-legacy-rule` targets a local toolchain, and
+ *   `rule-meta` reads an `improve-rule` sidecar file.
+ */
+export declare const INTERNAL_TOPICS: readonly ["auth", "check", "ci", "create-legacy-rule", "create-remote-rule", "delete-rule", "detect", "improve-rule", "info", "init", "onboard", "route", "rule", "rule-meta", "update", "verify-rule"];
+/** A topic name the package exports. Unknown names fail to type-check. */
+export type PromptTopic = (typeof TOPICS)[number];
+/** Options accepted by every prompt render function. */
+export type PromptOptions = RecipeOptions;
+/**
+ * Render a prompt to finished text. Every `%(KEY)s` placeholder is resolved
+ * from values the package already holds, so the caller never handles a
+ * template dialect.
+ *
+ * @throws when the topic has no canonical recipe in the build, which means
+ * {@link TOPICS} and the recipe files have diverged.
+ */
+export declare function getPrompt(topic: PromptTopic, options?: PromptOptions): string;
+/** Every exported topic as a render function, keyed by topic name. */
+export declare const PROMPTS: Record<PromptTopic, (options?: PromptOptions) => string>;

package/dist/prompts/recipes.d.ts

@@ -0,0 +1,36 @@
+/** The canonical `<topic>.txt` recipe names present in the build. */
+export declare function canonicalRecipeTopics(): string[];
+/** Options accepted by the shared render path. */
+export interface RecipeOptions {
+    /**
+     * Select the `.anonymous` variant of the topic, falling back to the
+     * canonical recipe when the topic has no variant.
+     *
+     * @default false
+     */
+    anonymous?: boolean;
+    /**
+     * Value substituted for the `%(PACKAGE_MANAGER_DLX)s` placeholder. The
+     * default is an agent-fill marker, which is the right answer whenever
+     * the caller does not know the consuming repo's package manager.
+     *
+     * @default "<package-manager-dlx>"
+     */
+    packageManagerDlx?: string;
+    /**
+     * Include the `# Topic: <name> (CLI v<version> / topic vN)` first line.
+     * Suppressing it drops the CLI version from the text, which matters to
+     * an LLM consumer whose prompt-cache key would otherwise churn on every
+     * CLI publish.
+     *
+     * @default true
+     */
+    header?: boolean;
+}
+/**
+ * Look up a help topic from the embedded recipe map and return the rendered
+ * text. Anonymous variants are preferred when `anonymous` is set and a
+ * variant exists; otherwise the canonical recipe is returned. Returns
+ * `undefined` when the topic is unknown.
+ */
+export declare function getRecipe(topic: string, options?: RecipeOptions): string | undefined;

package/dist/prompts.js

@@ -0,0 +1,43 @@
+import { F as o } from "./recipes-Ay7coxQs.js";
+const i = [
+  "create-sg-rule",
+  "create-vale-rule",
+  "create-runtime-rule"
+], n = [
+  "auth",
+  "check",
+  "ci",
+  "create-legacy-rule",
+  "create-remote-rule",
+  "delete-rule",
+  "detect",
+  "improve-rule",
+  "info",
+  "init",
+  "onboard",
+  "route",
+  "rule",
+  "rule-meta",
+  "update",
+  "verify-rule"
+];
+function a(e, r) {
+  const t = o(e, r);
+  if (t === void 0)
+    throw new Error(
+      `No recipe is embedded for prompt topic "${e}". This is a packaging fault: TOPICS lists a topic with no help/${e}.txt behind it.`
+    );
+  return t;
+}
+const u = Object.fromEntries(
+  i.map((e) => [
+    e,
+    (r) => a(e, r)
+  ])
+);
+export {
+  n as INTERNAL_TOPICS,
+  u as PROMPTS,
+  i as TOPICS,
+  a as getPrompt
+};