openspec schema init --default sets a config key nothing reads #1708

The problem

openspec schema init <name> --default says it made your new schema the project default, but new changes keep using spec-driven.

The flag writes defaultSchema: <name> to openspec/config.yaml. Nothing in the CLI reads that key. The key the config loader actually reads is schema.

Reproduce

openspec schema init my-workflow --default
# ...
# Set as project default schema.

cat openspec/config.yaml
# defaultSchema: my-workflow

openspec new change test-change
# Creating change 'test-change' with schema 'spec-driven'...
# Schema: spec-driven

The new change is created with spec-driven, not my-workflow. No warning is printed.

Expected

After --default, new changes use the schema you just created:

openspec new change test-change
# Schema: my-workflow

That's what happens when openspec/config.yaml contains schema: my-workflow instead (verified by editing the file by hand).

Cause

• schema init --default writes the defaultSchema key: src/commands/schema.ts#L962-L977
• the config loader only reads schema: src/core/project-config.ts#L274-L280
• change creation resolves config?.schema ?? 'spec-driven': src/utils/change-utils.ts#L148-L150

So the flag has been a no-op since it was added in #525.

Fix

In schema init, write schema: <name> instead of defaultSchema: <name> (both branches: updating an existing config.yaml and creating a new one). Two lines.

openspec schema init --help ("Set as project default schema") and the success message are both correct once the key is fixed.

The CLI reference already describes the current behaviour honestly (docs-lab/reference/cli.md, the --default row under openspec schema init). Update that row once this lands.