AGENTS.md project tree calls clients/ "one subdir per service" but layout is flat

[ooloth]

Why

A cold reader (human or agent) following AGENTS.md will create clients/src/<service>/mod.rs when adding a new client, contradicting the existing flat convention.

Current state

Line 31 reads clients/ # external API wrappers — one subdir per service. The actual layout in clients/src/ is flat files: github.rs, linear.rs, lib.rs, plus the private/ symlink. clients/README.md itself uses the permissive wording "one file or subdirectory per external service".

Ideal state

• AGENTS.md line 31 matches the permissive wording, e.g. one file (or subdirectory) per external service
• AGENTS.md and clients/README.md are consistent with each other

Starting points

• AGENTS.md line 31
• clients/README.md line 7

QA plan

1. Read AGENTS.md line 31 and clients/README.md line 7 — expect both to use equivalent wording
2. Check clients/src/ listing — expect the wording to accurately describe the flat layout

Done when

AGENTS.md no longer prescribes a subdir-only layout for clients/.

[ooloth]

Two additional drift findings in the same file (surfaced by /repo-scan docs), worth folding into the same fix pass since the file should be re-read end-to-end:

1. Stack table claims SQLite is in use, but no SQLite is wired in.

Line 23 of the Stack table:

| SQLite | rusqlite (bundled) or sqlx |

store/Cargo.toml has only domain = { path = "../domain" } — no rusqlite, no sqlx. store/src/lib.rs is empty. (Also tracked for store/README.md in #23.)

2. "No registration step" claim contradicts add-a-workflow.md.

Line 11:

Extensible — adding a new workflow = adding files to clients/ and workflows/; no registration step

docs/playbooks/add-a-workflow.md lists 7 explicit registration steps, including a WorkflowConfig enum variant in config/src/toml.rs, an rstest case, a JSON schema definition + oneOf entry in config/schemas/hub.toml.schema.json, a hub.toml.example entry, and CLI wiring in ui/cli/src/main.rs. The "no registration step" framing is inaccurate.

A fix that resolves #20, the stack-table claim, and the "no registration step" framing in one pass keeps the file internally consistent.