ultra-builder-pro-cli 0.11.0 → 0.12.1

package/skills/ultra-init/SKILL.md

@@ -1,70 +1,66 @@
 ---
 name: ultra-init
-description: Initialize an Ultra Builder Pro project with authoritative state, baseline specification files, and optional Git setup. Use when a repository has not yet been initialized for the Ultra workflow.
+description: Initialize Ultra Builder Pro or resume greenfield and brownfield baseline adoption. Use when a repository lacks Ultra state or its project baseline is missing, draft, adopting, or blocked.
 ---
 
-# Initialize an Ultra project
+# Initialize or adopt a project
 
-Create the project-local Ultra runtime without inventing product requirements or
-business tasks.
+Create project-local Ultra state, then route the repository according to its actual
+baseline status. Do not treat an existing codebase as a new product.
 
-## Inputs
+## Preflight
 
-Use the current working directory unless the user names another target. Inspect
-existing project manifests to infer:
+Use the current working directory unless the user names another target. Inspect the
+root, project manifests, Git state, and `.ultra/` without mutation.
 
-- project name;
-- project type;
-- primary technologies;
-- whether Git and `.ultra/` already exist.
+If `.ultra/` exists, call `baseline.get` and `system.doctor`:
 
-Ask only about unresolved ambiguity, optional Git initialization, or permission to
-replace an existing `.ultra/` directory. Never infer permission to overwrite it.
+- a healthy `ready` baseline routes to `ultra-change` or `ultra-status`;
+- `draft`, `adopting`, or baseline-blocked state resumes this workflow;
+- state integrity or migration failure routes to `ultra-doctor`;
+- recreation requires explicit authorization and must preserve the returned backup.
 
-## Workflow
+Never overwrite `.ultra/` merely because the repository is old or its documents are
+incomplete.
 
-1. Resolve the absolute target directory and verify that it exists.
-2. Derive the project metadata from repository evidence. Treat user-provided values
-   as authoritative when they conflict with inference.
-3. If `.ultra/` exists, stop and ask whether to keep it, cancel, or recreate it with
-   `overwrite: true`. Explain that recreation first preserves a timestamped backup.
-4. Call `task.init_project` with the smallest complete input:
+## Bootstrap
 
-   ```json
-   {
-     "target_dir": "/absolute/project/path",
-     "project_name": "example",
-     "project_type": "fullstack",
-     "stack": "react,node,postgres",
-     "overwrite": false
-   }
-   ```
+When `.ultra/` is absent, derive project name, type, and stack from repository evidence,
+then call `task.init_project` with `mode: "auto"`. Use an explicit `greenfield` or
+`brownfield` mode only when the user has made that classification authoritative.
 
-5. Verify the returned `.ultra` path, `state_db_path`, status, and copied-file list.
-   Confirm that the returned state database and baseline specification files exist.
-6. If the user requested Git setup, initialize Git only when needed and add narrowly
-   scoped ignore rules. Do not stage or commit without explicit authorization.
+Verify the returned mode, baseline id and status, state database path, initial
+projection, and copied specification files.
 
-If the MCP server cannot start, use the installed
-`ultra-tools task init-project` command only when it is available. The CLI and MCP
-must use the same initializer. Do not simulate initialization by creating projection
-files manually.
+## Route by mode
 
-## Failure handling
+### Greenfield
+
+The new baseline begins as `draft`. Route unresolved product or architecture intent to
+`ultra-research`. That workflow records evidence and converges the baseline before
+planning. Do not create implementation tasks during initialization.
+
+### Brownfield
 
-- `ULTRA_DIR_EXISTS`: return to the overwrite decision; do not retry automatically.
-- `TEMPLATE_MISSING`: stop and report an installation/package integrity failure.
-- `TARGET_NOT_DIR` or `VALIDATION_ERROR`: correct the input and retry once.
-- `IO_ERROR`: report the affected path and preserve any backup or partial evidence.
+Read `references/brownfield-adoption.md` completely. Adopt current behavior from the
+checkout, tests, maintained documentation, and runtime evidence. Use `baseline.record`
+for the bounded snapshot and `baseline.converge` only after the owner approves the
+captured baseline and any accepted known-red verification.
+
+## Failure handling
 
