docs(openspec): correct the remaining recipe .txt references to .md

NOT A NORMATIVE CHANGE. Every file under `packages/cli/src/agent/` has
been `.md` since the Vale-coverage change, and the build globs
`../agent/*.md`; verified there are 22 recipe files and zero `.txt`
among them. The specs still described the mechanism in terms of `.txt`,
so the obligations are unchanged and only the filenames they name are
now the real ones.

25 occurrences across five standing specs: cli-agent (recipe lookup,
embedding, template and anonymous-variant requirements), cli (the Vite
embedding scenario), cli-knowledge-prompts (purpose, export, anonymous
variants, topic membership), cli-rules (the improve-rule recipe) and
skills (where recipes live).

NONE of them sit in a requirement this branch's change wrote a delta
for. Checked per line rather than assumed: the deltas touch 'CLI info
subcommand outputs version as JSON', 'Recipe substitution uses
sprintf-js named arguments', the three cli-onboard requirements, and an
added cli-knowledge-prompts requirement, and no corrected line falls in
any of them. So there is no archived copy to keep in step here.

DELIBERATELY LEFT: `requirements.txt` in cli-detect. That is a Python
dependency manifest, which really is a `.txt` file, and rewriting it
would introduce an error rather than remove one.

`openspec/changes/archive/` is untouched, as before: it records what
each change said when it landed.

Author: theCodeDrift

openspec/specs/cli-agent/spec.md

@@ -10,8 +10,8 @@ Defines the `agent` subcommand for the `@taskless/cli` package, including recipe
 
 The CLI SHALL support an `agent` subcommand that accepts at most one positional argument identifying a topic AND an optional `--anonymous` boolean flag. Topics SHALL be addressed by a single token; the subcommand SHALL NOT join multiple positionals into a topic key. When a topic is provided, the subcommand SHALL look up a matching recipe file embedded at build time using the following resolution order:
 
-1. If `--anonymous` is set AND `<topic>.anonymous.txt` exists in the embedded map, return that file.
-2. Otherwise, return `<topic>.txt`.
+1. If `--anonymous` is set AND `<topic>.anonymous.md` exists in the embedded map, return that file.
+2. Otherwise, return `<topic>.md`.
 3. If neither exists, exit with code 1 and an error message suggesting `taskless agent` for the topic index.
 
 When no positional argument is provided, the subcommand SHALL print a topic index containing a one-paragraph human slug followed by a topic disambiguation table mapping topic names to their summaries.
@@ -21,18 +21,18 @@ The subcommand is named for its reader. It serves agents fetching a procedure, n
 #### Scenario: Agent subcommand for a topic returns the recipe
 
 - **WHEN** a user runs `taskless agent check`
-- **THEN** the CLI SHALL print the contents of `check.txt` to stdout
+- **THEN** the CLI SHALL print the contents of `check.md` to stdout
 
 #### Scenario: Multi-word topic paths are not resolved
 
 - **WHEN** a user runs `taskless agent rule create`
-- **THEN** the CLI SHALL NOT look up `rule-create.txt` by joining the positionals
+- **THEN** the CLI SHALL NOT look up `rule-create.md` by joining the positionals
 - **AND** it SHALL exit non-zero rather than guessing a topic
 
 #### Scenario: Formerly nested topics are addressed by one token
 
 - **WHEN** a user runs `taskless agent improve-rule`
-- **THEN** the CLI SHALL look up `improve-rule.txt` and print its contents
+- **THEN** the CLI SHALL look up `improve-rule.md` and print its contents
 
 #### Scenario: The former command name is gone
 
@@ -41,7 +41,7 @@ The subcommand is named for its reader. It serves agents fetching a procedure, n
 
 ### Requirement: Recipe files are embedded at build time
 
-Recipe files SHALL be located at `packages/cli/src/agent/` as plain `.txt` files. The Vite build SHALL embed these files into the CLI bundle via `import.meta.glob` with raw imports. A recipe file SHALL exist for every registered command and subcommand.
+Recipe files SHALL be located at `packages/cli/src/agent/` as `.md` files. The Vite build SHALL embed these files into the CLI bundle via `import.meta.glob` with raw imports. A recipe file SHALL exist for every registered command and subcommand.
 
 #### Scenario: Recipe files are available without filesystem access
 
@@ -51,15 +51,15 @@ Recipe files SHALL be located at `packages/cli/src/agent/` as plain `.txt` files
 #### Scenario: Recipe file naming convention
 
 - **WHEN** a recipe file is created for the `rule create` subcommand
-- **THEN** the file SHALL be named `rule-create.txt` in `packages/cli/src/agent/`
+- **THEN** the file SHALL be named `rule-create.md` in `packages/cli/src/agent/`
 
 ### Requirement: Recipe files follow a consistent format
 
