docs: add scope headers + Next: footers to all tour docs
Each of the eight tour docs (README, DESIGN, docs/CRYPTO, docs/FORMATS, docs/SECURITY, crates/relicario-core/ARCHITECTURE, crates/relicario-cli/ARCHITECTURE, extension/ARCHITECTURE) now declares its scope in a blockquote under its H1 and ends with a single-line "Next:" pointer to the next doc in the canonical reading order: README → DESIGN → CRYPTO → FORMATS → SECURITY → core → cli → extension. Also trimmed README's mid-section "Architecture" stub to a one- paragraph pointer at DESIGN.md (was duplicating cross-codebase content and referencing a non-existent docs/architecture/ tree). Renamed docs/CRYPTO.md's H1 from "Relicario — Architecture" to "Relicario — Crypto Pipeline" to match the file's renamed scope. Spec: docs/superpowers/specs/2026-05-30-doc-structure-redesign-design.md
This commit is contained in:
@@ -1,10 +1,6 @@
|
||||
# Architecture: relicario extension
|
||||
|
||||
> Strategic-depth doc for the `extension/` codebase. Pairs with `/CLAUDE.md`
|
||||
> at the repo root (project-level summary) and the typed-items design spec
|
||||
> under `docs/superpowers/specs/`. Things that are easy to recover from
|
||||
> reading code are deliberately omitted; things that are not — invariants,
|
||||
> multi-file control flow, design rationale — go here.
|
||||
> **Audience:** contributors editing the browser extension. This doc owns the bundle structure (popup, vault tab, background SW, content scripts), the SW ↔ popup message contract, the component / pane architecture, routing, and the build pipeline. **Does NOT own:** WASM crypto internals (see [../crates/relicario-core/ARCHITECTURE.md](../crates/relicario-core/ARCHITECTURE.md)), wire formats (see [../docs/FORMATS.md](../docs/FORMATS.md)), or threat model (see [../docs/SECURITY.md](../docs/SECURITY.md)).
|
||||
|
||||
## What this codebase is for
|
||||
|
||||
@@ -870,3 +866,7 @@ still required before shipping.
|
||||
next to `relicario_wasm_bg.wasm`. The runtime calls
|
||||
`WebAssembly.instantiateStreaming(fetch(URL))` against a
|
||||
hardcoded path; we just hand it that path.
|
||||
|
||||
---
|
||||
|
||||
**End of tour.** For roadmap and in-flight work see [../STATUS.md](../STATUS.md) and [../ROADMAP.md](../ROADMAP.md).
|
||||
|
||||
Reference in New Issue
Block a user