docs: update roadmap to reflect current state

··· 6 6 7 7 ## now 8 8 9 + - use zat in real projects and let usage drive what's next 9 10 - keep current APIs stable (0.x semver) 10 11 - tighten docs/examples as real apps discover sharp edges 11 - - keep the “primitives, not framework” ethos 12 + - keep the "primitives, not framework" ethos 12 13 13 14 ## next 14 15 15 16 ### polish 16 17 17 18 - improve docs around common workflows: 18 - - resolving handle → DID → PDS 19 - - making XRPC calls + parsing JSON 20 - - verifying JWTs from DID documents 19 + - ~~resolving handle → DID → PDS~~ done: `HandleResolver` (HTTP + DoH), `DidResolver`, `DidDocument` 20 + - ~~making XRPC calls + parsing JSON~~ done: `Xrpc`, `json` helpers 21 + - verifying JWTs from DID documents (`Jwt` exists, docs could be better) 21 22 - add more integration tests that hit real-world edge cases (without becoming flaky) 22 23 23 24 ### primitives 24 25 25 26 - fill gaps that show up repeatedly in other atproto projects: 26 - - CIDs and common multiformats plumbing 27 - - richer `AtUri` helpers (safe joins, parsing variants) 28 - - more ergonomic JSON navigation patterns (still optional, no forced codegen) 27 + - ~~CIDs and common multiformats plumbing~~ done: `multibase`, `multicodec` 28 + - ~~richer `AtUri` helpers~~ done: `AtUri` with parsing, formatting 29 + - ~~more ergonomic JSON navigation patterns~~ done: `json` module (still optional, no forced codegen) 30 + - sync types for firehose consumption (`CommitAction`, `EventKind`, `AccountStatus`) 29 31 30 32 ## later (maybe) 31 33