fix: architecture doccs syntax

[MartianGreed]

Closes #

Introduced changes

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Add a dedicated CI job for new examples
• Performed self-review of the code

Summary by CodeRabbit

• Documentation
  • Improved architecture diagram for readability: clearer subgraph names, richer node labels with line breaks, and more explicit edge descriptions.
  • Updated “What’s Next” roadmap: renamed "TanStack DB" item, refined wording (e.g., "manifests"), and added a cross-cutting note about incremental delivery for focused reviews.
  • Fixed knowledge‑base link to the architecture overview and refreshed the last-updated timestamp.

[coderabbitai]

Walkthrough

Refactors documentation: Mermaid diagram labels in the architecture overview were changed to quoted strings, node labels gain HTML-like line breaks, and edge labels were clarified; the "What's Next" TanStack DB section wording and cross-cutting note were updated; the knowledge-base link and timestamp were updated. No behavior or control flow changes.

Changes

Cohort / File(s)	Summary
Architecture Overview Diagram etc/architecture/overview.md	Reformatted Mermaid diagram: subgraph labels converted to quoted/phrased strings, node labels use <br/> line breaks, edge labels made more explicit/quoted, plus minor whitespace/formatting edits. No semantic or control-flow changes.
Roadmap / What’s Next etc/architecture/whats-next.md	Renamed “TanStack/DB” → “TanStack DB”; generalized “Dojo manifests” to “manifests”; updated Key Steps and added cross-cutting note about maintaining incremental delivery via stacked jj changes.
Knowledge Base etc/knowledge-base.md	Updated architecture snapshot link to etc/architecture/overview.md and refreshed last-updated timestamp.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I hop through docs with whiskered cheer,
Quoting nodes so lines read clear.
A dash removed, a manifest light,
Links refreshed beneath the night.
(\_/) 🥕 Small changes—big delight.

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The title contains a spelling error (“doccs” instead of “docs”) and is overly generic, failing to clearly convey what specific syntax corrections were made in the architecture documentation.	Please correct the typo to “docs” and revise the title to concisely describe the change, for example “fix: correct Mermaid syntax in architecture docs.”
Description Check	⚠️ Warning	The pull request description is just the unmodified template with no issue reference, no description of the actual changes, and an unchecked checklist, so it provides no useful context.	Populate the template by linking any resolved issues, summarizing the specific documentation changes made, and completing the checklist items to reflect updated documentation and any added tests or CI jobs.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/arch-docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

etc/architecture/overview.md (1)

47-50: Avoid quoting Mermaid edge labels.

Wrapping edge text in quotes renders the quotes literally in Mermaid. Prefer the pipe syntax so the labels stay clean.

-    World -- "events & state" --> ToriiIndexer
-    CoreProvider -- "invoke / call" --> World
-    ToriiIndexer -- "queries / subscriptions" --> ToriiWasm
-    ToriiIndexer -- "gRPC streams" --> GrpcClient
+    World --|events & state|--> ToriiIndexer
+    CoreProvider --|invoke / call|--> World
+    ToriiIndexer --|queries / subscriptions|--> ToriiWasm
+    ToriiIndexer --|gRPC streams|--> GrpcClient

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d7107ba and b302b88.

📒 Files selected for processing (3)

• etc/architecture/overview.md (1 hunks)
• etc/architecture/whats-next.md (2 hunks)
• etc/knowledge-base.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• etc/knowledge-base.md

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-09-23T14:02:06.709Z

Learnt from: CR
PR: dojoengine/dojo.js#0
File: AGENTS.md:0-0
Timestamp: 2025-09-23T14:02:06.709Z
Learning: Prefer small, stacked changes using jj new and jj describe

Applied to files:

• etc/architecture/whats-next.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: build-examples
• GitHub Check: build-packages
• GitHub Check: build

🔇 Additional comments (3)

etc/architecture/whats-next.md (2)

32-39: Terminology edit improves clarity.

Switching the TanStack section title and generalizing the manifest reference reads cleaner and better matches current naming.

---

61-61: Appreciate the incremental-delivery reminder.

The cross-cutting note reinforces our stacked jj preference and keeps the roadmap actionable. Based on learnings

etc/architecture/overview.md (1)

18-32: Mermaid subgraph/node updates render well.

Quoting the subgraph titles and using <br/> in node labels improves the diagram’s readability without altering structure.