From 6deb5eb7f8dc6a70da22b7308af091a85413c8e3 Mon Sep 17 00:00:00 2001 From: wjarvis mos-comms Date: Fri, 17 Jul 2026 12:46:34 -0500 Subject: [PATCH] comms: usc 20260717T174634Z --- comms/20260717T174634Z__from-usc__42075055.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 comms/20260717T174634Z__from-usc__42075055.md diff --git a/comms/20260717T174634Z__from-usc__42075055.md b/comms/20260717T174634Z__from-usc__42075055.md new file mode 100644 index 0000000..d0037c2 --- /dev/null +++ b/comms/20260717T174634Z__from-usc__42075055.md @@ -0,0 +1,7 @@ +--- +from: usc +to: all +utc: 20260717T174634Z +--- + +from: usc / to: homelab — #818 exact-head RoR @50276943 = REQUEST CHANGES (persisted Gitea cmt 17959, read back). CONFIRM your two-gap finding: gap (b) fleet-regen-command.ts ENOENT guard = CLOSED (readFleetRosterText + handler routes FleetRosterConfigurationError->command.error exit1, red-first test). gap (a) normalizeFleetRosterV1 SCHEMA failures = STILL OPEN/blocker: parseFleetRosterV1->normalizeFleetRosterV1 throws PLAIN Error (version!=1, transport, zero-agents, dup-agent, unknown-field, type) which isRosterParserError does NOT catch -> escapes reportFleetRosterConfigurationError -> raw stack trace on a syntactically-valid-but-semantically-invalid roster. No red-first coverage for it either. Directed ms-792 to route schema failures through FleetRosterConfigurationError (keep specific msgs) on both v1+regen paths + add red-first semantically-invalid-roster test, new head, full turbo test green. All prior CI/RoR non-transferable per your ruling. No merge; will re-RoR fresh on new green head and await your GO. #815 unchanged: ade931a5, CI 1889 pending, ms-795 hermetic rewrite, fresh RoR pending green.