-## Authority and output
+- `ULTRA_DIR_EXISTS`: inspect and resume; do not retry with overwrite automatically.
+- `BASELINE_EXISTS`: keep the ready baseline unless explicit re-adoption is required.
+- `BASELINE_IN_PROGRESS`: resume the named baseline rather than creating another.
+- `TEMPLATE_MISSING`: report a package-integrity failure and route to installer doctor.
+- `TARGET_NOT_DIR`, `VALIDATION_ERROR`, or `IO_ERROR`: correct only the evidenced input;
+  preserve any backup and partial diagnostic.
 
-`.ultra/state.db` is the durable Ultra authority. Generated JSON and Markdown are
-projections or workflow artifacts and must not be edited to create state.
+## Output
 
-Report the initialized path, state database path, backup path when present, Git
-action, and one next action. Route incomplete product intent to `ultra-research`;
-route an already validated baseline to `ultra-plan`.
+Report target path, detected mode, baseline id/status/revision, state health, known-red
+verification, blocking unknowns, and one next action. `.ultra/state.db` is authoritative;
+JSON and Markdown projections do not create state.
 
-Do not create business tasks, browse the web, or rewrite an existing README as part
-of initialization.
+Do not browse by default, invent missing behavior, rewrite application code, create
+business tasks, stage files, or commit as part of initialization.

package/skills/ultra-init/references/brownfield-adoption.md

@@ -0,0 +1,65 @@
+# Brownfield adoption
+
+Use this procedure only after `task.init_project` selects `brownfield`, or when an
+existing baseline remains `adopting` or `blocked`.
+
+## Establish the snapshot boundary
+
+Bind the repository root, current Git HEAD when available, included paths, excluded
+generated or vendored paths, project manifests, and the user-visible or public seams.
+Use the revision returned by `baseline.record`; non-Git projects receive a deterministic
+workspace revision from the recorded evidence.
+
+## Read current behavior
+
+Inspect only the evidence needed to explain the maintained system:
+
+- entry points and consumers;
+- persisted state and its writers;
+- external interfaces, events, permissions, and failure paths;
+- tests and their live seams;
+- deployment, migration, and recovery paths when present;
+- maintained documents and their relationship to source.
+
+Classify every statement as observed, verified, decided, or unknown. Source and runtime
+evidence outrank stale prose. External memory and code-graph providers may supply
+references, but their content remains outside Ultra state.
+
+## Capture the baseline
+
+Update `.ultra/specs/product.md` with confirmed behavior, actors, entry points, failures,
+and acceptance. Update `.ultra/specs/architecture.md` with actual boundaries, authority,
+runtime paths, dependencies, permissions, and recovery. Use `discovery.md` only for
+evidence or decisions that affect scope.
+
+Do not redesign the project, normalize it to a preferred architecture, manufacture
+personas or alternatives, or convert every source file into documentation.
+
+Run the repository's existing verification commands. Record each result as `pass`,
+`known_red`, or `not_run`. A known-red item needs evidence and a rationale; a missing
+command is not a passing result. Mark an unknown blocking when it can change accepted
+behavior, authority, security, data integrity, or the next implementation plan.
+
+Call `baseline.record` with full replacement arrays for:
+
+- scope and repository revision;
+- product and architecture specification paths;
+- bounded source, documentation, runtime, test, deployment, or external references;
+- verification results;
+- blocking and non-blocking unknowns;
+- external provider metadata references, when supplied.
+
+The server computes specification digests. Do not send prompt, transcript, memory, or
+code-graph payloads.
+
+## Converge
+
+Present the observed behavior, known-red verification, blocking unknowns, and material
+decisions to the project owner. After explicit approval, call `baseline.converge` with
+the recorded revision, approver, approval note, and `accept_known_red` only when the
+owner accepted those failures.
+
+Resolve returned blockers through evidence or an owner decision, record the replacement
+snapshot, and retry. Adoption is complete only when `baseline.get` and `system.doctor`
+report the baseline ready and current. Route the first new outcome to `ultra-change`, or
+route planning of already accepted work to `ultra-plan`.

package/skills/ultra-plan/SKILL.md

