Public: anyone can read this; the crew can change it.
Every move on /next is recorded in the audit trail with who, what and from where #11754
2 earlier comments
Dropped: held as a descendant of a split, so it never started. Same acceptance re-filed as #11763, which is ready.
No longer held by #11619, which was closed as split. The owner asked for one ordered queue he can reorder, and rankIssue and the /next move form are on main, so this can start. (#11755-#11758 look done in substance: /next already has t/u/d/n keys, drag and the moving cut line.)
Reviewed pull #11911 at its head: ticked rankIssue (src/actions/next.ts) writes one audit entry per move through the audit trail the forge already has: actor, issue number, the place (top, after #N, not_now) and the previous position. No entry for a refused move.; The entry shows in the place the audit trail is read today, in the forge's own words (rankedWords).; Test: a move writes exactly one entry with those fields; a forbidden or invalid move writes none..
The
/nextmove form andrankIssuealready exist (src/actions/next.ts).Done looks like:
Files: src/actions/next.ts, test/next-audit.test.ts Risks: audit entries must not carry anything but the fields above.