train 23: 0.6.7 wave 1 — edit-check pairing, map data sections, fresh whereis/not-found answers

.coderabbit.yaml

@@ -5,6 +5,7 @@
 #   - No re-review on every push: each fix commit used to start a new pass over a new diff.
 #   - No automatic reply inside review threads: every in-thread answer used to wake another pass.
 #   - Vendored parsers and generated/pinned files are excluded; a review of them cannot change them.
+#   - No docstring-coverage pre-merge check: the house style documents contracts where they bite, not every symbol.
 # CodeRabbit reads this file from the PR's head branch, so a fork PR picks it up once it merges main.
 reviews:
   profile: chill                     # the default; "quiet" is the lever if noise persists
@@ -31,5 +32,8 @@ reviews:
         labelled a floor; a zero means none found. Flag silent zeros, undisclosed truncation, and gate arms
         that cannot fail.
   sequence_diagrams: false
+  pre_merge_checks:
+    docstrings:
+      mode: "off"                    # quoted: a bare off is a YAML 1.1 boolean, and the schema wants the string
 chat:
   auto_reply: false                  # thread replies no longer wake it

.github/pargates-shard-weights.json

@@ -135,6 +135,7 @@
 "duprowcheck.sh": 1.5,
 "dynmapsimdcheck.sh": 36.4,
 "editcheckcheck.sh": 17.8,
+"editcheckdeclcheck.sh": 46.2,
 "editchecknotecheck.sh": 5.1,
 "edithandlehintcheck.sh": 3.0,
 "editpayloadbinarycheck.sh": 2.0,
@@ -285,6 +286,7 @@
 "luacheck.sh": 3.5,
 "macroedgecheck.sh": 3.6,
 "manifestcheck.sh": 62.9,
+"mapdatasectioncheck.sh": 55.0,
 "mapdiffcheck.sh": 3.3,
 "matchcapturecheck.sh": 11.8,
 "matchgrammarcheck.sh": 0.6,

.ripwire_quality_acks