@@ -13,6 +13,11 @@ Markdown are generated projections.
 
 Start with a state-backed MCP read. If state or schema health blocks access, stop and
 route to `ultra-doctor`. Never read or write `.ultra/tasks/tasks.json` as a fallback.
+Call `baseline.get`. Initial product planning is blocked until the baseline is
+`ready` and current; route its missing, adopting, blocked, or stale state to
+`ultra-init`. Planning an already active bounded change may continue with the
+baseline condition recorded as a warning. Convergence still requires approved
+adoption, and archive atomically reconciles and verifies revision/spec drift.
 
 Choose one input:
 
@@ -30,8 +35,10 @@ current evidence. A material unresolved assumption blocks persistence.
 2. Prefer a walking skeleton or `tracer_bullet` before horizontal layers.
 3. Give each task one outcome, bounded ownership, explicit dependencies, required
    references, and one deterministic verification command.
-4. Use the context budget returned by the current Ultra contract. Widen it only when
-   an approved slice cannot be split without losing correctness.
+4. Use the context budget as an attention signal. Prefer bounded excerpts, direct
+   reads, or a smaller slice, but keep necessary files when correctness requires them.
+   Budget overflow is a warning, never a reason to inflate a threshold or manufacture
+   a smaller but incomplete contract.
 5. Add integration checkpoints at actual boundaries, not after arbitrary task counts.
 6. Put validation, errors, recovery, documentation, and migrations in the task that
    owns the behavior.

package/skills/ultra-research/SKILL.md

@@ -10,8 +10,8 @@ decision. Do not force a fixed discovery ceremony onto a well-defined change.
 
 ## Preflight
 
-1. Require an initialized `.ultra/specs/` directory. Route to `ultra-init` when it is
-   absent.
+1. Require an initialized `.ultra/specs/` directory and call `baseline.get`. Route to
+   `ultra-init` when state or the baseline is absent. Preserve its mode and id.
 2. Read the current specification files and repository evidence before asking the
    user to repeat known facts.
 3. Define the intended deliverable, unresolved decisions, and evidence standard.
@@ -50,7 +50,12 @@ default.
    open questions. Do not duplicate the same narrative across several files.
 5. Validate cross-document consistency and trace each required behavior from problem
    or constraint to acceptance and architecture.
-6. Use `references/synthesis.md` for the completion check and report one next action.
+6. Use `references/synthesis.md` for the completion check.
+7. Call `baseline.record` with the complete current specification list, bounded evidence
+   references, actual verification results, provider metadata, and explicit unknowns.
+   Use the returned repository revision for convergence.
+8. Present the baseline and any known-red verification to the owner. After explicit
+   approval, call `baseline.converge`. Resolve deterministic blockers before routing.
 
 ## Completion gate
 
@@ -59,5 +64,5 @@ material decision is recorded, required acceptance is testable, architecture res
 known constraints, and unresolved items are either blocking or explicitly outside the
 accepted scope.
 
-Route a validated baseline to `ultra-plan`. Do not create business tasks, write Ultra
-state, or maintain a second condensed specification that can drift from the baseline.
+Route a converged baseline to `ultra-plan`. Do not create business tasks, write raw
+SQLite, or maintain a second condensed specification that can drift from the baseline.

package/skills/ultra-status/SKILL.md

@@ -12,12 +12,14 @@ authoritative; reports and Markdown are evidence or projections.
 
 1. Call `system.doctor` in read-only mode. If authority is unhealthy, route only to
    `ultra-doctor` and include the blocking diagnostic.
-2. Call `change.breadcrumb` for the active change, task, role, gate, readiness,
-   blockers, staleness, and next action.
-3. Call `task.list` and `session.list` for progress and active execution details.
-4. Read test and delivery reports only when present, and mark a report stale when its
+2. Call `baseline.get` for mode, lifecycle status, repository revision, specification
+   digest health, known warnings, and adoption blockers.
+3. Call `change.breadcrumb` for the active change, task, role, gate, readiness,
+   blockers, advisory warnings, staleness, and next action.
+4. Call `task.list` and `session.list` for progress and active execution details.
+5. Read test and delivery reports only when present, and mark a report stale when its
    HEAD differs from the current checkout.
