feat: scaffold redsen-lean-harness v0.1.0
Recovered from crashed session (Node OOM). Repo contains full P0-P6 scaffold: plugin.json/marketplace.json, AGENTS.md, ADRs 0001-0006, lh CLI (init/index/graph/lane/run/memory/host/report/doctor), 10 .github/agents, 12 CLI skills, instructions, context7 mcp.json, and unit/e2e test suite. Fixed: run.mjs read --in-tokens/--out-tokens but tests and CLI docs use --input-tokens/--output-tokens, so telemetry totals were always 0. Now accepts both forms. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
@@ -0,0 +1,30 @@
|
||||
# {{PROJECT}} architecture
|
||||
|
||||
<!-- Living document. Update when components, data flow, invariants, or ADR outcomes change. Keep claims concrete and current. -->
|
||||
|
||||
## Purpose
|
||||
|
||||
Describe what this system exists to do, who uses it, and what success means.
|
||||
|
||||
## System context
|
||||
|
||||
List upstream callers, downstream services, data stores, queues, files, and trust boundaries.
|
||||
|
||||
## Components
|
||||
|
||||
- Component: responsibility, owner, key files.
|
||||
|
||||
## Data flow
|
||||
|
||||
1. Input source.
|
||||
2. Validation and transformation.
|
||||
3. Persistence or external calls.
|
||||
4. Output and observability.
|
||||
|
||||
## Key invariants
|
||||
|
||||
- Invariant: why it must hold, where enforced, how verified.
|
||||
|
||||
## Decision log (ADRs)
|
||||
|
||||
<!-- Append ADR links or summaries here. Newest last. -->
|
||||
Reference in New Issue
Block a user