sauron-cli 1.3.0 → 1.4.1

package/OpenSpec-main/openspec/changes/archive/2026-02-17-project-local-schemas/proposal.md

@@ -1,167 +0,0 @@
-# Project-Local Schemas
-
-## Summary
-
-Add project-local schema resolution (`./openspec/schemas/`) as the highest priority in the schema lookup chain. This enables teams to version control custom workflow schemas with their repository.
-
-## Motivation
-
-Currently, schema resolution is 2-level:
-1. User override: `~/.local/share/openspec/schemas/<name>/`
-2. Package built-in: `<npm-package>/schemas/<name>/`
-
-This creates friction for teams:
-- Custom schemas must be set up per-machine via XDG paths
-- Cannot share schemas via version control
-- No single source of truth for team workflows
-
-## Design Decisions
-
-### 3-Level Resolution Order
-
-```
-1. ./openspec/schemas/<name>/                    # Project-local (NEW)
-2. ~/.local/share/openspec/schemas/<name>/       # User global (XDG)
-3. <npm-package>/schemas/<name>/                 # Package built-in
-```
-
-Project-local takes highest priority, enabling:
-- Version-controlled custom workflows
-- Automatic team sharing via git
-- No per-machine setup required
-
-### Fork Model (Not Inheritance)
-
-Custom schemas are complete definitions, not extensions. There is no `extends` keyword.
-
-**Rationale:** Simplicity. Inheritance adds complexity (conflict resolution, partial overrides, debugging "where did this come from?"). Users who need custom workflows can define them fully. This keeps the mental model simple:
-- Use a preset → Configure path (see project-config change)
-- Need different structure → Fork path (define your own)
-
-### Directory Structure
-
-```
-openspec/
-├── schemas/                      # Project-local schemas
-│   └── my-workflow/
-│       ├── schema.yaml           # Full schema definition
-│       └── templates/
-│           ├── artifact1.md
-│           ├── artifact2.md
-│           └── ...
-└── changes/
-```
-
-### Schema Naming
-
-Project-local schemas are referenced by their directory name:
-- `openspec/schemas/my-workflow/` → referenced as `my-workflow`
-- Works with `--schema my-workflow` flag
-- Works with `schema: my-workflow` in config.yaml (see project-config change)
-
-## Scope
-
-### In Scope
-
-- Add `getProjectSchemasDir()` function to resolver
-- Update `getSchemaDir()` to check project-local first
-- Update `listSchemas()` to include project schemas
-- Update `listSchemasWithInfo()` to include `source: 'project'`
-- Update `schemasCommand` output to show project schemas
-
-### Out of Scope
-
-- Schema management CLI (`openspec schema copy/which/diff/reset`) - future enhancement
-- Schema inheritance/extends - explicitly not supported
-- Template-level overrides (partial fork) - explicitly not supported
-
-## User Experience
-
-### Creating a Custom Schema
-
-```bash
-# Create schema directory
-mkdir -p openspec/schemas/my-workflow/templates
-
-# Define schema
-cat > openspec/schemas/my-workflow/schema.yaml << 'EOF'
-name: my-workflow
-version: 1
-description: Our team's planning workflow
-
-artifacts:
-  - id: research
-    generates: research.md
-    template: research.md
-    description: Background research
-    requires: []
-
-  - id: proposal
-    generates: proposal.md
-    template: proposal.md
-    description: Change proposal
-    requires: [research]
-
-  - id: tasks
-    generates: tasks.md
-    template: tasks.md
-    description: Implementation tasks
-    requires: [proposal]
-EOF
-
-# Create templates
-echo "# Research\n\n..." > openspec/schemas/my-workflow/templates/research.md
-# ... etc
-```
-
-### Using the Custom Schema
-
-```bash
-# Via CLI flag
-openspec new change add-feature --schema my-workflow
-openspec status --change add-feature --schema my-workflow
-
-# Via config.yaml (requires project-config change)
-# schema: my-workflow
-```
-
-### Team Sharing
-
-```bash
-# Commit to repo
-git add openspec/schemas/
-git commit -m "Add custom workflow schema"
-git push
-
-# Team members get it automatically
-git pull
-openspec status --change add-feature --schema my-workflow  # Just works
-```
-
-## Implementation Notes
-
-### Files to Modify
-
-| File | Changes |
-|------|---------|
-| `src/core/artifact-graph/resolver.ts` | Add `getProjectSchemasDir()`, update resolution order |
-| `src/commands/artifact-workflow.ts` | Update `schemasCommand` to show source |
-
-### Project Root Detection
-
-Use existing `findProjectRoot()` pattern or current working directory. The project-local schemas directory is always `./openspec/schemas/` relative to project root.
-
-### Source Indication
-
-`listSchemasWithInfo()` returns `source: 'project' | 'user' | 'package'`. Update type definition and implementation.
-
-## Testing Considerations
-
-- Create temp project with local schema, verify resolution priority
-- Verify local schema overrides user override with same name
-- Verify `listSchemas()` includes project schemas
-- Verify `schemasCommand` shows correct source labels
-
-## Related Changes
-
-- **project-config**: Adds `config.yaml` with `schema` field that can reference project-local schemas