@@ -1456,6 +1456,7 @@ ack short-horizon-churn e8abfc6e8faace3b 5 cid=ba58d27ecdba1f2f OPTREMARKS F3 (d
 ack short-horizon-churn e98afe9f7356dca7 116 cid=9ff08b0551bdf16e macro-vocabulary rename (VERIFY/DEGRADED_PATH_ALERT family -> ASSUME/EXPECTS/ENSURES/DASSERT/UNREACHABLE/VALIDATE/DISCLOSE): identifier-only churn across 179 files, no logic change (rename_selfcheck.py, --check idempotent; ripwire --no-cache byte-identical old binary vs new binary on 3 trees)
 ack short-horizon-churn e9db97026e7265d2 145 cid=5e8fa13c43d29808 macro-vocabulary rename (VERIFY/DEGRADED_PATH_ALERT family -> ASSUME/EXPECTS/ENSURES/DASSERT/UNREACHABLE/VALIDATE/DISCLOSE): identifier-only churn across 179 files, no logic change (rename_selfcheck.py, --check idempotent; ripwire --no-cache byte-identical old binary vs new binary on 3 trees)
 ack short-horizon-churn ea9e556ae2c5b78f 3 cid=8f4414705d24d6f7 by=src/* member-variable round (card A3), side-table rule: symbols this round created (collectFieldUseSites, FieldUseAnswer, memberOwnerRefusal, declaredFieldSet, isInstanceFieldSite, dropFieldDefinitionSites, fieldCaptureKept) and touched twice within it while fields moved from ing.symbols to the IngestResult::fields side table under the orchestrator's rule; collectFacts/buildDefSpanIndex each carry ONE deliberate edit | prior: member-variable round (card A3): kUsesLegendOpen gains the one-sentence pointer to the member form, buildDefSpanIndex zero-widths field spans so containment attribution is byte-identical, kParserVer 74->75 for the new SymKind::Field + member use-site capture — each a single deliberate edit on a symbol other rounds touched recently
+ack short-horizon-churn eac088e77e30bd57 11 cid=4b0efd60def2f3b3 now=11 was=0 facet=self p=src/editcheck.h:281 review fix round (M2/M3): editCheckGroups is edited again on this branch to stop offering declaration-only handles and to verify only offered spellings; the churn is the review loop itself
 ack short-horizon-churn ec2848a4801493a2 153 cid=e95af915562f1c12 every short-horizon-churn row in this delta names a symbol this lane wrote or rewrote under review (the two compact-legend tables, the four map legends, MapAnnotations, serialize/writeRecentRows, pagingDisclosure, the cli.h guards, scopedRecentPage, refuseInertMainModifiers). The kind measures 2+ committed in-window rewrites of the same lines, which is what a reviewed lane does to its own code: round 1 added the block, round 2 answered CodeRabbit, round 3 answered the Fable review (the paging half, the stub vocabulary, the derived preemption, the crawl check). The churn here is the review cycle, not an unstable design, and it decays out of the window on its own. | prior: L7 lint-catalog: short-horizon-churn=self is ambient repo-wide churn on cli.h/main.cpp/didyoumean.h (49-92 commits/14d, unrelated lanes) inherited by any edit to these hot, central dispatch symbols, not fixable by reshaping this change; runLint/printUsage complexity+verbosity residual is the minimum new dispatch glue (4 extracted helper calls + 3 new flags' --help text) after extracting emitLintCatalog/resolveLintSelection/computeLintApplicability/printLintRuleTallyRow out of runLint, which cut the original complexity delta from +121 to +16
 ack short-horizon-churn ec9ec1cc3c01feb4 113 cid=691a45e7025a3510 round 3 test-script iteration: pymodulealiascheck.sh helper functions touched across three consecutive review-response rounds — expected churn from addressing review feedback quickly, not a structural defect
 ack short-horizon-churn ed0cbdfe7fa72e8c 154 cid=f42bf8683228ffff C1 F-06/F-07/F-10 (the listing-paging round): three listing verbs learn to disclose and page their row listings, and every gating row is that one change. api-surface 14 = ONE trailing DEFAULTED parameter each (an int pageOffset, an McpPageArgs window, a SituPageArgs, or the next= invocation a header now carries) on the emitters that must be TOLD their window — writeFlags/writeGate, writeCappedRows/writeCappedList/writeFlip/writeFlipHeader/writeFlipLights, computeFlip, nearestGateNames (which gains its cap and its TOTAL, the disclosure itself), situShowingNote/writeSituation, and the three MCP twins flagsText/flipText/situationDiffJson; additive by construction, every pre-existing call site compiles unchanged, and the alternative — a second capped emitter per verb — is the drift this repo removes rather than adds, because two emitters that disagree about a window can drop the row that IS the answer. verbosity 3 = kDocDriftLegend +20 lines and writeDocDriftPage +10 are the in-band vocabulary a reader needs to read shown_failed=/failed_capped=/failed_total= where they meet it (the rationale and the next= scan were already hoisted OUT of the body into their own function and comment, which took the complexity row to zero and the LOC row from +48 to +10); dispatchMcpLine +12 is two pagedResult wrappers on a pre-existing 1376-line dispatcher this lane adds to rather than creates. complexity 1 = the same dispatcher, +9 on a base of 518. duplication 1 = flagsText | flipText at 110 tokens, down from 131 after the shared mcpRowCap fold; the residual is getIndex + compute + captureXml, the shape EVERY index-backed MCP twin in this file has, and merging two verbs that return different results behind one entry point would be worse code than the clone. short-horizon-churn 19 = this lane's own footprint across cli.h/docdrift.h/darkflags.h/flipimpact.h/situ.h/mcp*, plus cli.h symbols three other lanes touched the same day; none foreign, none thrash.