protocol: reclaim the numbers pre-release churn retired #339

Merged

natsukium merged 1 commit from issue-330 into main 2026-09-22 03:31:25 +09:00

Conversation 0 Commits 1 Files changed 26 +177 -339

natsukium commented 2026-09-22 02:04:11 +09:00

Owner

Copy link

Closes #330.

The 1.0 base schema no longer carries pre-release history: the 25 reserved declarations and their "field N was…" comments are gone, surviving fields and enum values are renumbered densely, ConnWelcome.build_id (superseded by identity) is dropped, and the 86 base arms omit since: 0, so a since appears only where a minor adds an arm. The five reserved 100; slots stay: they are the live wire-wide correlation envelope for the uncorrelated families, not history. This applies the schema's own rule that a number retired before any baseline exists is free again; BREAKING.md acknowledges the break against the merge-base.

Also records the #326 item-1 decision inline in the IPC explanation: SessionMsg keeps its field-100 envelope as a correlation-capable family with no base arm using it yet.

Decision: the last comment on #330 (six rounds of design review). Code review: pi luna (PASS, two non-blocking fixed: a stale comment, untyped documented) then pi sol (PASS).

First of the sequential proto PRs; #328, #327, #333 rebase on this one.

Closes #330. The 1.0 base schema no longer carries pre-release history: the 25 `reserved` declarations and their "field N was…" comments are gone, surviving fields and enum values are renumbered densely, `ConnWelcome.build_id` (superseded by `identity`) is dropped, and the 86 base arms omit `since: 0`, so a `since` appears only where a minor adds an arm. The five `reserved 100;` slots stay: they are the live wire-wide correlation envelope for the uncorrelated families, not history. This applies the schema's own rule that a number retired before any baseline exists is free again; `BREAKING.md` acknowledges the break against the merge-base. Also records the #326 item-1 decision inline in the IPC explanation: `SessionMsg` keeps its field-100 envelope as a correlation-capable family with no base arm using it yet. Decision: the last comment on #330 (six rounds of design review). Code review: pi luna (PASS, two non-blocking fixed: a stale comment, `untyped` documented) then pi sol (PASS). First of the sequential proto PRs; #328, #327, #333 rebase on this one.

natsukium added 1 commit 2026-09-22 02:04:11 +09:00

protocol: reclaim the numbers pre-release churn retired ... 95b6688494

The first public wire contract is the minor-0 base schema, and it is
the last point at which a retired number is free to take back: the
schema's own rule is that a number retired while no baseline exists is
free again, and after the freeze every gap is permanent. Carrying them
past it would make a reader of the first public schema reason about
what a missing field used to hold, and would leave the schema narrating
its own pre-release history in comments, which is what git log is for.

`ConnWelcome.build_id` goes the same way: it existed only for a reader
that knows nothing but that field, and no such reader can exist before
the first release. `BuildIdentity` says the same thing typed and in
full, so `felis version` and `felis doctor` read the one field.

Field 100 stays reserved on Conn, Input, Grid, Image and Push. It is
not history but the live wire-wide correlation-envelope slot: reserving
it on the families that carry no envelope is what keeps the number
uniform, so a reader lifts the envelope off any body without a
per-family table.

`since: 0` goes from the base arms because 0 is the proto3 default and
never reaches the descriptor, so spelling it declares a row the schema
cannot be written to carry; an addition is now the one place a `since`
appears.

Renumbering is a wire break, acknowledged in BREAKING.md against the
merge-base: a daemon and a client across this change must be rebuilt
together.

Assisted-by: Claude Code

natsukium force-pushed issue-330 from 95b6688494 to 52cf38def0 2026-09-22 02:45:48 +09:00 Compare

natsukium merged commit 7f7ca048f7 into main 2026-09-22 03:31:25 +09:00

natsukium deleted branch issue-330 2026-09-22 03:31:25 +09:00

natsukium referenced this pull request from a commit 2026-09-22 03:31:26 +09:00

protocol: reclaim the numbers pre-release churn retired (#339)

natsukium referenced this pull request 2026-09-22 03:34:04 +09:00

protocol: put a resource row's scope-dependent numbers in its scope arm #340

natsukium referenced this pull request 2026-09-22 14:37:30 +09:00

[v0.1/P1] Final interface simplification audit before public freeze #326

natsukium referenced this pull request 2026-09-22 15:13:09 +09:00

protocol: split the refusal into an attach half and a spawn half #345

Commenting is not possible because the repository is archived.

Reviewers

No reviewers

Labels

Clear labels   

priority/P0

Must be resolved before the v0.1.0 tag

  

priority/P1

Must be settled before the first public contract freezes

  

priority/P2

Explicitly deferred until after v0.1.0

  

release/v0.1.0

Work tracked for the first tagged release

  

status/blocked

Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  

status/planned

Triaged with a source-grounded plan and a passed pi review; ready to implement

  

type/bug

Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  

type/design

An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  

type/test-gap

Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  

type/tracker

Parent issue that tracks child work

No labels

priority/P0

priority/P1

priority/P2

release/v0.1.0

status/blocked

status/planned

type/bug

type/design

type/test-gap

type/tracker

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

natsukium/felis!339

No description provided.