The first paragraph of README.md called mfer/mf.proto the format specification and linked to it. It now links docs/FORMAT.md as the specification and names mfer/mf.proto as the protobuf schema that document refers to for exact field numbers and types.
The other mentions already agreed, so nothing else changes: the README's Design section calls mfer/mf.proto the protobuf schema, its design questions point to both files, and AGENTS.md names docs/FORMAT.md as the format specification.
Judgement call: the new link is relative (docs/FORMAT.md), like the README's link to REPO_POLICIES.md. The old one was an absolute link to the main branch, and docs/FORMAT.md is not on main yet, so a link of that kind would be dead until next is merged.
The first paragraph of `README.md` called `mfer/mf.proto` the format specification and linked to it. It now links `docs/FORMAT.md` as the specification and names `mfer/mf.proto` as the protobuf schema that document refers to for exact field numbers and types.
The other mentions already agreed, so nothing else changes: the README's Design section calls `mfer/mf.proto` the protobuf schema, its design questions point to both files, and `AGENTS.md` names `docs/FORMAT.md` as the format specification.
Judgement call: the new link is relative (`docs/FORMAT.md`), like the README's link to `REPO_POLICIES.md`. The old one was an absolute link to the `main` branch, and `docs/FORMAT.md` is not on `main` yet, so a link of that kind would be dead until `next` is merged.
Closes https://git.eeqj.de/sneak/mfer/issues/166
Model: opus-5-5
clawbot
self-assigned this 2026-10-07 15:35:40 +02:00
The README's opening paragraph called mfer/mf.proto the format specification
and linked to it. It now links docs/FORMAT.md, which is the specification, and
names mfer/mf.proto as the protobuf schema that document refers to for field
numbers and types. The link is relative, as the README's link to
REPO_POLICIES.md is, because docs/FORMAT.md is not on main yet.
Model: opus-5-5
Judgement call: the relative link docs/FORMAT.md is accepted; it resolves on the Gitea repository page of any branch that contains the file, so on next now and on main once merged.
Not checked: how renderers outside Gitea treat the relative link.
Model: opus-5-5
Review passed.
- Gated on `next` at `4fe1ff2`.
- Judgement call: the relative link `docs/FORMAT.md` is accepted; it resolves on the Gitea repository page of any branch that contains the file, so on `next` now and on `main` once merged.
- Not checked: how renderers outside Gitea treat the relative link.
Model: opus-5-5
clawbot
merged commit dce5e050c3 into next2026-10-07 15:59:11 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The first paragraph of
README.mdcalledmfer/mf.protothe format specification and linked to it. It now linksdocs/FORMAT.mdas the specification and namesmfer/mf.protoas the protobuf schema that document refers to for exact field numbers and types.The other mentions already agreed, so nothing else changes: the README's Design section calls
mfer/mf.protothe protobuf schema, its design questions point to both files, andAGENTS.mdnamesdocs/FORMAT.mdas the format specification.Judgement call: the new link is relative (
docs/FORMAT.md), like the README's link toREPO_POLICIES.md. The old one was an absolute link to themainbranch, anddocs/FORMAT.mdis not onmainyet, so a link of that kind would be dead untilnextis merged.Closes #166
Model: opus-5-5
Review passed.
nextat4fe1ff2.docs/FORMAT.mdis accepted; it resolves on the Gitea repository page of any branch that contains the file, so onnextnow and onmainonce merged.Model: opus-5-5