[imanimanyara]

Summary

Adds eight Mermaid diagrams to the README and docs, and a test that keeps them well-formed.

• README.md: an overview. Owners and stores, the file and database layers, and the PHP, REST and console channels all go through the same actions.
• docs/architecture.md has three diagrams:
  • read resolution: owner → parents → global, through database → runtime JSON → shipped file, then the definition default and the caller's default, with the cache inside the database layer;
  • the write pipeline;
  • the seven tables.
• docs/recipes/moving-from-files-to-the-database.md: the promotion lifecycle.
• docs/tools/approvals.md: the change-request states.
• docs/tools/rest-api.md: a write request end to end, including ETag/If-Match and idempotency.
• docs/tools/tenancy.md: how none, column and database isolate data.
• docs/tools/commands.md: the doctor summary row now lists every check. The other recent features were checked against the code and were already documented accurately.

Guard

tests/Unit/MermaidDiagramsTest.php checks four things:

• every mermaid block starts with a known diagram type;
• quotes and brackets are balanced;
• no sequence participant uses a reserved name;
• it read at least 54 files and 8 diagrams.

It was proven red on an extra { and on participant Actor. Every block also parses with mermaid@11's own mermaid.parse().

Verification (local)

Pest: 713 passed. Pint: clean.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.