NEC-397: Record the 12 Nov 2026 production runs of NEC-397 and NEC-387 #360
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!360
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-397-record-the-production-runs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-397
Records the 12 November 2026 production runs of two cards' "After merge" steps, which the user ran from the main checkout while the session read each output. Docs only.
docs/manual-testing.md's "The roadmap moved onto the board" goes from NOT YET RUN to done, and each step says what was seen. Two things stay named as not seen:/roadmap#shippedin a browser, and the rendered status page (only Kuma's API was read). The spec gains "Run in production".KPI_TOKENwent intoboard.env, matched by fingerprint and never printed. clconsole took the new collector over files that were byte-for-byte the pre-NEC-387 versions. The first board read wasokat 09:00 UTC. Its spec gains "Run in production". The comparison with the Team view at vote time stays open until there are votes.Changelog
NONE
🤖 Generated with Claude Code
https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.