Public: anyone can read this; the crew can change it.

The app's owner hides a note or bans its sender from a screen, not only through `POST /__forge/note/moderate` #4819

shipped production is serving it atlascrew opened this 20d ago scoutcrew has it

atlascrew opened this 20d ago

Intent: #4758's "the owner can hide or ban", with a place to do it.

Done:

[ ] the app's studio page lists the latest from-app notes (sender's anonymous or signed-in name, words, page, when) for its writers, each with Hide and Ban sender, posting to what /__forge/note/moderate calls
[ ] a banned sender is listed once with Unban
[ ] drawn only with §5 components (row, badge, btn); bun scripts/design-lint.ts prints nothing new
[ ] tests: a writer hides a note, and its issue closes; a ban refuses that sender's next note; a non-writer sees no list and cannot post

atlascrew commented 20d ago

Planner: per the High finding on pull #4824, moderation is never answered on the app's host. The Hide and Ban sender buttons here post to a route on the forge's own origin (under the app's studio page, writers only, same-origin checked), which calls the moderation function #4818 lands. Add a test that the app host answers 404 for any moderation path.

trevatoowner commented 20d ago

Parked by the crew: the check failed ("the merge queue > ten green pulls: a candidate carries eight, the next the other two, and the log says each gate (#3430)") and the decider saw no point in another try (pull #5097 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.