dorfl 0.1.0 → 0.1.2

package/src/triage-gate.ts

@@ -3,7 +3,7 @@ import {launchWithOptionalWatch} from './agent-launch.js';
 import {extractJsonObjectSpan} from './verdict-json.js';
 
 /**
- * The **TRIAGE auto-disposition GATE** (prd `advance-loop`, task
+ * The **TRIAGE auto-disposition GATE** (spec `advance-loop`, task
  * `advance-rung-triage`, US #17) — the CONSERVATIVE, `observationTriage: 'auto'`-
  * gated exception to the question-gated default. On `classify=triage-observation`
  * AND `observationTriage` resolved to `'auto'`, the engine asks this gate whether

package/src/triage-persist.ts

@@ -12,7 +12,7 @@ import type {TriageAutoKind} from './triage-gate.js';
 import {renderTaskBody, renderSpecBody} from './buildable-body.js';
 
 /**
- * The engine-owned TRIAGE PERSIST (prd `advance-loop`, task `advance-rung-triage`,
+ * The engine-owned TRIAGE PERSIST (spec `advance-loop`, task `advance-rung-triage`,
  * US #16/17/24/30) — the half of the observation-triage rung the ENGINE owns (the
  * triage gate JUDGES, the engine ACTS). It is the SIBLING of `surface-persist.ts`
  * (the surface rung's persist) and `apply-persist.ts` (the apply rung's persist),
@@ -232,7 +232,7 @@ export interface PromoteObservationOptions {
 	 * triage-local {@link createItemThroughCas} writer (one local commit through the
 	 * CAS) — NOT intake's branch+integrate band — so the CAS-loser-backs-off
 	 * guarantee and the same-commit note deletion are uniform across the two routes.
-	 * MIGRATE step (prd `prd-to-spec-vocabulary-cutover-and-migration-command`): the
+	 * MIGRATE step (spec `prd-to-spec-vocabulary-cutover-and-migration-command`): the
 	 * produced VALUE is `'spec'` (the verdict outcome renamed from `'prd'`).
 	 */
 	artifact?: 'task' | 'spec';
