You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: make doc/status.md the single owner of current-state facts (#74)
doc/status.md now owns 'what is live right now'. Remove current-state claims
that had drifted from architecture.md and README and point to status.md:
- architecture.md: banner up top (design intent, not current state); reframe the
onboarding summary and the §8 identity model as intended design — drop the false
'no email accounts / already built / assumes a wallet' claims (the Privy email
path ships) and link to status.md for what actually ships. Design intent kept.
- README: deployed contract IDs and the contract-test count no longer restated
(they drift); the IDs now point to status.md, the count to the command.
- status.md: add a 'Which doc owns what' table so each doc under doc/ is the
single source for one thing.
Copy file name to clipboardExpand all lines: README.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,15 +101,11 @@ The browser is a trust boundary: every API route is read-only, no key ever touch
101
101
102
102
## ✅ What's live
103
103
104
-
> Deployed and verified on **Stellar testnet**.
104
+
> Deployed on **Stellar testnet**. **[`doc/status.md`](doc/status.md)** is the single source for what is live right now — the network, the deployed contract IDs, and exactly which features are on or off.
The deployed contract IDs (with explorer links) and the active network live in **[`doc/status.md`](doc/status.md)** — kept in one place rather than restated here, so they cannot drift out of sync.
113
109
114
110
### Product
115
111
@@ -145,7 +141,7 @@ The contracts implement the Stellar ecosystem standards that let a third party i
145
141
146
142
Claims here are checkable by cloning the repo and running the commands.
147
143
148
-
-**111 contract tests** — `cd contracts && cargo test --workspace`. Property-based tests over the distribution math (conservation, dust, non-negativity, clean overflow), boundary cases, TTL lifetime tests, and XDR-level event assertions.
144
+
-**Contract tests** — `cd contracts && cargo test --workspace`. Property-based tests over the distribution math (conservation, dust, non-negativity, clean overflow), boundary cases, TTL lifetime tests, and XDR-level event assertions.
149
145
-**Mutation testing** (cargo-mutants) — a full run over all three contracts generates **140 mutants**; the suite currently catches **125**, with 15 unviable and **0 surviving**. Reproduce with `cd contracts && cargo mutants`.
150
146
151
147
<sub>The four that survived the first full run were real gaps, all in the NFT: nothing asserted that a royalty of _exactly_ 1% or _exactly_ 15% is accepted (only that outside the range is rejected), that `get_royalty_info` tolerates a zero sale price, or that `burn_from` does anything at all. Tests were added rather than the claim narrowed.</sub>
@@ -220,7 +216,7 @@ pnpm dev
220
216
|`pnpm lint`| ESLint |
221
217
|`pnpm typecheck`|`tsc --noEmit` across the workspace |
222
218
|`pnpm --filter=web test`| Web + indexer unit tests |
223
-
|`cd contracts && cargo test --workspace`| The 111 contract tests |
219
+
|`cd contracts && cargo test --workspace`| The contract test suite|
224
220
225
221
> `pnpm test` at the root also runs `@molotov/indexer-db-tests`, an integration suite that needs a local Supabase (`supabase start`, requires Docker). Without the local stack those tests fail on a connection error — use the scoped commands above instead.
0 commit comments