package/OpenSpec-main/openspec/changes/archive/2026-02-17-project-local-schemas/specs/schema-resolution/spec.md

@@ -1,88 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Project-local schema resolution
-
-The system SHALL resolve schemas from the project-local directory (`./openspec/schemas/<name>/`) with highest priority when a `projectRoot` is provided.
-
-#### Scenario: Project-local schema takes precedence over user override
-- **WHEN** a schema named "my-workflow" exists at `./openspec/schemas/my-workflow/schema.yaml`
-- **AND** a schema named "my-workflow" exists at `~/.local/share/openspec/schemas/my-workflow/schema.yaml`
-- **AND** `getSchemaDir("my-workflow", projectRoot)` is called
-- **THEN** the system SHALL return the project-local path
-
-#### Scenario: Project-local schema takes precedence over package built-in
-- **WHEN** a schema named "spec-driven" exists at `./openspec/schemas/spec-driven/schema.yaml`
-- **AND** "spec-driven" is a package built-in schema
-- **AND** `getSchemaDir("spec-driven", projectRoot)` is called
-- **THEN** the system SHALL return the project-local path
-
-#### Scenario: Falls back to user override when no project-local schema
-- **WHEN** no schema named "my-workflow" exists at `./openspec/schemas/my-workflow/`
-- **AND** a schema named "my-workflow" exists at `~/.local/share/openspec/schemas/my-workflow/schema.yaml`
-- **AND** `getSchemaDir("my-workflow", projectRoot)` is called
-- **THEN** the system SHALL return the user override path
-
-#### Scenario: Falls back to package built-in when no project-local or user schema
-- **WHEN** no schema named "spec-driven" exists at `./openspec/schemas/spec-driven/`
-- **AND** no schema named "spec-driven" exists at `~/.local/share/openspec/schemas/spec-driven/`
-- **AND** "spec-driven" is a package built-in schema
-- **AND** `getSchemaDir("spec-driven", projectRoot)` is called
-- **THEN** the system SHALL return the package built-in path
-
-#### Scenario: Backward compatibility when projectRoot not provided
-- **WHEN** `getSchemaDir("my-workflow")` is called without a `projectRoot` parameter
-- **THEN** the system SHALL only check user override and package built-in locations
-- **AND** the system SHALL NOT check project-local location
-
-### Requirement: Project schemas directory helper
-
-The system SHALL provide a `getProjectSchemasDir(projectRoot)` function that returns the project-local schemas directory path.
-
-#### Scenario: Returns correct path
-- **WHEN** `getProjectSchemasDir("/path/to/project")` is called
-- **THEN** the system SHALL return `/path/to/project/openspec/schemas`
-
-### Requirement: List schemas includes project-local
-
-The system SHALL include project-local schemas when listing available schemas if `projectRoot` is provided.
-
-#### Scenario: Project-local schemas appear in list
-- **WHEN** a schema named "team-flow" exists at `./openspec/schemas/team-flow/schema.yaml`
-- **AND** `listSchemas(projectRoot)` is called
-- **THEN** the returned list SHALL include "team-flow"
-
-#### Scenario: Project-local schema shadows same-named user schema in list
-- **WHEN** a schema named "custom" exists at both project-local and user override locations
-- **AND** `listSchemas(projectRoot)` is called
-- **THEN** the returned list SHALL include "custom" exactly once
-
-#### Scenario: Backward compatibility for listSchemas
-- **WHEN** `listSchemas()` is called without a `projectRoot` parameter
-- **THEN** the system SHALL only include user override and package built-in schemas
-
-### Requirement: Schema info includes project source
-
-The system SHALL indicate `source: 'project'` for project-local schemas in `listSchemasWithInfo()` results.
-
-#### Scenario: Project-local schema shows project source
-- **WHEN** a schema named "team-flow" exists at `./openspec/schemas/team-flow/schema.yaml`
-- **AND** `listSchemasWithInfo(projectRoot)` is called
-- **THEN** the schema info for "team-flow" SHALL have `source: 'project'`
-
-#### Scenario: User override schema shows user source
-- **WHEN** a schema named "my-custom" exists only at `~/.local/share/openspec/schemas/my-custom/`
-- **AND** `listSchemasWithInfo(projectRoot)` is called
-- **THEN** the schema info for "my-custom" SHALL have `source: 'user'`
-
-#### Scenario: Package built-in schema shows package source
-- **WHEN** "spec-driven" exists only as a package built-in
-- **AND** `listSchemasWithInfo(projectRoot)` is called
-- **THEN** the schema info for "spec-driven" SHALL have `source: 'package'`
-
-### Requirement: Schemas command shows source
-
-The `openspec schemas` command SHALL display the source of each schema.
-
-#### Scenario: Display format includes source
-- **WHEN** user runs `openspec schemas`
-- **THEN** the output SHALL show each schema with its source label (project, user, or package)

