wtclaude 76b2276d36 docs(events): Phase 2 as built - the runner ...

The docs half of Event System Phase 2. Pairs with `RunicGateway/website`
`feat/events-phase-2`.

EVENTS.md gains what the runner settled: the parked step (`running` with a NULL
lease), the two success-envelope members `await: 'human'` and `holdFor`, the
answer for a run whose concurrency key is held, `n` in §L's `retry(n)`, the rule
that all three `on_failure` dispositions write the step `failed`, and the health
transition on the first retry rather than the eventual failure.

EVENTS_PLAN.md marks Phase 2 complete and records the four org-lead decisions
and the three things the build settled on its own.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-09-02 06:32:15 -05:00

..

API_V2_PLAN.md

docs(website): one self-service surface — /auth/me/account

2026-08-29 00:49:40 -05:00

API_V2_SKELETON.md

docs(website): finalize the API plan — in-place router split, no /api/v2

2026-07-27 14:31:26 -05:00

api-route-inventory.json

docs(website): event triggers, audiences and the ceiling lattice (engagement Phase 2)

2026-08-29 06:40:48 -05:00

ARCHITECTURE.md

docs: hygiene sweep - the four places the docs describe a site that no longer exists

2026-08-19 18:04:41 -05:00

BACKEND_DESIGN.md

docs(events): Phase 1 as built — schema, CRUD and the core action registry

2026-09-01 23:28:26 -05:00

CLILOCS.md

docs(website): an operator runbook for extracting from your own UO client

2026-07-30 03:34:29 -05:00

ENGAGEMENT.md

docs(events): Phase 0 — the eleven decisions, and the two documents they reach into

2026-09-01 20:52:37 -05:00

EVENTS_PLAN.md

docs(events): Phase 2 as built - the runner

2026-09-02 06:32:15 -05:00

EVENTS.md

docs(events): Phase 2 as built - the runner

2026-09-02 06:32:15 -05:00

HERO_EDITOR.md

Hero Phase 4: moon/badge/image elements + resize + snap grid

2026-06-28 08:47:05 -05:00

MARKETPLACE.md

docs(link): the player-vendor marketplace (Protocol 3.0 §8)

2026-07-29 09:52:14 -05:00

MODERATION_APPEALS.md

docs(website): add moderation appeals + Discord reversal (Phase 6c/6d)

2026-07-19 03:34:26 +00:00

MODULE_API.md

docs(engagement): the two walk defects, fixed -- and what digest is

2026-09-01 14:31:00 -05:00

MODULE_SYSTEM.md

docs(modules): the module release version is derived, not declared

2026-08-19 13:01:50 -05:00

PROJECT_TREE.md

docs(tree): sync website/PROJECT_TREE.md from RunicGateway/website@6331b36 [skip ci]

2026-09-01 20:57:26 +00:00

SHARD_VISIBILITY.md

docs(modules): close Phase 4 — de-UO the backend reference, record the acceptance run

2026-08-12 09:16:29 -05:00

SPAWN_ATLAS.md

docs(modules): close Phase 4 — de-UO the backend reference, record the acceptance run

2026-08-12 09:16:29 -05:00

TEAMS.md

docs(website): the email channel and the Teams migration as built (engagement Phase 6)

2026-08-29 20:12:15 -05:00

test-plan.md

docs(website): add Discord bot test plan

2026-07-21 01:01:34 -05:00

THEMING_AND_NAV.md

docs(website): settle the nav interleave and the feature-provider seam

2026-08-10 23:42:21 -05:00

TRUSTED_DEVICES_MFA.md

docs(website): record trusted-device support on the SSO login paths

2026-07-28 01:01:49 -05:00

UOFIDDLER.md

docs(website): an operator runbook for extracting from your own UO client

2026-07-30 03:34:29 -05:00

UPGRADE_NOTES.md

docs(website): the engagement release note -- three things that arrive switched off

2026-09-01 08:35:38 -05:00

website-README.md

docs: the shard screen's real path, and the two keys a deploy cannot boot without

2026-08-24 11:24:41 -05:00

WIKI_UPGRADE.md

docs(website): record the PR 4 admin router split and the end of admin.routes.js

2026-07-27 20:02:49 -05:00