-Every recipe file at `packages/cli/src/agent/<topic>.txt` SHALL follow the canonical recipe template: a single-line header `# Topic: <name>     (CLI v%(CLI_VERSION)s / topic v<n>)`, followed by `## Goal`, `## Preconditions`, `## Steps`, optional `## Input schema` (for recipes that take `--from`), `## Errors`, and `## See Also` sections in that order. Recipe templates SHALL use sprintf-js `%(KEY)s` named-argument placeholders for all substitution. The header SHALL embed `%(CLI_VERSION)s` for the CLI version. Topics that document a `--from` input SHALL embed `%(INPUT_SCHEMA)s` inside the `## Input schema` fenced code block. The topic version integer in the header SHALL be a literal value maintained by the recipe author and bumped when the recipe changes meaningfully.
+Every recipe file at `packages/cli/src/agent/<topic>.md` SHALL follow the canonical recipe template: a single-line header `# Topic: <name>     (CLI v%(CLI_VERSION)s / topic v<n>)`, followed by `## Goal`, `## Preconditions`, `## Steps`, optional `## Input schema` (for recipes that take `--from`), `## Errors`, and `## See Also` sections in that order. Recipe templates SHALL use sprintf-js `%(KEY)s` named-argument placeholders for all substitution. The header SHALL embed `%(CLI_VERSION)s` for the CLI version. Topics that document a `--from` input SHALL embed `%(INPUT_SCHEMA)s` inside the `## Input schema` fenced code block. The topic version integer in the header SHALL be a literal value maintained by the recipe author and bumped when the recipe changes meaningfully.
 
 #### Scenario: Recipe contains all template sections
 
-- **WHEN** any `<topic>.txt` file is read
+- **WHEN** any `<topic>.md` file is read
 - **THEN** it SHALL begin with a `# Topic:` header containing `%(CLI_VERSION)s` and the topic version integer
 - **AND** SHALL contain `## Goal`, `## Preconditions`, `## Steps`, `## Errors`, and `## See Also` sections in that order
 
@@ -206,20 +206,20 @@ Fetching a routing recipe SHALL emit the command's single intent event, `cli_age
 
 ### Requirement: Anonymous variant lookup uses a compile-time map
 
-The `agent` command SHALL construct, at build time, a Set of topic names that have a corresponding `<topic>.anonymous.txt` file. Lookup at runtime SHALL be O(1). The Set SHALL be derived from `import.meta.glob` matching `*.anonymous.txt` in the recipe directory.
+The `agent` command SHALL construct, at build time, a Set of topic names that have a corresponding `<topic>.anonymous.md` file. Lookup at runtime SHALL be O(1). The Set SHALL be derived from `import.meta.glob` matching `*.anonymous.md` in the recipe directory.
 
 #### Scenario: Topics with variants are detected at build time
 
 - **WHEN** the CLI bundle is built
-- **AND** a file `improve-rule.anonymous.txt` exists
+- **AND** a file `improve-rule.anonymous.md` exists
 - **THEN** the embedded variants set SHALL contain `improve-rule`
 
 #### Scenario: Topics without variants are absent from the map
 
 - **WHEN** the CLI bundle is built
-- **AND** no `check.anonymous.txt` file exists
+- **AND** no `check.anonymous.md` file exists
 - **THEN** the embedded variants set SHALL NOT contain `check`
-- **AND** `taskless agent check --anonymous` SHALL fall back to `check.txt`
+- **AND** `taskless agent check --anonymous` SHALL fall back to `check.md`
 
 ### Requirement: Embedded JSON schemas are generated via zod-to-json-schema
 

openspec/specs/cli-knowledge-prompts/spec.md

@@ -2,7 +2,7 @@
 
 ## Purpose
 
-The CLI's `agent/*.txt` recipes are the authoritative guidance Taskless gives an
+The CLI's `agent/*.md` recipes are the authoritative guidance Taskless gives an
 agent about authoring and operating rules. Until now the only way to read them
 was to run `taskless agent`, which puts them out of reach of anything that cannot
 spawn the CLI — notably the service-side generator, which needs the same text to
@@ -20,7 +20,7 @@ silently become public API.
 
 ### Requirement: The package exposes knowledge prompts via a dedicated import
 
-The package SHALL expose its knowledge prompts (the `agent/*.txt` recipes) through a subpath export `@taskless/cli/prompts`, built into `dist` and listed in `files`, so consumers can import them without invoking the CLI.
+The package SHALL expose its knowledge prompts (the `agent/*.md` recipes) through a subpath export `@taskless/cli/prompts`, built into `dist` and listed in `files`, so consumers can import them without invoking the CLI.
 
 #### Scenario: Importing a prompt by topic
 
@@ -112,7 +112,7 @@ The `@taskless/cli/prompts` module SHALL contain only embedded prompt data, type
 
 ### Requirement: Anonymous variants are accessible distinctly from canonical
 
-Where a `<topic>.anonymous.txt` variant exists, the export SHALL make it retrievable distinctly via `PromptOptions.anonymous`, falling back to the canonical recipe when no variant exists.
+Where a `<topic>.anonymous.md` variant exists, the export SHALL make it retrievable distinctly via `PromptOptions.anonymous`, falling back to the canonical recipe when no variant exists.
 
 #### Scenario: Anonymous variant retrieval and fallback
 
