NEC-51: Refresh the Relay snapshot to 0.8.12 #142
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
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!142
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-51-refresh-the-relay-snapshot-to-0812"
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-51 — https://projectron.nerchure.com/tasks/51
Refreshes docs/competition-relay.md from a 1 September snapshot to one taken 24 September against Relay 0.8.12, with every source re-read rather than recalled. Adds what 0.8.12 shipped (disk-edit ingestion pitched at agents, Canvas default-on with per-node/edge merging, Plugin API, Bases, background sync), what came after (Relay CLI, Relay Comments, OAuth-only sign-in), and their three open data-safety bugs with which the maintainer reproduced. Those bugs are recorded as a checklist for our own disk-edit path: applyMinimalDiff replaces a single span, and a disk edit to an open note defers to the editor binding, both untested against those shapes. Background sync is recorded as parity, not a lead. positioning.md and go-to-market.md lists updated to match. Three facts on the card were wrong (#137 not reproduced, password auth never supported, Relay Comments' beta status) and a review pass corrected seven more in the first draft; both are recorded in the spec.
Spec:
docs/changes/NEC-51-relay-snapshot-0812/spec.mdChangelog
NONE