Skip to content

docs(protocol): proto 2 frozen with the console v0.2.0 / core v0.3.0 pair #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
temrjan merged 1 commit into from
Jul 15, 2026
Merged

docs(protocol): proto 2 frozen with the console v0.2.0 / core v0.3.0 pair #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/APPROVER-PROTOCOL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,8 @@
> is documented as-is and cross-referenced to a tracked follow-up rather than
> silently "corrected" here.
>
> **proto 2 — DRAFT** (Console v2 Фаза 2) — additive over proto 1: the read-ops
> **proto 2 — FROZEN** with the `console v0.2.0` / `core v0.3.0` release pair
> (2026-07-15) — additive over proto 1: the read-ops
> `context` (§3.7), `positions` (§3.8) and `activity` (§3.9), gated behind `auth`
> unlike `list`/`get` (§2), plus the `wallet_locked` error code (§3.11). A
> `proto: 1` session negotiated by an already-shipped `console v0.1.0` continues
Expand Down Expand Up @@ -477,7 +478,7 @@ must mirror them exactly (e.g. `amount_wei` is a decimal string while a nested
| proto | core (server) | console (client) |
|-------|---------------|------------------|
| 1 | shipped as `0.1.0`; freezes at `v0.2.0` | ≥ `v0.1.0` |
| 2 | DRAFT — adds `context` (§3.7) + `positions` (§3.8) + `activity` (§3.9) + `wallet_locked` (§3.11); freezes alongside its own console/core release pair (TBD) | a `proto:1` client is unaffected — it never sends `context`/`positions`/`activity` and the server still answers its `hello` with `proto:1` (§3.1) |
| 2 | frozen at `core v0.3.0` (adds `context` §3.7 + `positions` §3.8 + `activity` §3.9 + `wallet_locked` §3.11) | frozen at `console v0.2.0`; a `proto:1` client is unaffected — it never sends `context`/`positions`/`activity` and the server still answers its `hello` with `proto:1` (§3.1) |

- **`proto` is the only compatibility gate.** The `server` version string is
informational (§3.1) — a client must never gate on it. The shipped server reports
Expand Down
Loading