Why
An agent or human looking for per-workflow schema docs will hunt for a directory that does not exist.
Current state
docs/decisions/003-config-model.md line 93 reads: "Per-workflow schemas live in config/schemas/workflows/ and document what each workflow accepts." The directory config/schemas/ contains only hub.toml.schema.json and README.md — no workflows/ subdirectory.
Ideal state
- The line is rewritten to describe the actual model: per-workflow object shapes live as
workflow_<name> definitions inside config/schemas/hub.toml.schema.json
- OR the
config/schemas/workflows/ directory is created and populated with the per-workflow schemas the ADR describes
Starting points
docs/decisions/003-config-model.md line 93
config/schemas/hub.toml.schema.json (see definitions section for actual per-workflow shapes)
config/schemas/README.md
QA plan
- Read
docs/decisions/003-config-model.md around line 93 — expect no reference to a missing path
- Verify the description of where per-workflow schema shapes live matches
config/schemas/ as it actually exists
Done when
ADR 003 no longer references config/schemas/workflows/.
Why
An agent or human looking for per-workflow schema docs will hunt for a directory that does not exist.
Current state
docs/decisions/003-config-model.mdline 93 reads: "Per-workflow schemas live inconfig/schemas/workflows/and document what each workflow accepts." The directoryconfig/schemas/contains onlyhub.toml.schema.jsonandREADME.md— noworkflows/subdirectory.Ideal state
workflow_<name>definitions insideconfig/schemas/hub.toml.schema.jsonconfig/schemas/workflows/directory is created and populated with the per-workflow schemas the ADR describesStarting points
docs/decisions/003-config-model.mdline 93config/schemas/hub.toml.schema.json(seedefinitionssection for actual per-workflow shapes)config/schemas/README.mdQA plan
docs/decisions/003-config-model.mdaround line 93 — expect no reference to a missing pathconfig/schemas/as it actually existsDone when
ADR 003 no longer references
config/schemas/workflows/.