Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
d3be5f0527
test(communication): close register row 102 — serialize the two gauge-moving classes so the subscribers.active baseline holds
324ba369d9
infra(docker)+test(siteeventlog): close register tripwires 79 + 93 — rig data to named volumes; pin site_events schema to the cap-model calibration
5936573e71
docs(register): close row 38 — OtOpcUa racing-clear test rebuilt on retry-exhaustion assertion cross-session (34829ea0, 837d8a17)
505f356916
merge(agent): whole-snapshot staleness guard — generalize row 101's definitions generation to one _storeWriteGeneration over both tables, bumped at BOTH ends of every actor-thread config mutation (dispatch + completion; ApplyDeployment/Disable/Delete advance actor state before the write, so completion-only left a window); stale sweep discarded whole (closes the proven backward-restart and delete-resurrection hazards), stale boot load re-dispatched with a capped fallback; CDC/reconciliation writes deliberately never bump — discovering them is the sweep's purpose
f02e116688
fix(siteruntime): extend the row-101 stale-snapshot guard to the instance-config half
45058d57a5
Merge feat/followup-closeout: feed-level snapshot_status truncation frame on StreamAlarms rolled out to all five clients, ShowTagValues gating all three dashboard seams, both-direction codegen Check 3, GroupToTag/UntaggedSessionVisibility settings rows, dashboard_tags on ApiKeysPage, wnwrap probe answers (@COUNT records-in-reply, re-raise GUID replacement, ack leg re-blocked)
f2a422b02f
docs(auth): canonical scope strings in the two remaining stale lists
a5f843cbfb
chore(plan): close the record — prior follow-ups annotated, closeout as-built noted
c3c603f169
docs(alarms): describe the real StreamAlarms open sequence, and close TST-16
a95e510015
chore(plan): Task 8 verification-green at 90331b6 — residuals recorded