package/OpenSpec-main/openspec/changes/archive/2026-02-17-project-local-schemas/tasks.md

@@ -1,28 +0,0 @@
-## 1. Update Resolver Types and Helpers
-
-- [x] 1.1 Update `SchemaInfo.source` type to include `'project'` in `src/core/artifact-graph/resolver.ts`
-- [x] 1.2 Add `getProjectSchemasDir(projectRoot: string): string` function
-
-## 2. Update Schema Resolution Functions
-
-- [x] 2.1 Update `getSchemaDir(name, projectRoot?)` to check project-local first when projectRoot provided
-- [x] 2.2 Update `resolveSchema(name, projectRoot?)` to pass projectRoot to getSchemaDir
-- [x] 2.3 Update `listSchemas(projectRoot?)` to include project-local schemas
-- [x] 2.4 Update `listSchemasWithInfo(projectRoot?)` to include project schemas with `source: 'project'`
-
-## 3. Update CLI Commands
-
-- [x] 3.1 Update `schemasCommand` to pass projectRoot and display source labels in output
-
-## 4. Update Call Sites
-
-- [x] 4.1 Review and update call sites that need project-local schema support to pass projectRoot
-
-## 5. Testing
-
-- [x] 5.1 Add unit tests for `getProjectSchemasDir()`
-- [x] 5.2 Add unit tests for project-local schema resolution priority
-- [x] 5.3 Add unit tests for backward compatibility (no projectRoot = user + package only)
-- [x] 5.4 Add unit tests for `listSchemas()` including project schemas
-- [x] 5.5 Add unit tests for `listSchemasWithInfo()` with `source: 'project'`
-- [x] 5.6 Add integration test with temp project containing local schema