@@ -141,18 +141,18 @@ What the requirement actually protects is not the version number but the notice.
 
 ### Requirement: Topic membership is explicit and verified against the recipe files
 
-`PromptTopic` SHALL be derived from an explicit, hand-maintained list of exported topics rather than inferred from whatever recipe files are present, so that adding or removing an `agent/*.txt` file cannot silently change the public API. Recipe files deliberately withheld from the export SHALL be recorded in an explicit internal-topics list.
+`PromptTopic` SHALL be derived from an explicit, hand-maintained list of exported topics rather than inferred from whatever recipe files are present, so that adding or removing an `agent/*.md` file cannot silently change the public API. Recipe files deliberately withheld from the export SHALL be recorded in an explicit internal-topics list.
 
-An automated check SHALL assert that the set of canonical `agent/*.txt` topics on disk is exactly the union of the exported topics and the internal-topics list, failing when the two diverge in either direction.
+An automated check SHALL assert that the set of canonical `agent/*.md` topics on disk is exactly the union of the exported topics and the internal-topics list, failing when the two diverge in either direction.
 
 #### Scenario: A new recipe file is added without being classified
 
-- **WHEN** a new canonical `agent/<topic>.txt` is added and appears in neither the exported topics nor the internal-topics list
+- **WHEN** a new canonical `agent/<topic>.md` is added and appears in neither the exported topics nor the internal-topics list
 - **THEN** the completeness check SHALL fail, requiring the author to either export the topic or record it as internal
 
 #### Scenario: An exported topic loses its recipe file
 
-- **WHEN** a topic remains in `PromptTopic` but its canonical `agent/<topic>.txt` no longer exists
+- **WHEN** a topic remains in `PromptTopic` but its canonical `agent/<topic>.md` no longer exists
 - **THEN** the completeness check SHALL fail, rather than the topic rendering empty or undefined at runtime
 
 #### Scenario: A deliberately internal recipe stays unexported

openspec/specs/cli-rules/spec.md

@@ -195,12 +195,12 @@ The API calls for rule generation (`POST /cli/api/request` and `GET /cli/api/req
 
 ### Requirement: Rules improve has an agent recipe
 
-`taskless agent improve-rule` SHALL return the recipe per `cli-agent` requirements. The recipe file is `improve-rule.txt`, with an `improve-rule.anonymous.txt` variant for the local-only flow.
+`taskless agent improve-rule` SHALL return the recipe per `cli-agent` requirements. The recipe file is `improve-rule.md`, with an `improve-rule.anonymous.md` variant for the local-only flow.
 
 #### Scenario: The recipe resolves by its single-token name
 
 - **WHEN** a user runs `taskless agent improve-rule`
-- **THEN** the CLI SHALL print the contents of `improve-rule.txt`
+- **THEN** the CLI SHALL print the contents of `improve-rule.md`
 
 ### Requirement: Rules delete removes rule and test files
 

openspec/specs/cli/spec.md

@@ -51,7 +51,7 @@ The CLI SHALL use Vite in library mode to produce a single bundled ESM output fi
 #### Scenario: Build embeds agent recipe files
 
 - **WHEN** `pnpm build` is run in `packages/cli/`
-- **THEN** every `.txt` file under `packages/cli/src/agent/` SHALL be embedded in the output bundle
+- **THEN** every `.md` file under `packages/cli/src/agent/` SHALL be embedded in the output bundle
 
 #### Scenario: Build fails on version mismatch
 

openspec/specs/skills/spec.md

@@ -10,7 +10,7 @@ Defines the structure, conventions, and distribution model for Taskless skills,
 
 The single skill SHALL be defined at `skills/taskless/SKILL.md` with YAML frontmatter (`name`, `description`, `metadata`) followed by markdown instructions. The `name` field SHALL be exactly `taskless` (no per-task prefix). The `metadata` field SHALL include `author`, `version`, and `commandName: tskl` keys. The `version` SHALL be used for staleness detection when the skill is installed into target repositories.
 
-The skill body SHALL begin by instructing the agent that it does NOT have step-by-step instructions for any Taskless action and that recipes must be fetched via `npx @taskless/cli agent <topic>` before proceeding. The body SHALL NOT contain inline step-by-step recipes for any individual task — those live in `packages/cli/src/agent/<topic>.txt` files served by the `agent` subcommand.
+The skill body SHALL begin by instructing the agent that it does NOT have step-by-step instructions for any Taskless action and that recipes must be fetched via `npx @taskless/cli agent <topic>` before proceeding. The body SHALL NOT contain inline step-by-step recipes for any individual task — those live in `packages/cli/src/agent/<topic>.md` files served by the `agent` subcommand.
 
 #### Scenario: Skill directory contains valid SKILL.md