|
1628 | 1628 | {"id":"int-8d569975ed3b2d421b704138e52728ac","kind":"field_change","created_at":"2026-07-19T03:13:04.335528Z","actor":"Hellblazer","issue_id":"nexus-jxizy.7","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"FORCE-CLOSE RATIONALE for the .6 dep: the .7<-.6 edge encoded gate-obs-1 ACTIVATION ordering (serving flip only inside .6's freeze window), not unfinished .7 work — satisfied structurally: the flip ships in the cohort engine whose DEPLOYMENT is the .6-tracked cutover choreography (freeze -> boot -> rekey), so activation-after-ETL holds by construction. CODE COMPLETE + REVIEWED: Chash inversion (9234abf4+cb8c366f+da2c4f86) byte[32]-backed, fromHex strictly 64-hex with dual-remedy legacy hint, fromSha256Hex=identity, requireLength32 DELETED (one strict tier), ChashHex jOOQ converter seam (recorded interpretation: boundary-typed, seam-converted, RawSqlGateTest-guarded), PgVectorServingContractTest REWRITTEN proving 32-char non-hex ids REJECTED, ChashTypeTest polarity-replaced. Engine suite 1320/0/0. Review marker T1 366c9c36."}} |
1629 | 1629 | {"id":"int-cb3339b221dfd998aac1505d5724cb79","kind":"field_change","created_at":"2026-07-19T03:13:05.699764Z","actor":"Hellblazer","issue_id":"nexus-jxizy.8","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"FORCE-CLOSE RATIONALE: dep chain rode .7's activation edge (see .7 close). CODE COMPLETE + REVIEWED: every handler parses chash through the type at bind time -> uniform 400 with offending length BEFORE any transaction (fk-001 pattern); mute mid-transaction CHECK class gone; dual-remedy hint on legacy width. Pinned by the handler test family (full-64-accepted + legacy-32-rejected pairs). Review marker T1 366c9c36."}} |
1630 | 1630 | {"id":"int-6f929482908b2caf130d3c4e1a58cd54","kind":"field_change","created_at":"2026-07-19T03:13:07.046156Z","actor":"Hellblazer","issue_id":"nexus-jxizy.9","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"FORCE-CLOSE RATIONALE: the .9<-.6 edge was the alias-resolution dependency — the alias resolver EXISTS and is proven (engine resolveLegacyRef + client alias route, RekeyOpsIntegrationTest + test_chash_citation_resolution); what remains of .6 is the PRODUCTION rekey run, which populates alias FACTS but does not change the resolver contract this bead pins. Grammar truthful (64 == storage); 64-hex citations resolve at 256 bits; legacy 32-hex references resolve via the alias route end-to-end (critic HIGH fix 6c72ad55); unmapped legacy = dangling-None. Review marker T1 366c9c36."}} |
| 1631 | +{"id":"int-1019c0720516506ce95454dea402722b","kind":"field_change","created_at":"2026-07-20T13:52:05.086193Z","actor":"Hellblazer","issue_id":"nexus-339xv","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"SHIPPED 8573c15b. In-transaction ANALYZE of chash_alias in RekeyOps + StagingPromoteOps via ChashSqlIdioms.refreshAliasStats; GRANT MAINTAIN in grants-nexus-svc (runAlways, self-heals next boot); alias_stats_refreshed rides the envelope and the client rung surfaces a false. KEY FINDING: the bare statement is a SILENT no-op — Postgres WARNs+SKIPs for a non-owner rather than erroring (verified empirically: statement alone produced ZERO stats and threw nothing), so tests assert the RESULTING STATISTICS, never the statement. Version guard is load-bearing: has_table_privilege(...,'MAINTAIN') RAISES on PG16 rather than returning false, which would abort the whole rekey. Cloud verified PG 17.10 so the fix is live there on the next engine tag. Full engine suite 1355/0/0 on the final tree. Mutation-verified both directions."}} |
| 1632 | +{"id":"int-ed4743cad80977a8ab1ca15af6651ce3","kind":"field_change","created_at":"2026-07-20T13:52:06.31082Z","actor":"Hellblazer","issue_id":"nexus-noa8d","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"SHIPPED 79d234ec + 9400a014. Gate-three/report-two: the three CONTENT octet CHECKs always VALIDATE; the two POINTER checks are skipped while pre-existing orphan debt exists, counts reported with a remediation pointer. Implemented as a CEILING measured within the run (debt before the rekey vs after) — growth raises, pre-existing is grandfathered — NOT a table exemption, per conexus's own correction that Hal caught. Ceiling is run-local by design: the only cross-run store is the completion record's detail field, which protocol.py declares observability-only and accepted lossy, and a load-bearing gate must not ride a lossy field. pointer_debt_fn rides the read-only diag choke point; None (managed/no creds) leaves all-five behaviour untouched. Red-first, mutation-verified (blanket exemption fails the ceiling test); upgrade-ladder suite 569 passed."}} |
| 1633 | +{"id":"int-883fe00ad881cad99d142b4753755f4a","kind":"field_change","created_at":"2026-07-20T14:22:55.350354Z","actor":"Hellblazer","issue_id":"nexus-kmd5b","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Closed"}} |
| 1634 | +{"id":"int-41ac5d2f24df5830a1b439f03b0df48a","kind":"field_change","created_at":"2026-07-20T16:24:38.183794Z","actor":"Hellblazer","issue_id":"nexus-b878d","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}} |
| 1635 | +{"id":"int-0bdba4c1c2193b0d09849eab52b73047","kind":"field_change","created_at":"2026-07-20T16:30:03.954804Z","actor":"Hellblazer","issue_id":"nexus-3h0u6","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}} |
| 1636 | +{"id":"int-206ba840457ec123e18502be7dbbfc01","kind":"field_change","created_at":"2026-07-20T16:38:22.76847Z","actor":"Hellblazer","issue_id":"nexus-xzop6","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}} |
| 1637 | +{"id":"int-6ab0294dee824356b5c7b81ddbbc5261","kind":"field_change","created_at":"2026-07-20T16:38:24.36679Z","actor":"Hellblazer","issue_id":"nexus-84tr4","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}} |
| 1638 | +{"id":"int-15dc5b11b9cb47bd7b765388d72ff609","kind":"field_change","created_at":"2026-07-20T16:38:25.53695Z","actor":"Hellblazer","issue_id":"nexus-sfgqi","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}} |
| 1639 | +{"id":"int-5fbd41ca19b13bf1f410f7c3407d8d4a","kind":"field_change","created_at":"2026-07-20T16:43:37.964777Z","actor":"Hellblazer","issue_id":"nexus-leunq","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Closed"}} |
| 1640 | +{"id":"int-9fb250e8aa217b49e04bd6aabe1dc7e4","kind":"field_change","created_at":"2026-07-20T18:01:35.956673Z","actor":"Hellblazer","issue_id":"nexus-ixl85","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"MEASURED, no code change (Hal's call, 2026-07-20).\n\nFull classification sweep on the real 15-collection legacy Chroma footprint: median 3.3 ms, per-collection 0.2 ms, 5 of 15 data-bearing so only 5 reach the dim probe. The bead framed this as the vgtff shape, but vgtff was 300 SECONDS and this is 3 MILLISECONDS.\n\nResolution (c) accept and bound, with (d) noted: the cost retires with RDR-155 P4b by construction when the footprint gate goes permanently False. Candidates (a) and (b) are explicitly NOT taken — both make detect() consult stored state and would contradict test_gap4_two_mechanisms.py::test_rung_convergence_is_re_derived_live_never_cached, trading a 3ms perf non-issue for the marker-file-as-authority correctness class.\n\nScope limit recorded on the bead comment: measured on a LOCAL PersistentClient leg. A cloud legacy leg makes each data-bearing collection's probe a network round trip (5 here, not 15); the larger N+1 network half was already fixed. Re-measure there before reopening on a cloud-leg report."}} |
| 1641 | +{"id":"int-7c0933e9dfe939419b40601fb0f22c13","kind":"field_change","created_at":"2026-07-20T21:48:32.638867Z","actor":"Hellblazer","issue_id":"nexus-q6830","extra":{"field":"status","new_value":"closed","old_value":"in_progress","reason":"Shipped as 5f967f65 on develop. Full suite 14184 passed / 0 failed.\n\nBoth halves of the bead's sketch are addressed, though the second differently than sketched: the error now reports whichever stream carried text (with an explicit sentinel when the subprocess was silent), and a structlog operator_dispatch_failed event at the choke point gives every one of the 17 call sites a record — rather than the per-call-site persist the bead originally imagined.\n\nDeliberately NOT claimed as nexus-1at5 parity. That branch writes a dedicated uncapped per-incident file and names its path in the exception; this writes a capped event into the shared 10MB x 5 rotating mcp.log with no pointer back. And durability is a property of the CALLING process's logging mode, not the choke point: the 15 mcp-mode sites get the file handler, the 2 taxonomy CLI sites get stderr only. Residuals tracked as nexus-ri56e (addressability, retention, CLI coverage — with the warning not to port _persist_timeout_log literally, since its no-cleanup design is only safe because timeouts are rare) and nexus-l1qpj (per-failure stderr volume in the taxonomy batches, untested).\n\nStacked review earned its keep four times across two rounds, none visible to a green suite: the nexus-1at5 overclaim, the mcp.log gap being systemic rather than nx_plan_audit-only (13 of 17 sites bare, 3 with no covered path), silent truncation of the log field (the same 'silence must read as silence' principle this diff designed into the exception, missing one field over), and a code comment left contradicting its own corrected commit message. Three independent enumerations of the call sites gave 12/17/17 — the first was an inherited partial list presented as traced, which is the exact sampling-as-inventory failure nexus-ou4tb is open over.\n\nRoot cause of the GH #1414 failure itself is untouched and remains open as nexus-g6vb4 (MCP host cannot self-detect staleness after an in-place uv tool upgrade; upgrade_finish.py:197 excludes pid == me by construction)."}} |
0 commit comments