package/OpenSpec-main/openspec/changes/archive/2026-02-17-schema-management-cli/.openspec.yaml

@@ -1,2 +0,0 @@
-schema: spec-driven
-created: 2026-01-20

package/OpenSpec-main/openspec/changes/archive/2026-02-17-schema-management-cli/design.md

@@ -1,113 +0,0 @@
-## Context
-
-OpenSpec uses workflow schemas to define artifact sequences for change proposals. Currently, schemas are resolved from three locations (project → user → package), but managing custom schemas requires manual file creation with no tooling support. The resolver infrastructure exists (`src/core/artifact-graph/resolver.ts`) but there's no CLI exposure for schema management operations.
-
-Users who want to customize workflows must:
-1. Manually create directory structures under `openspec/schemas/<name>/`
-2. Copy and modify `schema.yaml` files without validation
-3. Debug resolution issues by inspecting the filesystem directly
-
-This creates friction for schema customization and leads to runtime errors when schemas are malformed.
-
-## Goals / Non-Goals
-
-**Goals:**
-- Provide CLI commands for common schema management operations
-- Enable interactive schema creation with guided prompts
-- Allow forking existing schemas as customization starting points
-- Surface schema validation errors before runtime
-- Help debug schema resolution order when shadowing occurs
-
-**Non-Goals:**
-- Schema editing (users edit YAML directly or via `$EDITOR`)
-- Schema publishing or sharing mechanisms
-- Schema versioning or migration tooling
-- Validation of template file contents (only checks existence)
-- Schema inheritance or composition beyond simple forking
-
-## Decisions
-
-### 1. Command Structure: `openspec schema <subcommand>`
-
-Add a new command group following the existing pattern used by `openspec config` and `openspec completion`.
-
-**Rationale:** Grouping related commands under a noun (schema) matches the established CLI patterns and provides a natural namespace for future schema operations.
-
-**Alternatives considered:**
-- Flat commands (`openspec schema-init`, `openspec schema-fork`): Rejected because it pollutes the top-level namespace and doesn't scale well.
-- Extending existing commands (`openspec init --schema`): Rejected because schema management is distinct from project initialization.
-
-### 2. Implementation Location
-
-New file `src/commands/schema.ts` with a `registerSchemaCommand(program: Command)` function that registers the `schema` command group and all subcommands.
-
-**Rationale:** Follows the pattern established by `config.ts` and matches how other command groups are organized.
-
-### 3. Schema Validation Approach
-
-Validation checks:
-1. `schema.yaml` exists and is valid YAML
-2. Parses successfully against the Zod schema in `types.ts`
-3. All referenced template files exist in the schema directory
-4. Artifact dependency graph has no cycles (use existing topological sort)
-
-**Rationale:** Reuse existing validation infrastructure (`parseSchema` from `schema.ts`) and extend with template existence checks. This catches the most common errors without duplicating validation logic.
-
-**Alternatives considered:**
-- Deep template validation (check frontmatter, syntax): Rejected as over-engineering. Template contents are free-form markdown.
-
-### 4. Interactive Prompts for `schema init`
-
-Use `@inquirer/prompts` (already a dependency) for:
-- Schema name input with kebab-case validation
-- Schema description input
-- Multi-select for artifact selection with descriptions
-- Optional: set as project default
-
-**Rationale:** Matches the UX established by `openspec init` and `openspec config reset`. Provides a guided experience while keeping the wizard lightweight.
-
-### 5. Fork Source Resolution
-
-`schema fork <source>` resolves the source schema using the existing `getSchemaDir()` function, respecting the full resolution order (project → user → package). This allows forking from any accessible schema.
-
-The destination is always project-local: `openspec/schemas/<name>/`
-
-**Rationale:** Forking to project scope makes sense because:
-- Custom schemas are project-specific decisions
-- User-global schemas can be added manually if needed
-- Keeps the command simple with a clear default
-
-### 6. Output Format Consistency
-
-All commands support `--json` flag for machine-readable output:
-- `schema init`: Outputs `{ "created": true, "path": "...", "schema": "..." }`
-- `schema fork`: Outputs `{ "forked": true, "source": "...", "destination": "..." }`
-- `schema validate`: Outputs validation report matching existing validate command format
-- `schema which`: Outputs `{ "name": "...", "source": "project|user|package", "path": "..." }`
-
-Text output uses ora spinners for progress and clear success/error messaging.
-
-**Rationale:** Consistent with existing OpenSpec commands and enables scripting/automation.
-
-### 7. Schema `which` Command Design
-
-Shows resolution details for a schema name:
-- Which location it resolves from (project/user/package)
-- Full path to the schema directory
-- Whether it shadows other schemas at lower priority levels
-
-**Rationale:** Essential for debugging "why isn't my schema being used?" scenarios when multiple schemas with the same name exist.
-
-## Risks / Trade-offs
-
-**[Template scaffolding may become stale]** → The `schema init` command will scaffold a default set of artifacts (proposal, specs, design, tasks). If the built-in schema patterns evolve, these templates may not reflect best practices.
-- *Mitigation*: Document that `init` creates a minimal starting point. Users can `fork` built-in schemas for the latest patterns.
-
-**[Interactive prompts in CI environments]** → `schema init` with prompts may hang in non-interactive environments.
-- *Mitigation*: Support `--name`, `--description`, and `--artifacts` flags for non-interactive use. Detect TTY and show helpful error if prompts would hang.
-
-**[Validation doesn't catch all errors]** → Schema validation checks structure but can't verify semantic correctness (e.g., a template that doesn't match its artifact purpose).
-- *Mitigation*: This is acceptable. Full semantic validation would require understanding template intent, which is out of scope.
-
-**[Fork overwrites without warning]** → If target schema already exists, `fork` could overwrite it.
-- *Mitigation*: Check for existing schema and require `--force` flag or interactive confirmation before overwriting.

package/OpenSpec-main/openspec/changes/archive/2026-02-17-schema-management-cli/proposal.md

@@ -1,55 +0,0 @@
-## Why
-
-Creating and managing project-local schemas currently requires manual directory creation, copying files, and hoping the structure is correct. Users only discover structural errors at runtime when commands fail. This friction discourages schema customization and makes it harder to tailor OpenSpec workflows to specific project needs.
-
-Key pain points:
-- **Manual scaffolding**: Users must manually create `openspec/schemas/<name>/` with correct structure
-- **No validation feedback**: Schema errors aren't caught until a command tries to use the schema
-- **Starting from scratch is hard**: No easy way to base a custom schema on an existing one
-- **Debugging resolution**: When a schema doesn't resolve as expected, there's no way to see the resolution path
-
-## What Changes
-
-Add a new `openspec schema` command group with subcommands for creating, forking, validating, and inspecting schemas.
-
-### Commands
-
-1. **`openspec schema init <name>`** - Interactive wizard to scaffold a new project schema
-   - Prompts for schema description
-   - Prompts for artifacts to include (with explanations)
-   - Creates valid directory structure with `schema.yaml` and template files
-   - Optionally sets as project default in `openspec/config.yaml`
-
-2. **`openspec schema fork <source> [name]`** - Copy an existing schema as a starting point
-   - Copies from user override or package built-in
-   - Allows renaming (defaults to `<source>-custom`)
-   - Preserves all templates and configuration
-
-3. **`openspec schema validate [name]`** - Validate schema structure and templates
-   - Checks `schema.yaml` is valid
-   - Verifies all referenced templates exist
-   - Reports missing or malformed files
-   - Run without name to validate all project schemas
-
-4. **`openspec schema which <name>`** - Show schema resolution path
-   - Displays which location the schema resolves from (project/user/package)
-   - Shows full path to schema directory
-   - Useful for debugging shadowing issues
-
-## Capabilities
-
-### New Capabilities
-- `schema-init-command`: Interactive wizard for creating new project schemas with guided prompts
-- `schema-fork-command`: Copy existing schemas to project for customization
-- `schema-validate-command`: Validate schema structure and report errors before runtime
-- `schema-which-command`: Debug schema resolution by showing which location is used
-
-### Modified Capabilities
-<!-- None - these are additive commands -->
-
-## Impact
-
-- **Code**: New command implementations in `src/commands/` using existing resolver infrastructure
-- **CLI**: New `schema` command group with 4 subcommands
-- **Dependencies**: May use `enquirer` or similar for interactive prompts in `schema init`
-- **Documentation**: Need to update CLI reference and schema customization guide

package/OpenSpec-main/openspec/changes/archive/2026-02-17-schema-management-cli/specs/schema-fork-command/spec.md

@@ -1,66 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Schema fork copies existing schema
-The CLI SHALL provide an `openspec schema fork <source> [name]` command that copies an existing schema to the project's `openspec/schemas/` directory.
-
-#### Scenario: Fork with explicit name
-- **WHEN** user runs `openspec schema fork spec-driven my-custom`
-- **THEN** system locates `spec-driven` schema using resolution order (project → user → package)
-- **AND** copies all files to `openspec/schemas/my-custom/`
-- **AND** updates `name` field in `schema.yaml` to `my-custom`
-- **AND** displays success message with source and destination paths
-
-#### Scenario: Fork with default name
-- **WHEN** user runs `openspec schema fork spec-driven` without specifying a name
-- **THEN** system copies to `openspec/schemas/spec-driven-custom/`
-- **AND** updates `name` field in `schema.yaml` to `spec-driven-custom`
-
-#### Scenario: Source schema not found
-- **WHEN** user runs `openspec schema fork nonexistent`
-- **THEN** system displays error that schema was not found
-- **AND** lists available schemas
-- **AND** exits with non-zero code
-
-### Requirement: Schema fork prevents accidental overwrites
-The CLI SHALL require confirmation or `--force` flag when the destination schema already exists.
-
-#### Scenario: Destination exists without force
-- **WHEN** user runs `openspec schema fork spec-driven my-custom` and `openspec/schemas/my-custom/` exists
-- **THEN** system displays error that destination already exists
-- **AND** suggests using `--force` to overwrite
-- **AND** exits with non-zero code
-
-#### Scenario: Destination exists with force flag
-- **WHEN** user runs `openspec schema fork spec-driven my-custom --force` and destination exists
-- **THEN** system removes existing destination directory
-- **AND** copies source schema to destination
-- **AND** displays success message
-
-#### Scenario: Interactive confirmation for overwrite
-- **WHEN** user runs `openspec schema fork spec-driven my-custom` in interactive mode and destination exists
-- **THEN** system prompts for confirmation to overwrite
-- **AND** proceeds based on user response
-
-### Requirement: Schema fork preserves all schema files
-The CLI SHALL copy the complete schema directory including templates, configuration, and any additional files.
-
-#### Scenario: Copy includes template files
-- **WHEN** user forks a schema with template files (e.g., `proposal.md`, `design.md`)
-- **THEN** all template files are copied to the destination
-- **AND** template file contents are unchanged
-
-#### Scenario: Copy includes nested directories
-- **WHEN** user forks a schema with nested directories (e.g., `templates/specs/`)
-- **THEN** nested directory structure is preserved
-- **AND** all nested files are copied
-
-### Requirement: Schema fork outputs JSON format
-The CLI SHALL support `--json` flag for machine-readable output.
-
-#### Scenario: JSON output on success
-- **WHEN** user runs `openspec schema fork spec-driven my-custom --json`
-- **THEN** system outputs JSON with `forked: true`, `source`, `destination`, and `sourcePath` fields
-
-#### Scenario: JSON output shows source location
-- **WHEN** user runs `openspec schema fork spec-driven --json`
-- **THEN** JSON output includes `sourceLocation` field indicating "project", "user", or "package"

package/OpenSpec-main/openspec/changes/archive/2026-02-17-schema-management-cli/specs/schema-init-command/spec.md

@@ -1,71 +0,0 @@
-## ADDED Requirements
-
-### Requirement: Schema init command creates project-local schema
-The CLI SHALL provide an `openspec schema init <name>` command that creates a new schema directory under `openspec/schemas/<name>/` with a valid `schema.yaml` file and default template files.
-
-#### Scenario: Create schema with valid name
-- **WHEN** user runs `openspec schema init my-workflow`
-- **THEN** system creates directory `openspec/schemas/my-workflow/`
-- **AND** creates `schema.yaml` with name, version, description, and artifacts array
-- **AND** creates template files referenced by artifacts
-- **AND** displays success message with created path
-
-#### Scenario: Reject invalid schema name
-- **WHEN** user runs `openspec schema init "My Workflow"` (contains space)
-- **THEN** system displays error about invalid schema name
-- **AND** suggests using kebab-case format
-- **AND** exits with non-zero code
-
-#### Scenario: Schema name already exists
-- **WHEN** user runs `openspec schema init existing-schema` and `openspec/schemas/existing-schema/` already exists
-- **THEN** system displays error that schema already exists
-- **AND** suggests using `--force` to overwrite or `schema fork` to copy
-- **AND** exits with non-zero code
-
-### Requirement: Schema init supports interactive mode
-The CLI SHALL prompt for schema configuration when run in an interactive terminal without explicit flags.
-
-#### Scenario: Interactive prompts for description
-- **WHEN** user runs `openspec schema init my-workflow` in an interactive terminal
-- **THEN** system prompts for schema description
-- **AND** uses provided description in generated `schema.yaml`
-
-#### Scenario: Interactive prompts for artifact selection
-- **WHEN** user runs `openspec schema init my-workflow` in an interactive terminal
-- **THEN** system displays multi-select prompt with common artifacts (proposal, specs, design, tasks)
-- **AND** each option includes a brief description
-- **AND** uses selected artifacts in generated `schema.yaml`
-
-#### Scenario: Non-interactive mode with flags
-- **WHEN** user runs `openspec schema init my-workflow --description "My workflow" --artifacts proposal,tasks`
-- **THEN** system creates schema without prompting
-- **AND** uses flag values for configuration
-
-### Requirement: Schema init supports setting project default
-The CLI SHALL offer to set the newly created schema as the project default.
-
-#### Scenario: Set as default interactively
-- **WHEN** user runs `openspec schema init my-workflow` in interactive mode
-- **AND** user confirms setting as default
-- **THEN** system updates `openspec/config.yaml` with `defaultSchema: my-workflow`
-
-#### Scenario: Set as default via flag
-- **WHEN** user runs `openspec schema init my-workflow --default`
-- **THEN** system creates schema and updates `openspec/config.yaml` with `defaultSchema: my-workflow`
-
-#### Scenario: Skip setting default
-- **WHEN** user runs `openspec schema init my-workflow --no-default`
-- **THEN** system creates schema without modifying `openspec/config.yaml`
-
-### Requirement: Schema init outputs JSON format
-The CLI SHALL support `--json` flag for machine-readable output.
-
-#### Scenario: JSON output on success
-- **WHEN** user runs `openspec schema init my-workflow --json --description "Test" --artifacts proposal`
-- **THEN** system outputs JSON with `created: true`, `path`, and `schema` fields
-- **AND** does not display interactive prompts or spinners
-
-#### Scenario: JSON output on error
-- **WHEN** user runs `openspec schema init "invalid name" --json`
-- **THEN** system outputs JSON with `error` field describing the issue
-- **AND** exits with non-zero code