Reply and like on a post are git primitives: a reply is a comment on its issue or pull, a like is a signal in the decision ledger #1086

Replaces #602, parked twice:

• the check failed ("capacity: only a forge admin reads or changes it > an admin changes each one from the page, the API and MCP; a wrong value is refused; every change is kept") and the decider saw no point in another try (pull #986 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
• the check failed ("capacity: only a forge admin reads or changes it > an admin changes each one from the page, the API and MCP; a wrong value is refused; every change is kept") and the decider saw no point in another try (pull #1041 closed).

Both checks went red on test/capacity.test.ts, which this change does not touch. This waits on #1047, which takes the tests red on main out of the gate, so the check measures this change. Start from today's main. Per the 2026-10-11 steering on #334, a post is a distilled milestone (#1084), so a reply or like lands on the post a person was happy to read. What done looks like is #602's, unchanged:

---

Pillar: P1 Feed (umbrella #587). One run, started fresh from today's main.

Outcome (what a person sees). Under any post you can reply, like or repost. A reply is a comment on that issue or pull; a like is a signal written to the decision ledger, which the crew and the feed read; a repost is a share.

Today. Share exists (POST /api/v1/share, MCP share). Comments exist. The ledger (decision table, src/core/decisions.ts) records next/land/retry, not likes.

Acceptance.

• [ ] Reply: inline under the post, writes a comment on its issue or pull, and shows as a reply under it.
• [ ] Like: toggles a like signal in the decision ledger for that issue or pull, with a count; feed affinity reads it.
• [ ] Repost: the existing share.
• [ ] A person and an agent do this with the same words: the page buttons and the MCP tools are named reply, like, share.

Done means reachable (all four, or the pull says which one does not apply and why):

• Page: the buttons under every post
• MCP: reply {issue|pull, body} and like {issue|pull}
• Test: reply lands as a comment; like writes and unwrites a ledger row; affinity moves
• Look: a post with a reply and a like, on the pull

Start from: src/core/decisions.ts, src/crew/ledger.ts, src/feed/share.ts, src/feed/affinity.ts, src/web/studio/feed.ts, src/http/feed.ts, src/http/mcp.ts.

Depends on: #599 (home is the feed).

Must not touch: the release workflow, the chart (charts/), other repositories.

Parked by the crew: the check failed ("a fork that follows its parent > a proposal names only what is actually ahead: work the parent already has is not listed again") and the decider saw no point in another try (pull #1372 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("report mode is loud to admins, and to nobody else > reported: the Capacity page says it once, as a note; vitals do not") and the decider saw no point in another try (pull #1548 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("a fork that follows its parent > a proposal names only what is actually ahead: work the parent already has is not listed again") and the decider saw no point in another try (pull #1372 closed)
2. the check failed ("report mode is loud to admins, and to nobody else > reported: the Capacity page says it once, as a note; vitals do not") and the decider saw no point in another try (pull #1548 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Deferred behind the Later gate (#595): reply and like (P1 Feed) wait while the owner's top is /flow and Boards. Both pulls went red on unrelated suites, so it should start again from a green main.