-5. Read Git branch, HEAD, and worktree status without mutation.
+6. Read Git branch, HEAD, and worktree status without mutation.
 
 If MCP task or change state is unavailable, label that panel unavailable. Never fall
 back to generated task JSON, context frontmatter, or raw SQLite.
@@ -28,7 +30,10 @@ Follow the breadcrumb's primary route and return one action, not a menu:
 
 - unhealthy authority: `ultra-doctor`;
 - missing Ultra project: `ultra-init`;
-- missing baseline evidence: `ultra-research` or `ultra-plan`, matching the gap;
+- missing baseline evidence with no active change: `ultra-init`, then
+  `ultra-research` or `ultra-plan` according to the gap;
+- baseline or context-budget warning during an active change: keep the current route
+  and surface the warning; do not turn it into a refusal;
 - blocked or stale context: the workflow named by the breadcrumb;
 - ready implementation task: `ultra-dev <task-id>`;
 - completed tasks with missing or stale test evidence: `ultra-test`;
@@ -45,7 +50,9 @@ Use a compact shape:
 ```text
 Ultra: <healthy|degraded> · <branch>@<head> · worktree <clean|dirty>
 Position: change=<id|none> task=<id|none> role=<role> gate=<gate>
+Baseline: <greenfield|brownfield|migrated>/<status> revision=<revision|none>
 Readiness: <ready|blocked|stale> — <blockers or none>
+Warnings: <advisory conditions or none>
 Progress: <completed>/<total>; sessions=<active count>
 Evidence: tests=<fresh|stale|missing>; delivery=<fresh|stale|missing>
 Next: <one exact action>

package/spec/cli-protocol.md

@@ -100,6 +100,10 @@ as a fallback unless `ultra-tools <family> --help` lists it.
 | `session.admission_check` | `session admission`         | 4.5   | any     |
 | `session.heartbeat`       | `session heartbeat`         | 4.5   | mcp     |
 | `session.subscribe_events`| `session subscribe`         | 4.5   | any     |
+| `baseline.start`          | `baseline start`            | 11    | mcp     |
+| `baseline.record`         | `baseline record`           | 11    | mcp     |
+| `baseline.get`            | `baseline get`              | 11    | any     |
+| `baseline.converge`       | `baseline converge`         | 11    | mcp     |
 | `change.create`           | `change create`             | 9     | mcp     |
 | `change.update`           | `change update`             | 9     | mcp     |
 | `change.get`              | `change get`                | 9     | any     |

package/spec/mcp-tools.yaml

@@ -23,6 +23,7 @@ families:
   - { name: task,    description: 'authoritative task lifecycle on state.db', phase: '2' }
   - { name: session, description: 'execution-unit lifecycle with single-active-lease admission (D33)', phase: '4.5' }
   - { name: plan,    description: 'execution-plan artifact export and query (D34)', phase: '8a' }
+  - { name: baseline, description: 'project adoption, baseline evidence, convergence, and drift authority', phase: '11' }
   - { name: change,  description: 'continuous post-delivery change lifecycle and convergence', phase: '9' }
   - { name: system,  description: 'read-only diagnostics and explicit backup-first repair', phase: '9' }
 
@@ -217,9 +218,9 @@ tools:
   - name: task.init_project
     family: task
     description: |
-      Bootstrap a fresh `.ultra/` skeleton in target_dir from the bundled
-      templates/.ultra/ source. Copies spec templates, tasks.json, context
-      template, and report stubs. Phase 3.1 entry point for /ultra-init.
+      Bootstrap `.ultra/` and start an authoritative greenfield or brownfield
+      baseline. Auto mode detects meaningful existing project content before
+      copying specification templates and creating state.db.
     phase: '3'
     writer_role: mcp
     input_schema:
@@ -240,6 +241,11 @@ tools:
         stack:
           type: string
           description: optional tech stack descriptor (comma-separated for fullstack)
+        mode:
+          type: string
+          enum: [auto, greenfield, brownfield]
+          default: auto
+          description: auto detects whether meaningful project content already exists
         overwrite:
           type: boolean
           default: false
@@ -249,7 +255,7 @@ tools:
           description: override path to the template root (defaults to bundled templates/.ultra/)
     output_schema:
       type: object
-      required: [created_path, state_db_path, status, copied_files]
+      required: [created_path, state_db_path, status, mode, baseline, copied_files]
       additionalProperties: false
       properties:
         created_path:
@@ -261,6 +267,13 @@ tools:
         status:
           type: string
           enum: [created, overwritten]
+        mode:
+          type: string
+          enum: [greenfield, brownfield]
+        baseline:
+          type: object
+          required: [id, mode, status]
+          additionalProperties: true
         copied_files:
           type: array
           items: { type: string }
@@ -629,6 +642,210 @@ tools:
     emits_events: []
     trace_to: '§7.3, D31'
 
+  # ───────────────────────── baseline family ─────────────────────────────
+  - name: baseline.start
+    family: baseline
+    description: Start a greenfield baseline or brownfield adoption without overwriting a ready baseline implicitly.
+    phase: '11'
+    writer_role: mcp
+    input_schema:
+      type: object
+      required: [project_name, mode]
+      additionalProperties: false
+      properties:
+        id: { type: string, pattern: '^[a-zA-Z0-9_\-]+$', default: project-baseline }
+        project_name: { type: string, minLength: 1 }
+        project_type: { type: string, enum: [web, api, cli, fullstack, other] }
+        stack: { type: string }
+        mode: { type: string, enum: [greenfield, brownfield] }
+        scope: { type: array, minItems: 1, items: { type: string, minLength: 1 }, default: ['.'] }
+        repository_revision: { type: string, minLength: 1 }
+        replace_ready: { type: boolean, default: false }
+        provider_refs:
+          type: object
+          additionalProperties: false
+          properties:
+            memory:
+              type: object
+              required: [provider]
+              additionalProperties: false
+              properties:
+                provider: { type: string }
+                project: { type: string }
+                reference: { type: string }
+                revision: { type: string }
+                indexed_head: { type: string }
+                status: { type: string, enum: [available, unavailable, fresh, stale, unknown] }
+            code_graph:
+              type: object
+              required: [provider]
+              additionalProperties: false
+              properties:
+                provider: { type: string }
+                project: { type: string }
+                reference: { type: string }
+                revision: { type: string }
+                indexed_head: { type: string }
+                status: { type: string, enum: [available, unavailable, fresh, stale, unknown] }
+    output_schema:
+      type: object
+      required: [baseline]
+      additionalProperties: false
+      properties:
+        baseline: { type: object }
+    errors:
+      - { code: BASELINE_EXISTS, description: 'a ready baseline requires explicit replacement' }
+      - { code: BASELINE_IN_PROGRESS, description: 'another adoption is already active' }
+      - { code: PROVIDER_CONTENT_FORBIDDEN, description: 'provider payload content must remain external' }
+    cli_subcommand: baseline start
+    emits_events: [baseline_started]
+
+  - name: baseline.record
+    family: baseline
+    description: Replace the current adoption snapshot with bounded specification digests, evidence references, verification, unknowns, and provider metadata.
+    phase: '11'
+    writer_role: mcp
+    input_schema:
+      type: object
+      required: [id]
+      additionalProperties: false
+      properties:
+        id: { type: string, pattern: '^[a-zA-Z0-9_\-]+$' }
+        repository_revision: { type: string, minLength: 1 }
+        scope: { type: array, minItems: 1, items: { type: string, minLength: 1 } }
+        spec_refs:
+          type: array
+          items:
+            type: object
+            required: [kind, path]
+            additionalProperties: false
+            properties:
+              kind: { type: string, enum: [discovery, product, architecture, quality, delivery, other] }
+              path: { type: string, minLength: 1 }
+        evidence:
+          type: array
+          items:
+            type: object
+            required: [kind, ref, summary]
+            additionalProperties: false
+            properties:
+              kind: { type: string, enum: [source, docs, runtime, test, deploy, external] }
+              ref: { type: string, minLength: 1 }
+              summary: { type: string, minLength: 1 }
+        verification:
+          type: array
+          items:
+            type: object
+            required: [name, command, status, evidence]
+            additionalProperties: false
+            properties:
+              name: { type: string, minLength: 1 }
+              command: { type: string, minLength: 1 }
+              status: { type: string, enum: [pass, known_red, not_run] }
+              evidence: { type: string, minLength: 1 }
+              rationale: { type: string, minLength: 1 }
+        unknowns:
+          type: array
+          items:
+            type: object
+            required: [summary, blocking]
+            additionalProperties: false
+            properties:
+              summary: { type: string, minLength: 1 }
+              blocking: { type: boolean }
+              owner: { type: string, minLength: 1 }
+        provider_refs:
+          type: object
+          additionalProperties: false
+          properties:
+            memory:
+              type: object
+              required: [provider]
+              additionalProperties: false
+              properties:
+                provider: { type: string }
+                project: { type: string }
+                reference: { type: string }
+                revision: { type: string }
+                indexed_head: { type: string }
+                status: { type: string, enum: [available, unavailable, fresh, stale, unknown] }
+            code_graph:
+              type: object
+              required: [provider]
+              additionalProperties: false
+              properties:
+                provider: { type: string }
+                project: { type: string }
+                reference: { type: string }
+                revision: { type: string }
+                indexed_head: { type: string }
+                status: { type: string, enum: [available, unavailable, fresh, stale, unknown] }
+    output_schema:
+      type: object
+      required: [baseline]
+      additionalProperties: false
+      properties:
+        baseline: { type: object }
+    errors:
+      - { code: BASELINE_NOT_FOUND, description: 'baseline id does not exist' }
+      - { code: BASELINE_NOT_MUTABLE, description: 'ready and superseded baselines are immutable' }
+      - { code: BASELINE_SPEC_MISSING, description: 'a declared specification file does not exist' }
+      - { code: PROVIDER_CONTENT_FORBIDDEN, description: 'provider payload content must remain external' }
+    cli_subcommand: baseline record
+    emits_events: [baseline_recorded]
+
+  - name: baseline.get
+    family: baseline
+    description: Read the current or named authoritative baseline with live digest and repository-revision health.
+    phase: '11'
+    readonly: true
+    input_schema:
+      type: object
+      additionalProperties: false
+      properties:
+        id: { type: string, pattern: '^[a-zA-Z0-9_\-]+$' }
+    output_schema:
+      type: object
+      required: [baseline, health]
+      additionalProperties: false
+      properties:
+        baseline: { type: object }
+        health: { type: object }
+    errors:
+      - { code: BASELINE_NOT_FOUND, description: 'no matching baseline exists' }
+    cli_subcommand: baseline get
+    emits_events: []
+
+  - name: baseline.converge
+    family: baseline
+    description: Approve a baseline only when its revision, specification digests, evidence, verification, and blocking unknowns satisfy deterministic gates.
+    phase: '11'
+    writer_role: mcp
+    input_schema:
+      type: object
+      required: [id, expected_revision, approved_by, approval_note]
+      additionalProperties: false
+      properties:
+        id: { type: string, pattern: '^[a-zA-Z0-9_\-]+$' }
+        expected_revision: { type: string, minLength: 1 }
+        approved_by: { type: string, minLength: 1 }
+        approval_note: { type: string, minLength: 3 }
+        accept_known_red: { type: boolean, default: false }
+    output_schema:
+      type: object
+      required: [ready, status, blockers, baseline]
+      additionalProperties: false
+      properties:
+        ready: { type: boolean }
+        status: { type: string, enum: [blocked, ready] }
+        blockers: { type: array, items: { type: string } }
+        baseline: { type: object }
+    errors:
+      - { code: BASELINE_NOT_FOUND, description: 'baseline id does not exist' }
+      - { code: BASELINE_NOT_CONVERGEABLE, description: 'baseline lifecycle does not allow convergence' }
+    cli_subcommand: baseline converge
+    emits_events: [baseline_blocked, baseline_converged]
+
   # ────────────────────────── change family ──────────────────────────────
   - name: change.create
     family: change
@@ -1048,6 +1265,8 @@ tools:
     errors:
       - { code: CHANGE_NOT_READY, description: 'change has not passed convergence' }
       - { code: BASELINE_RECONCILIATION_REQUIRED, description: 'baseline update or explicit no-change reason required' }
+      - { code: BASELINE_FILE_MISSING, description: 'a declared baseline update does not exist' }
+      - { code: BASELINE_RECONCILIATION_INCOMPLETE, description: 'repository revision or tracked specification digests remain stale after reconciliation' }
       - { code: ARCHIVE_EXISTS, description: 'archive target already exists' }
     cli_subcommand: change archive
     emits_events: [change_archived]

package/spec/schemas/mcp-tools.schema.json

@@ -60,7 +60,7 @@
         },
         "family": {
           "type": "string",
-          "enum": ["task", "memory", "review", "impact", "skill", "session", "ask", "plan", "change", "system"]
+          "enum": ["task", "memory", "review", "impact", "skill", "session", "ask", "plan", "baseline", "change", "system"]
         },
         "description": { "type": "string", "minLength": 10 },
         "phase": {

package/spec/schemas/state-db.sql

@@ -1,9 +1,9 @@
 -- Ultra Builder Pro — authoritative state schema
 -- Phase 2 builds .ultra/state.db from this file. Source of truth for all
--- task / session / event / telemetry data. tasks.json and context md status
+-- baseline / change / task / session / event / telemetry data. tasks.json and context md status
 -- header are projections (PLAN §7.1, D18, D32).
 --
--- Trace: docs/PLAN.zh-CN.md §7.1; decisions D18/D30/D31/D32/D37.
+-- Trace: docs/PLAN.zh-CN.md §7.1; decisions D18/D30/D31/D32/D37/D52/D54.
 --
 -- PRAGMAs are applied by mcp-server/lib/state-db.ts on connection open;
 -- they cannot be persisted in CREATE statements but are documented here.
@@ -12,6 +12,35 @@
 --   PRAGMA busy_timeout=5000;       -- block up to 5s on lock (R25)
 --   PRAGMA foreign_keys=ON;         -- enforce FK constraints
 
+-- ──────────────────────────── project baseline ─────────────────────────────
+-- The baseline is the approved, repository-scoped snapshot that every change
+-- is measured against. It stores digests and evidence references, never source,
+-- prompt, transcript, memory, or code-graph payloads.
+CREATE TABLE IF NOT EXISTS baselines (
+  id                  TEXT PRIMARY KEY,
+  project_name        TEXT NOT NULL,
+  project_type        TEXT,
+  stack               TEXT,
+  mode                TEXT NOT NULL CHECK (mode IN ('greenfield', 'brownfield', 'migrated')),
+  status              TEXT NOT NULL DEFAULT 'draft'
+                        CHECK (status IN ('draft', 'adopting', 'blocked', 'ready', 'superseded')),
+  repository_root     TEXT NOT NULL DEFAULT '.',
+  scope_json          TEXT NOT NULL DEFAULT '["."]',
+  repository_revision TEXT,
+  spec_refs_json      TEXT NOT NULL DEFAULT '[]',
+  evidence_json       TEXT NOT NULL DEFAULT '[]',
+  verification_json   TEXT NOT NULL DEFAULT '[]',
+  unknowns_json       TEXT NOT NULL DEFAULT '[]',
+  provider_refs_json  TEXT NOT NULL DEFAULT '{}',
+  approved_by         TEXT,
+  approval_note       TEXT,
+  started_at          TEXT NOT NULL DEFAULT (strftime('%Y-%m-%dT%H:%M:%fZ', 'now')),
+  updated_at          TEXT NOT NULL DEFAULT (strftime('%Y-%m-%dT%H:%M:%fZ', 'now')),
+  converged_at        TEXT
+);
+
+CREATE INDEX IF NOT EXISTS baselines_status ON baselines(status, updated_at);
+
 -- ──────────────────────────── changes ─────────────────────────────────────
 -- A project baseline is continuous; each feature, fix, incident, or redesign
 -- is an independently converged change unit. Only changes become terminal.
@@ -305,3 +334,5 @@ INSERT OR IGNORE INTO schema_version (version, description)
 VALUES ('9.1', 'Kimi runtime support in durable events and sessions');
 INSERT OR IGNORE INTO schema_version (version, description)
 VALUES ('10.0', 'Role-scoped context snapshots, deterministic breadcrumbs, and approval-gated specification learning');
+INSERT OR IGNORE INTO schema_version (version, description)
+VALUES ('11.0', 'Greenfield and brownfield baseline adoption, convergence, and drift authority');