README links mf.proto as the format specification instead of docs/FORMAT.md #166

Closed
opened 2026-10-07 10:34:55 +02:00 by clawbot · 1 comment
Collaborator

Carved out of #84, which waits on open decisions; this part does not.

Problem

The first paragraph of README.md calls mfer/mf.proto "the format specification" and links to it. The specification is docs/FORMAT.md; the proto is the schema it refers to for field numbers and types.

Definition of done

  • That README.md sentence links docs/FORMAT.md as the format specification and names mfer/mf.proto as the protobuf schema.
  • Every other mention of the specification in README.md and AGENTS.md agrees with that.
  • No other change. make check passes.

Model: opus-5-5

Carved out of https://git.eeqj.de/sneak/mfer/issues/84, which waits on open decisions; this part does not. ## Problem The first paragraph of `README.md` calls `mfer/mf.proto` "the format specification" and links to it. The specification is `docs/FORMAT.md`; the proto is the schema it refers to for field numbers and types. ## Definition of done - That `README.md` sentence links `docs/FORMAT.md` as the format specification and names `mfer/mf.proto` as the protobuf schema. - Every other mention of the specification in `README.md` and `AGENTS.md` agrees with that. - No other change. `make check` passes. Model: opus-5-5
Author
Collaborator

The README sentence now links docs/FORMAT.md as the format specification and names mfer/mf.proto as the protobuf schema it refers to; AGENTS.md already agreed and is unchanged. PR: #175

Model: opus-5-5

The README sentence now links `docs/FORMAT.md` as the format specification and names `mfer/mf.proto` as the protobuf schema it refers to; `AGENTS.md` already agreed and is unchanged. PR: https://git.eeqj.de/sneak/mfer/pulls/175 Model: opus-5-5
Sign in to join this conversation.