@@ -287,22 +287,22 @@ export interface PromoteObservationResult {
 
 /**
  * Promote an ANSWERED observation to a NEW, SELF-CONTAINED artifact (US #1/#3/#8
- * for the task route; US #4/#9 for the PRD route): CAS-create the new item keyed
+ * for the task route; US #4/#9 for the SPEC route): CAS-create the new item keyed
  * on the NEW item's identity (its target path), with the observation note + its
  * answered sidecar `git rm`-ed IN THE SAME atomic commit. Promote is ONE commit
  * (create + delete).
  *
  * The artifact TYPE (`options.artifact`) selects the target + body shape: `'task'`
  * (default) mints `work/tasks/ready/<slug>.md`; `'prd'` mints
- * `work/prds/proposed/<slug>.md` (PRD staging — a human later promotes it to
+ * `work/specs/proposed/<slug>.md` (SPEC staging — a human later promotes it to
  * `ready/`). BOTH routes use the SAME triage-local {@link createItemThroughCas}
  * writer (NOT intake's `switchToWorkBranch`/`performIntegration` branch+integrate
  * band, which is intake's standalone front door): one create/integrate surface for
- * triage, the CAS-loser-backs-off guarantee uniform across task and PRD promotion.
+ * triage, the CAS-loser-backs-off guarantee uniform across task and SPEC promotion.
  *
  * The minted body is built FROM the observation (see {@link buildPromotedBody}):
  * its mechanism + fix prose is carried into the artifact's lead section (`## What
- * to build` for a task, `## Problem Statement` for a PRD), and its
+ * to build` for a task, `## Problem Statement` for a SPEC), and its
  * `## Open questions` scoping is transcribed into the new item's own
  * `## Open questions` block with `needsAnswers` set when questions remain (cleared
  * when none do) — so an agent can build from the artifact ALONE and no decision
@@ -398,10 +398,10 @@ export async function promoteObservation(
  *
  * The artifact TYPE selects the frontmatter + lead heading: a `task` gets
  * `## What to build` + `blockedBy: []` + a `## Prompt` (the buildable-task shape);
- * a `prd` gets `## Problem Statement` (the PRD document shape, with no `blockedBy` —
- * a PRD is not a blockable task — and no `## Prompt`, since a PRD is not
+ * a `prd` gets `## Problem Statement` (the SPEC document shape, with no `blockedBy` —
+ * a SPEC is not a blockable task — and no `## Prompt`, since a SPEC is not
  * dispatched by `do`/`run`). BOTH carry the SAME transcribed mechanism prose +
- * open-question block, so a PRD minted into `proposed/` is just as self-contained
+ * open-question block, so a SPEC minted into `proposed/` is just as self-contained
  * as a task.
  *
  * The `## Prompt` (task only) is the STRUCTURAL dispatchability the validator
@@ -409,9 +409,9 @@ export async function promoteObservation(
  * dispatched build throws "has no '## Prompt' section". The body BELOW the
  * frontmatter (lead section + mechanism prose + optional `## Open questions` +
  * the task-only `## Prompt`) is rendered by the SHARED owner of the
- * buildable-task/PRD schema, {@link renderTaskBody} / {@link renderSpecBody}
+ * buildable-task/SPEC schema, {@link renderTaskBody} / {@link renderSpecBody}
  * (`buildable-body.ts`), so the producer and the consumer cannot drift apart
- * (prd `centralize-buildable-task-renderer-shared-by-intake-and-promotion`,
+ * (spec `centralize-buildable-task-renderer-shared-by-intake-and-promotion`,
  * US #3/#5/#6). This function owns only the FRONTMATTER writer; the section
  * skeleton lives in the one renderer. The empty-mechanism `## Prompt` seed is
  * passed EXPLICITLY (`Build the task '<slug>', described above.`) so promotion's
@@ -434,8 +434,8 @@ export async function promoteObservation(
  * fails with `has no '## Prompt' section` (the `extractPromptSection`/`resolveTask`
  * guard in `prompt.ts`). This is the robust backstop that closes that hole
  * regardless of agent compliance: for a TASK, if the body has no `## Prompt`
- * heading, append a seeded one (blockquoted, matching the renderer's shape). A PRD
- * is left UNTOUCHED — a PRD is a north-star doc, not dispatched by `do`/`run`, and carries no
+ * heading, append a seeded one (blockquoted, matching the renderer's shape). A SPEC
+ * is left UNTOUCHED — a SPEC is a north-star doc, not dispatched by `do`/`run`, and carries no
  * `## Prompt` by design.
  */
 function ensureTaskDispatchable(
@@ -472,7 +472,7 @@ function buildPromotedBody(
 		`title: ${slug}`,
 		`slug: ${slug}`,
 		`needsAnswers: ${hasQuestions ? 'true' : 'false'}`,
-		// A PRD is a north-star doc, not a blockable task — only the task shape carries
+		// A SPEC is a north-star doc, not a blockable task — only the task shape carries
 		// `blockedBy`.
 		...(artifact === 'spec' ? [] : ['blockedBy: []']),
 		'---',
@@ -488,8 +488,8 @@ function buildPromotedBody(
 	// no leading blank. Do NOT move the separator into the renderer.
 	const fenceToBody = frontmatter.join('\n') + '\n\n';
 	// The body BELOW the frontmatter is rendered by the SHARED schema owner so the
-	// section skeleton has one home, not two (prd
-	// `centralize-buildable-task-renderer-shared-by-intake-and-promotion`). A PRD
+	// section skeleton has one home, not two (spec
+	// `centralize-buildable-task-renderer-shared-by-intake-and-promotion`). A SPEC
 	// goes through `renderSpecBody` (no `## Prompt`); a task through
 	// `renderTaskBody` (always a `## Prompt`).
 	if (artifact === 'spec') {

package/src/verify-workflow-template.ts

@@ -1,5 +1,5 @@
 /**
- * The `install-ci` VERIFY-WORKFLOW capability (prd
+ * The `install-ci` VERIFY-WORKFLOW capability (spec
  * `land-time-reverify-and-parallel-merge-ceiling`, task
  * `install-ci-tier1-branch-protection`; Story 11 — the Tier-1 GitHub ceiling).
  * Emits a small `verify.yml` workflow whose ONLY job is `verify` and runs on
@@ -49,7 +49,7 @@ export const VERIFY_WORKFLOW_PATH = 'workflows/verify.yml';
  */
 export function generateVerifyWorkflow(_config: ResolvedCIConfig): string {
 	return `\
-# dorfl — the VERIFY workflow (Tier-1 GitHub ceiling; prd
+# dorfl — the VERIFY workflow (Tier-1 GitHub ceiling; spec
 # land-time-reverify-and-parallel-merge-ceiling, task
 # install-ci-tier1-branch-protection). EMITTED by \`dorfl install-ci\`; the
 # human commits it. DO NOT hand-edit a copy — re-run install-ci to upgrade.

package/src/work-layout.ts

@@ -5,7 +5,7 @@ import {join} from 'node:path';
  * folder-name union/array, the item-scan predicate, and the prefix-task helpers
  * used across `src/`.
  *
- * This is Phase 0 of the `folder-taxonomy-reorg-and-rename` prd — the de-risking
+ * This is Phase 0 of the `folder-taxonomy-reorg-and-rename` spec — the de-risking
  * checkpoint. EVERY raw work-path literal (`join(cwd, 'work', ...)`, `'work/<folder>'`,
  * `'work/<folder>/'.length` prefix-tasks) and EVERY folder-name union/array that
  * used to be scattered across ~70 files now routes through here. The NAMES are
@@ -16,7 +16,7 @@ import {join} from 'node:path';
  * {@link WORK_FOLDER_NAME} (and `git mv` the on-disk folders) and NOTHING ELSE.
  * Call sites reference folders by their SYMBOLIC key (`'tasks-ready'`,
  * `'specs-ready'`, …), never by a raw string, so a folder-VALUE flip never
- * re-touches a single call site (a KEY rename, e.g. the prd→spec cutover below,
+ * re-touches a single call site (a KEY rename, e.g. the spec→spec cutover below,
  * is a mechanical relabel of the key literal at each site — behaviour-preserving).
  *
  * Domain note (crown-jewel invariant): a `work/` tree is a set of governance
@@ -65,17 +65,19 @@ export const WORK_ROOT = 'work' as const;
  *     and `needs-attention` (both are really lock-ref state, NOT durable folders;
  *     routed here only so no reader hand-writes the literal).
  *
- * NOTE on the prd→spec vocabulary cutover
+ * NOTE on the spec→spec vocabulary cutover
  * (`rename-spec-work-layout-and-folders`, migrate-batch 1 of
  * `prd-to-spec-vocabulary-cutover-and-migration-command`): the spec-regime KEYS
  * below now read in the `spec` vocabulary (`specs-proposed`/`specs-ready`/
  * `specs-tasked`/`specs-dropped`) AND their VALUES flip to `work/specs/*` in
- * lockstep with the on-disk `git mv work/prds/* → work/specs/*`. Unlike the earlier
+ * lockstep with the on-disk `git mv work/specs/* → work/specs/*`. Unlike the earlier
  * key-only relabel, this batch moves the folders too, so the KEY and VALUE change
  * together and the self-renaming-folder guard stays green. The KEY rename is a
  * mechanical relabel of the key literal at each call site (behaviour-preserving);
- * the frontmatter `prd:` field (a DATA alias the migration command converts) is the
- * one deliberate survivor; the `--specs-land-in` flag/`specsLandIn` config + the
+ * the legacy frontmatter `prd:` field survives ONLY as un-migrated on-disk DATA the
+ * `dorfl prd-to-spec` command textually converts to `spec:` (HARD CUTOVER: it is no
+ * longer READ by `parseFrontmatter` — `spec:` is the only read key); the
+ * `--specs-land-in` flag/`specsLandIn` config + the
  * `Spec*` symbols were completed by the later batches + the contract task. The
  * folder-as-status invariant is unchanged.
  */
@@ -193,7 +195,7 @@ export function isWorkItemFile(name: string): boolean {
  * order: `in-progress` over `tasks-ready`, with `done` appended only behind the
  * stranded-continue gate. Order is load-bearing — kept exactly as the original
  * union/array. (`tasks-backlog` is NOT in this DEFAULT order: it is appended at
- * the LOWEST priority ONLY behind the explicit `--allow-backlog` flag, prd
+ * the LOWEST priority ONLY behind the explicit `--allow-backlog` flag, spec
  * `do-allow-backlog-drive-staged-tasks-without-promotion` — see
  * {@link TaskResolutionFolder}.)
  */

package/src/workspace.ts

@@ -156,7 +156,7 @@ export interface CreateJobOptions {
 	slug: string;
 	/**
 	 * The item TYPE — `'task'` (build) or `'prd'` (tasking) — namespacing the
-	 * work branch via {@link workBranchRef} so a same-slug task and prd never
+	 * work branch via {@link workBranchRef} so a same-slug task and spec never
 	 * collide. Defaults to `'task'`.
 	 */
 	type?: SlugNamespace;