docs: add comprehensive echo technical teardown

[flyingrobots]

Summary

Add a full technical teardown in docs/technical-teardown.md covering:

• Entry-point walkthrough and command dispatch
• Golden paths for verify, inspect, wal, and bench
• Core engine execution lifecycle
• Data/model boundaries and deterministic hashing
• Concurrency and parallel merge semantics
• Validation failures and conflict handling
• Security and configuration boundaries
• Trade-offs and deep architectural trade-offs
• Mermaid diagrams (flowchart, sequence, state, timeline, class, and ER/architecture mappings)
• A new "Project Progress and Future Use Cases" section

Notes

This commit is documentation-only and is intentionally exhaustive for zero-to-hero onboarding into the Echo/Warp runtime.

[coderabbitai]

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 21 minutes and 1 second. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f481da9a-55d2-4151-8d48-2e44693b54ab

📥 Commits

Reviewing files that changed from the base of the PR and between b8b430a and 252712e.

📒 Files selected for processing (1)

• docs/technical-teardown.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch teardown

---

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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 718825c268

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[flyingrobots]

Activity Summary for Code Lawyer pass on PR #384.

#	Severity	Source	File	Commit	Outcome
1	P2	PR thread	docs/technical-teardown.md	50b9e475	Replaced local absolute /Users/james/git/echo-teardown/... source links with repo-relative links; also fixed markdownlint-invalid TOC fragment and ordered-list prefix found by the commit hook.
2	P2	PR thread	docs/technical-teardown.md	252712e0	Corrected Appendix B command examples to use echo-cli and real wal submission-posture long flags.

Self-audit found no additional issues beyond the PR review threads.

Local validation performed:

• Prettier check over docs/technical-teardown.md: passed.
• markdownlint over docs/technical-teardown.md: passed.
• Pre-commit and pre-push docs-only gates: passed.
• Linked-worktree hook stamp path was set with VERIFY_STAMP_DIR=$(git rev-parse --path-format=absolute --git-dir)/verify-local to avoid the known .git file issue without bypassing hooks.

All known unresolved review threads have been resolved via GraphQL.