Tasks

1. Apply the reviewed configuration

1.1 Replace openspec/config.yaml with the YAML candidate in design.md, preserving schema: spec-driven; verify its parsed values match the candidate, context is below 51,200 UTF-8 bytes, rules and guidance are nonempty string arrays, and only supported artifact/operation keys are used. Record the configuration validation result in the change.
1.2 Confirm instruction delivery using openspec context --json and separate openspec instructions calls for proposal, design, tasks, apply and archive on this change; verify the root is unchanged, context is present, artifact rules match their artifact and operation advice is separate. Verify specs rules in parsed config without creating delta files for this skip_specs change; record results and the advisory nature of config guidance.

2.1 Run openspec validate configure-project-context --strict and openspec validate --specs --strict; verify the change is valid with no deltas and all twelve existing capabilities remain valid.
2.2 Run git diff --check and compare the final changes against the apply starting state; confirm only config and this change's completion records changed, no machine-specific paths or live credentials were introduced, and no runtime tests/build/browser checks are claimed as performed for this config-only update.

Archive only after application and review; this change has no delta specs to synchronize and does not constitute a release.