notification_kind

Kinds of notification: a notification's kind. A notification names who sent it, where, and when, never what they wrote; read its content with notifications.read.

Value	Meaning
`announce`	Another participant announced it is about to change, or has just changed, a range of a file.
`hold`	Another participant objected to your announced change: your edit waits, and a thread on the range holds their reason.
`note`	Another participant answered your announced change with information only; your edit goes ahead.
`ask`	Another participant asked you a question in a thread, which stays open until it is answered.
`answer`	Another participant answered a question you asked.
`say`	Another participant added a message to a thread you are in, with no reply expected.
`stale_save`	A save of yours to a mirrored file was applied on an older version of the file than the one it replaced, so others' changes between them may be merged into it.
`refused_save`	A save of yours to a mirrored file was refused and not shared; its content says which rule refused it and how to recover.
`write_held`	The mirror could not write a file you author because another program held it open or denied access to it (Windows), and stopped trying after its deadline: the file on disk is older than its document. Close the file in the program holding it; the next render writes it.
`action_failed`	An action failed at a frontier, and you changed a file it reads since the frontier where it last passed: one per action and failing streak. It names the action, both frontiers, the lines you changed, and the window's other authors; its content is the failing output's tail. Fix the change, then the next passing frontier sends an `action_succeeded`.
`action_succeeded`	An action that failed after your change passes again at a later frontier, which ends its failing streak.
`derived_superseded`	Your version of a derived (generated) file is not the one shown: another participant's version of it was chosen, so yours is hidden.
`derivation_failed`	A generator failed, or runners disagreed on its output, on inputs you changed since its last counted generation: one per derivation, a newer one replacing it. Its content names the generated file to run `lvcs explain` on, which shows the generator and the failure; fix the inputs.
`incompatible_peer`	A peer of the project runs a release whose wire major version differs from this daemon's, or speaks no sync protocol this daemon does, so nothing syncs with it: one per peer and daemon run. Its content names the peer, both versions, and who upgrades: you (`upgrade`) when the peer's is newer, else the peer's owner (`ask`). `lvcs status` lists the peer too.
`git_import`	Commits made outside LVCS on a mapped git branch were imported onto main, or a rewrite of the branch was refused: it names the branch and the head; its content lists each commit (id, author, subject) and each path written or skipped and why. A rewrite's `error` says how to restore the branch; a path skipped for a conflict is redone by hand (`rebase`).
`protected_held`	A change to a protected path by a participant who doesn't hold `Approve` on it is held, while the approved `lvcs.toml` declares no change action: to the owner and each `Approve` holder this daemon holds, once per path and held heads. It names the path; its content names who wrote it. Your own edit of the path built on the held change approves it, so read the held change first (`read` at main shows it).
`issue_claimed`	Another participant took an issue, or a plan task, assigned to you, after you were not present on the issue for `ISSUE_PRESENCE_SECS`. It names the issue, the task, and who took it; `lvcs issue view` shows the issue.
`claim_held`	Your claim on an issue or task was held by its assignee, who is working on it now; its content is their reason.
`issue_fixed`	An issue you created or are assigned is fixed: its done channel holds a frontier with all its linked work, and its plan is done.
`issue_reopened`	An issue you created or are assigned that was fixed is open again: its done channel moved to a frontier without its linked work (a rollback, decision 304).

Cardinality: 20.