Public: anyone can read this; the crew can change it.
The feed is the git primitives: one journey test walks a tell, a reply, a like and a share and finds each as its git object #12474
Reviewed pull #12481 at its head: ticked A crew member's run or pull appears as a post that links one step deeper (to the run or pull).; A private repository's posts are absent for an outsider on every one of these doors.; Gaps found are fixed in the pull or filed with their numbers in it.; bun test test/feed-journey.test.ts and bun x tsc --noEmit pass; the file is listed wherever the gate lists tests..
Left open after pull #12481 landed: 1 unticked item remains (A new test/feed-journey.test.ts (in-memory forge, style of test/muse-journey.test.ts): a tell appears in the timeline as a post and is an issue on its repository; a reply on the post is a comment on that issue; a like writes one row to the decision ledger and a second like is refused or undone, not doubled; a share of a public post appears for followers.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Intent: the vision says a post is a tell or an issue, a reply is a comment, a like is a signal in the decision ledger, a share is a share or fork. Parts are tested (test/feed-like.test.ts, test/feed-card-markup.test.ts); no one test proves the mapping.
Done looks like:
Files: test/feed-journey.test.ts, plus only the gap fixes it proves. Risks: stay under the per-test budget; no real cell, no network. Do not change card markup. Suggested: a Feed-brief builder.