feat(spec): add the map visualization config block to ListViewSchema by os-steve · Pull Request #9370 · objectstack-ai/objectstack

os-steve · 2026-08-17T17:17:18Z

Cross-repo transfer of objectui#5001 (spec-side by that card's ruling): ListViewSchema is strict and declared seven per-visualization config blocks but no map block, so a type: 'map' list view could not declare its field mapping or camera at all. The showcase task map fell back to the renderer's titleField default name — an object with only title — so every marker title rendered undefined.

What landed

ListMapConfigSchema (packages/spec/src/ui/view.zod.ts) — the eighth visualization block, registered as map on ListViewSchema beside the seven siblings. Key set anchored in two measurements, both quoted in the schema's JSDoc:
- objectui plugin-map's actual read surface: getMapConfig in ObjectMap.tsx validates schema.map against a local zod schema with exactly latitudeField / longitudeField / locationField / titleField / descriptionField / zoom / center, each with a live read in the renderer (coordinate extraction, marker title/description, camera init); the same seven keys are the documented surface in content/docs/plugins/plugin-map.mdx. No key without a live read was admitted.
- Sibling-block precedent for shape and refusal behaviour: strictObject with surface name + VIEW_HISTORY, .describe() per key, edit-distance prescription on unknown keys.
Strict, not passthrough — gantt/tree passthrough exists because those renderers add knobs ahead of the spec; the map renderer's read set is itself closed (it validates schema.map and drops extras), so passthrough here would silently strip nothing-reads-this keys. A misspelling is now a loud parse error.
No defaults on zoom / center, deliberately — objectui#5000 ruled "declared camera wins, no declaration means fit to the queried records"; a spec-side default would read as a declared camera and defeat the fit. Consequently the alias is isomorphic and pinned (Iso851, count 837 to 838 with receipt) in type-alias-convention.pin.test.ts.
Naming: not MapConfigSchema — the automation map flow-node config (automation/builtin-node-config.zod.ts) already exports that name; same collision, same resolution as ListChartConfigSchema vs chart.zod.ts's ChartConfigSchema. check:dual-source-exports is why this matters.
Tests (view.test.ts): accept cases (full seven-key surface, the exact showcase shape, empty config with no defaults applied), strict refusal asserting prescription substance (surface name + offending key echoed + titleField suggestion + verbatim history sentence, both standalone and nested inside ListViewSchema), and value-level refusals (zoom outside 1-20, center arity/type).
Liveness ledger (liveness/view.json + README row): map recorded planned, deliberately not live — the component-level reader exists (ObjectMap.tsx reads schema.map) but objectui ListView.tsx case 'map' forwards only schema.options?.map, never the view-level block, so authoring the key changes nothing at runtime until the pre-registered objectui consumer card lands the forwarding (measured against the objectui checkout current today). VIEW_BINDING_BLOCKS in functional-completeness.ts was deliberately NOT extended — it is Tier-A verify-then-enforce (timeline/tree are likewise excluded).
Showcase (examples/app-showcase/src/ui/views/task.view.ts): pure metadata addition demonstrating the block — map: { titleField: 'title', locationField: 'location' } on the map view, plus the now-stale "map needs a spec MapConfigSchema" comment corrected. allowedVisualizations untouched (switcher wiring is the objectui follow-up).
Generated artifacts regenerated via check:generated --fix: api-surface/ui.json, authorable-surface/ui.json, export-origins/ui.json, json-schema.manifest/ui.json, content/docs/references/**, strictness-ledger counts, liveness state-counts.
Changeset: @objectstack/spec minor (accepted-set expansion; not breaking, so no ADR-0087 marker required — check:adr-0087-registration green).

Verification (all at `dd2cb8d1d`)

pnpm --filter @objectstack/spec test — 408 files / 10880 tests passed (re-run post-commit at this head).
pnpm --filter @objectstack/spec typecheck, check:generated (all 13 current), check:liveness — green.
dispatch-gates re-derived from the actual diff; every named family run locally and green: cross-package-test-inputs, doc-authoring, doc-formula-expressions, docs-audit-scope, docs-redirects, empty-state, merge-driver, quick-reference-counts, role-word, spec-parsed-alias, strictness-ledger, type-source-resolution, variant-docs, dev-prereqs, affected-docs n/a via lint families, nul-bytes, adr-0087-registration, query-options-erasure, type-check-coverage, type-check-debt (workspace built), engine-double-contract, where-matcher.
Showcase: pnpm --filter @objectstack/example-showcase validate && typecheck — green (pre-existing unrelated warnings only).
Reverse verification (from the committed state): restoring origin/main's view.zod.ts turns exactly the 8 new tests red (missing export + map refused on ListViewSchema); restoring the branch file returns them green. Direction observed: red, as predicted.

Out of scope

The objectui consumer wiring (ListView forwarding view.map to plugin-map, switcher inclusion) is the pre-registered follow-up card the PM files on landing — objectui#5001 remains closed as transferred; #9340 remains the tracking card until merge.

Generated by Claude Code

…9340) The eighth per-visualization block, isomorphic to the seven ruled siblings. ListMapConfigSchema declares the map renderer's documented read surface (latitudeField/longitudeField/locationField/titleField/descriptionField/ zoom/center), strict, no defaults (declared camera wins; no declaration => renderer fits the queried records). Showcase task map view now declares titleField: 'title' + locationField: 'location'. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fs18A2DdXLVN2h8PaaFBcP

github-actions · 2026-08-17T19:20:04Z

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/spec, touching 3 documentable anchor(s).

⛔ 1 release-owned page(s) name something this change touched. These are read-only:

content/docs/releases/v17.mdx (via ListViewSchema (symbol))

content/docs/releases/ is RELEASE-OWNED (AGENTS.md "Documentation Guardrails"): release
notes are written centrally at release time, and a code PR that edits them is the exact PR
that guardrail exists to stop. They are still audited — read-only. If one of them is actually
wrong, file an issue or open a dedicated docs-only PR; do not edit it here.

What this run could not see

7 changed file(s) yielded no anchor (packages/spec/api-surface/ui.json, packages/spec/authorable-surface/ui.json, packages/spec/export-origins/ui.json, …) — pages documenting those are invisible to this run

Coarse fallback — 113 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json origin/main → packageMentionDocs.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs origin/main → pass the list as args.docs.

…dvisory, loudly The `Flag docs affected by code changes` job died four consecutive times on PR #9370 (2026-08-17, 17:17Z-18:24Z) with a 503 from `/repos/.../issues/9370/comments`. actions/github-script routes any throw from the inline script to `main().catch(handleError)` -> `core.setFailed(...)`, so a degraded GitHub API turned an advisory-only check red and cost four re-runs that no local change could have fixed. Delivery of the advisory comment now retries a bounded, narrow transient class (5xx, 429, 403 carrying a secondary-rate-limit signature, and network-level codes) and, once the retries are spent, degrades VISIBLY instead of failing: a warning annotation plus a job summary that names the failed call, states that the run's verdict is NOT on the pull request, warns that any advisory comment shown there is from an earlier push, and reproduces the verdict it did compute. The tolerance is scoped to delivery only. A malformed `affected.json`, a 422 over-long body, a plain 403 permission denial and any non-HTTP error still fail the job — swallowing those would let "could not tell" render as "no drift", which is the same defect wearing the opposite mask. Fixes #9373 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XqDQYVU5smx29ts9pAErja

…dvisory, loudly (objectstack-ai#9423) The `Flag docs affected by code changes` job died four consecutive times on PR objectstack-ai#9370 (2026-08-17, 17:17Z-18:24Z) with a 503 from `/repos/.../issues/9370/comments`. actions/github-script routes any throw from the inline script to `main().catch(handleError)` -> `core.setFailed(...)`, so a degraded GitHub API turned an advisory-only check red and cost four re-runs that no local change could have fixed. Delivery of the advisory comment now retries a bounded, narrow transient class (5xx, 429, 403 carrying a secondary-rate-limit signature, and network-level codes) and, once the retries are spent, degrades VISIBLY instead of failing: a warning annotation plus a job summary that names the failed call, states that the run's verdict is NOT on the pull request, warns that any advisory comment shown there is from an earlier push, and reproduces the verdict it did compute. The tolerance is scoped to delivery only. A malformed `affected.json`, a 422 over-long body, a plain 403 permission denial and any non-HTTP error still fail the job — swallowing those would let "could not tell" render as "no drift", which is the same defect wearing the opposite mask. Fixes objectstack-ai#9373 Claude-Session: https://claude.ai/code/session_01XqDQYVU5smx29ts9pAErja Co-authored-by: claude <noreply@anthropic.com>

…rsession (objectstack-ai#18859) Fixes objectstack-ai#18828 Clause-②: no The claim protocol forbids a second `Claim:` — the rule is this file's own, in the objectstack-ai#17366 docblock at `scripts/pm/check-clause2-carriers.mjs:378` — and until this PR nothing READ it. A thread that carried the forbidden second line was RANKED, not refused: the governing-claim selector took the newest live claim that parses a branch and printed the loser as `rejected: 1 … a SUPERSEDED claim`, clean and green at exit 0, in the register reserved for a transition the protocol DESIGNED. A writer-side prohibition with no enforcing reader. `claimRepeats` and the C8 row are that reader. ⚠️ **This is a RESUMED delivery.** Three commits were already on this branch from a run whose container was killed in its final-gates phase. Nothing it wrote was rewritten and nothing was redone — every item of the dispatch contract was re-verified against the tree, and all three readings were re-taken at the current tip and are dated below. The verified/fixed ledger is the first section. ## What was VERIFIED and what was FIXED Every contract item was found already correct and is left **byte-unchanged**. No code fix was needed; the only commit this run adds is a merge of `origin/main` (the derivation was answering about a stale tree — see Gates). | contract item | finding | |:---|:---| | the reading is a VERDICT at `EXIT_PAIR_ADVERSE` (4), never a NOTE at 0 | **verified** — `C8` is pushed in `pairRows` (:4430); `pairNotes` does not carry it, pinned | | `claimCarrierSelection` stays a pure function of the rows it is handed | **verified** — byte-identical to `origin/main` (sha256 of the whole function `40f59ba86082c358` at both revs) | | `CLAIM_COMMENT_MARKER` unwidened | **verified** — it is *imported* from `check-half-states.mjs` and read through `markerMatches`; that file is not in this diff at all | | `CLAIM_SELECTION_RULE` and the governing-claim choice unchanged | **verified** — byte-identical across revs; every hunk but two is a pure insertion | | SUPERSEDED / RETRACTED wordings byte-unchanged where they still apply | **verified** — no hunk touches them; the fixture control below prints the SUPERSEDED sentence identically at both revs | | every pin (a)–(i) present, each with a non-vacuity control | **verified** — 52 `t(...)` cases in the battery block; the ablation shows all nine directions carried | | battery registered in the roster with its case count | **verified** — :792, pinned at 52, and the block declares exactly 52 | | `SELF_TEST_BATTERY_FLOOR` raised by exactly one | **verified** — 31 → 32 (:806) | | the live census extended for this shape, population named | **verified** — the five measured instances replayed from their real rows, with `objectstack-ai#18559` as the sanctioned-shape control | `rowAuthor`, `laterOnThread` and `claimRetractions` are byte-identical across the two revs as well. ## The before-reading — the fixture control through the exported reader The same two rows (one author, two claims each parsing a branch, no retraction between) through the same exported `claimCarrierSelection` / `pairInputRecord` / `pairRows`, at `origin/main` `88aa326deb` and at this branch: | | `origin/main` `88aa326deb` | this branch | |:---|:---|:---| | `claims` / `live` / `pool` / `rejected` | 2 / 2 / 1 / 1 | 2 / 2 / 1 / 1 — **unmoved** | | governing claim | `7100000002` | `7100000002` — **unmoved** | | `rejected[0].reason` | `a SUPERSEDED claim — it is not the newest LIVE claim that parses a branch …` | byte-identical | | `claimRepeats` exported | **no — the reader does not exist at that rev** | yes | | `claim.repeat` in the record | absent | `1 author(s) holding more than one LIVE claim comment …` | | `pairRows` codes | *(none)* | `C8` | | **verdict** | **exit 0 — nothing refused** | **exit 4 (`EXIT_PAIR_ADVERSE`)** | That is the defect and the repair in one table: the selector does not move, and the thread stops reading green. ## The live count — the five cards and the control, re-taken 2026-09-18T00:44:39Z Read per card through the gate's own `markerMatches` / `CLAIM_COMMENT_MARKER` and `claimRetractions`, not by eye. ⚠️ Those threads may have left this state since. | card | `Claim:` comments (author) | `Clause-②-correction:` | `Release:` | the OLD reading | C8 today | card state | open delivering PR | |:---|:---|:---|:---|:---|:---|:---|:---| | objectstack-ai#18540 | 2 — `os-support-ai` (5719079496, 5720020876) | 0 | 0 | SUPERSEDED, exit 0 | **named, exit 4** | closed | **none** | | objectstack-ai#18677 | 2 — `os-support-ai` (5720104138, 5720190458) | 0 | 0 | SUPERSEDED, exit 0 | **named, exit 4** | closed | **none** | | objectstack-ai#18748 | 2 — `os-support-ai` (5720212595, 5720888122) | 0 | 0 | SUPERSEDED, exit 0 | **named, exit 4** | closed | **none** | | objectstack-ai#18651 | 2 — `os-support-ai` (5721424769, 5721997887) | 0 | 0 | SUPERSEDED, exit 0 | **named, exit 4** | closed | **none** | | objectstack-ai#18778 | 2 — `os-support-ai` (5721425530, 5722028692) | 0 | 0 | SUPERSEDED, exit 0 | **named, exit 4** | closed | **none** | | objectstack-ai#18559 *(control)* | 1 — `os-support-ai` (5721425131) | **1** (5721779100) | 0 | *(nothing rejected)* | silent | closed | **none** | The card's table reproduces exactly. All six cards are now **closed**, and the open-PR column is empty for every one of them: the only open PR cross-referenced from any of these threads is objectstack-ai#18857, whose body's closing keyword names `objectstack-ai#18780` instead — `prDeliversCard` answers `false` for all six and `true` for `objectstack-ai#18780` (the control leg), so it is not paired with any of them. ⛔ The repair of the five is `os-support-ai`'s; this PR only names them, and posts nothing on those cards. ## The escalation probe — the triage's p1 condition, MEASURED The triage marked this p2 because all five instances were one seat self-superseding, and named the escalation condition it had not run: a second `Claim:` from a DIFFERENT session on one card, which would be a silent ownership transfer printed green. I ran it. **Population, read 2026-09-18T00:47:37Z → 00:48:42Z:** every open card on both boards this gate reads — **529 open cards in `objectstack-ai/objectstack`, 413 in `objectstack-ai/objectui` (942 total)**, of which **880** carry at least one comment and were read; **163** carry at least one claim comment. 9 comment lists sit at the 100-comment cap and are UNJUDGED past it, exactly as objectstack-ai#18683 prescribes. 0 parse failures. **The answer is not 0 — it is 12.** Twelve open cards carry LIVE `Claim:` comments from two or more DIFFERENT authors with no retraction between them: | repo | card | authors holding live claims | |:---|:---|:---| | objectstack | `objectstack-ai#13503` | `claude[bot]` + `baozhoutao` | | objectstack | `#14026` | `hotlong` + `claude[bot]` | | objectstack | `objectstack-ai#15811` | `os-bill` + `os-litant` | | objectstack | `objectstack-ai#17852` | `os-warren` + `os-litant` | | objectui | `objectstack-ai#4730` | `yinlianghui` + `os-sales` | | objectui | `objectstack-ai#7070` | `os-warren` + `claude[bot]` | | objectui | `objectstack-ai#7696` | `os-justin` + `os-tesla` | | objectui | `objectstack-ai#7804` | `os-tesla` + `os-sam` + `os-justin` | | objectui | `objectstack-ai#7848` | `claude[bot]` + `baozhoutao` | | objectui | `objectstack-ai#7924` | `os-warren` + `os-sales` | | objectui | `objectstack-ai#8115` | `claude[bot]` + `yinlianghui` | | objectui | `objectstack-ai#9370` | `os-tesla` + `os-justin` | ⚠️ **This PR is deliberately SILENT on all twelve** — and that silence is pinned, per direction (b). Refusing an ownership transfer between sessions is not this card's to do: it is a different state, it would need its own remedy sentence, and a row that answered both would make one sentence out of two states. This is reported here and in the dispatch report so the seat can file it; ⛔ it is not folded in. ## Who the new exit 4 meets before it lands The seat needs this before landing, so I swept it rather than assuming. Two facts: 1. **No CI job turns red.** `check:pm-clause2-carriers` — the only wiring, `.github/workflows/lint.yml:1140` — runs `--self-test` and nothing else. No workflow runs `--pair` or a sweep, so landing this changes no required context. The exit 4 appears only when a seat runs `--pair` or a sweep by hand. 2. **On the objectstack board: nobody.** Of 32 open PRs in objectstack, **none** delivers a card that would newly earn a C8. Twenty open cards across both boards would earn the row (report-only, listed in the dispatch report), but only one is reachable through an open PR, and it is in the sibling repo: **`objectstack-ai/objectui#9584`** (open, not draft; its closing keyword names `objectui#9499`), which delivers a card carrying two live claims by `os-try-charles` (5663366106 on 2026-09-14, 5690579598 on 2026-09-16). That pair answers exit 4 at its next `--pair`. `DEFAULT_SWEEP_REPO` is `objectstack-ai/objectstack`, so objectui is only ever read when passed explicitly. ⛔ Nothing was posted on objectstack-ai#9499, objectstack-ai#9584 or any of the twelve. ## The reading, and WHERE it is computed `claimRepeats` (:1898) is a **sibling pure reader beside `claimRetractions`, built on it** — the same map decides membership here and for governance, so the pool and this row cannot describe two different retractions. It names every author holding more than one LIVE claim comment, orders them by the file's one recency rule (`laterOnThread`, to ORDER the record, never to pick a winner), and resolves no state, no row and no exit code. `c8SecondClaimSameSeat` (:4380) renders the verdict; `pairRows` (:4430) pushes it as row `C8`; `pairInputRecord` adds `claim.repeat` (:5876, declared in `INPUT_RECORD_PAIR_FIELDS` at :5641) as the READING — one derivation feeding both, so the record and the verdict cannot disagree about how many claims a seat holds or which they are. **MEMBERSHIP first, and that is what makes the state repairable.** The state is read over LIVE claims only. A re-claim after a `Release:` is the protocol working and reads exactly as it did before. And a seat that already wrote a second claim has an act that clears the row: `Release:` what it holds, then one fresh `Claim:`. A rule written over the writing *moment* instead ("no retraction strictly BETWEEN the two lines") would have been unrepairable by construction — nothing un-writes a comment — so the row would have been a permanent red with a remedy nobody could execute. ### The four axes - **实际业务需求** — measured, not assumed. Five live instances on the objectstack board at filing, re-confirmed today, every one of them read green before this row; plus 20 open cards across both boards that carry the state now. The first signal in five occurrences came from a dev reading a docblock, not from any instrument. This is a real shape occurring repeatedly, not a speculative surface. - **项目长远合理性** — contract-first, and no workaround. The rule already existed in writing at :378; this adds the reader that enforces it, in the same file, over the same thread, through the same membership derivation governance uses. No new exit code was minted, no second selector, no second reader of the marker. The prohibition and its reader now live one screen apart. - **防 AI 写代码犯错** — this is the axis that decides the exit. A second `Claim:` re-enters the pool as the newest claim and becomes what every downstream reader is handed — the property the correction key was deliberately designed NOT to have. Rendering that as a NOTE at exit 0 is precisely the tolerant-consumer shape this repo refuses: an adverse fact printed green is how a batch of identical mistakes stays invisible. Declaring the prohibition and not enforcing it is the "声明而未兑现" gap; the repair is to enforce it loudly, at `EXIT_PAIR_ADVERSE`. The row also ⛔ never prescribes WHICH repair — choosing between a correction and a release would be choosing whether the card is being re-taken, which is the seat's judgement, so it names both and writes nothing. - **创业阶段不扩散需求** — the surface added is one file, one pure reader, one row, one record field. It refuses exactly one shape the protocol already forbade in writing and re-blocks no legal workflow: a card claimed once reads as it always did, a re-claim after a `Release:` reads as it always did, a `Clause-②-correction:` is not a claim and never was. The cross-seat question, which is a genuine second capability, is explicitly NOT taken here. ## The pins — per direction, each with a non-vacuity control | | direction | reading | |:---|:---|:---| | (a) | same author, two claims, no retraction | **named, exit 4**; the row carries both ids, the author and both repairs | | (b) | DIFFERENT authors | supersession as today, exit 0 — ⛔ not this state | | (c) | same author after a `Release:` **or** the id-naming retraction | RETRACTED as today, exit 0; the `⛔ NOT superseded` wording byte-unchanged | | (d) | a `Clause-②-correction:` as the later row | silent; the objectstack-ai#17366 exit still reads the declaration off it | | (e) | a DECORATED second claim (bold, backticked) | counted through `markerMatches` exactly as a bare one; the raw constant refuses both, so the counting is the sibling's ONE reading | | (f) | a second claim whose `Branch:` parses to zero branches | still named — the prohibition is on the WRITING, not the parse | | (g) | three claims by one seat | **ONE** refusal naming all three, not two | | (h) | an unattributable row (`rowAuthor` null) | fail closed, as `claimRetractions` does — and `null` never groups with `null` | | (i) | a later same-author comment that QUOTES or DISCUSSES the word | silent — the marker is read at line start | Direction (i) has a control in the wild on this very card: the triage comment 5722477144 contains the word `Claim:` mid-line, and `markerMatches` refuses it — card objectstack-ai#18828 reads one claim comment, so `--pair` on this PR is silent. **Roster line** (:792): `'objectstack-ai#18828: a SECOND \`Claim:\` by ONE seat — the writer-side prohibition, finally READ': 52` — and the battery block declares exactly 52 `t(...)` cases. **Floor** (:806): `SELF_TEST_BATTERY_FLOOR` **31 → 32**, raised by exactly one. ## The ablation Run from the **committed** fix, twice, each leg proving its mutation landed on disk before the reading was taken and proving its restore by an empty `git diff HEAD` and by blob hash — never by an editing command's exit code. `HEAD` blob `3a270ef2eb5f33780e04e4732714f8e88d74a017`. | leg | mutation | mutated blob | result | |:---|:---|:---|:---| | baseline | none | `3a270ef2eb…` | **941 cases pass, exit 0** | | **A** — the repeat detection neutered (a group is never reported) | `72115d2796ead200f93aa855c8ba5820a83f5f8f` | | **23 of 941 failed**, exit 1 | | **B** — the SAME-AUTHOR check removed (the author no longer decides the grouping) | `40cfadd4f5740f34210675ceb998fb2977823769` | | **3 of 941 failed**, exit 1 | Both legs restored: `git diff HEAD` empty, blob back to `3a270ef2eb…`. **Total case count is 941 in all three runs** — the rest of the self-test is byte-identical in its case count, and in both legs **0 of the failures fall outside the objectstack-ai#18828 battery**. Leg A is the interesting one, because it shows the per-direction controls doing their job. Five of the nine directions assert SILENCE and therefore *cannot* go red when the detection is removed — their non-vacuity controls go red instead. All nine directions are carried: - pin itself red: **(a) (e) (f) (g)** - carried by its control: **(b) (c) (d) (h) (i)** — "make those two authors ONE", "drop the retraction", "write that same correction as a SECOND `Claim:`", "give that same row a login", "move that same word to the OPENING of a line" Leg B is the narrower, sharper one: removing only the author test reds **3** cases, and pin (b) is among them. That is the pin which distinguishes this card from the cross-seat question — proof the author test is load-bearing and that (b) is not vacuous. **Self-test count: 889 before → 941 after** (+52, exactly the registered battery). The 889 was measured by running `--self-test` in a detached worktree at `origin/main` `88aa326deb`. ## Gates Derived from the worktree with `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` (no hand-fed path list). ⚠️ The first derivation printed **STALE TREE** — the branch was 2 commits behind `origin/main` and 8 files the derivation reads had changed — so `origin/main` was merged in first and the list re-derived on the merged tree at `7424cf3f44`; the `--repo` assertion holds against this checkout's `origin`. **34 derived, 34 run, all exit 0.** Each exit code captured redirect-then-`$?`, never across a pipe. ``` node scripts/check-adr-0087-registration.mjs --base origin/main :: exit 0 node scripts/check-adr-0087-registration.mjs --self-test :: exit 0 node scripts/check-changeset-no-major.mjs --base origin/main :: exit 0 node scripts/check-changeset-no-major.mjs --self-test :: exit 0 node scripts/check-ci-filter-parity.mjs :: exit 0 node scripts/check-closing-keyword-parity.mjs :: exit 0 node scripts/check-closing-keyword-parity.mjs --self-test :: exit 0 node scripts/check-comment-mask-corpus.mjs :: exit 0 node scripts/check-declaration-mirrors.mjs :: exit 0 node scripts/check-declaration-mirrors.mjs --self-test :: exit 0 node scripts/check-scripts-symbol-anchors.mjs :: exit 0 node scripts/check-scripts-symbol-anchors.mjs --self-test :: exit 0 node scripts/check-self-test-wired.mjs :: exit 0 node scripts/check-self-test-wired.mjs --self-test :: exit 0 node scripts/check-self-test-workflow-commands.mjs :: exit 0 node scripts/check-self-test-workflow-commands.mjs --self-test :: exit 0 node scripts/check-whole-set-label-write.mjs :: exit 0 node scripts/check-whole-set-label-write.mjs --self-test :: exit 0 node scripts/pm/bare-root-worklist.mjs --self-test :: exit 0 pnpm check:agent-test-spelling :: exit 0 pnpm check:bash32-floor :: exit 0 pnpm check:changeset-gate-self-tests :: exit 0 pnpm check:cli-command-ids :: exit 0 pnpm check:cross-package-test-inputs :: exit 0 pnpm check:driver-memory-census :: exit 0 pnpm check:entry-guard :: exit 0 pnpm check:nul-bytes :: exit 0 pnpm check:parse-guard :: exit 0 pnpm check:pm-clause2-carriers :: exit 0 pnpm check:pm-dispatch-gates :: exit 0 pnpm check:pnpm-filter-targets :: exit 0 pnpm check:ratchet-remedy-authority :: exit 0 pnpm check:refd-timer-probe :: exit 0 pnpm check:watch-hint-literal :: exit 0 ``` Reconciled with `--ran`, exit codes included: **34 derived, 34 run, 0 NOT-MEASURED, 0 UNRUN** — "a DERIVED zero — all 34 recorded an exit code and none of them is 3". Repo-wide `pnpm lint` (`eslint . --no-inline-config`): **exit 0**. The heavy run took a ticket through `scripts/pm/os-verify-lock.sh` (slot `issue-18828-dev`), queued behind the seat's own `dispatch-gates.mjs --self-test`. `node scripts/pm/check-clause2-carriers.mjs --pair` on this PR is reported in the dispatch report — this card carries one claim comment, so the row is silent on it. `skip-changeset`: `scripts/pm/**` publishes nothing from any released package — the whole diff is one non-published script. --- _Generated by [Claude Code](https://claude.ai/code/session_01Gqi43smmqjJ5sUrhfoPeKu)_ --------- Co-authored-by: Claude <noreply@anthropic.com>

github-actions Bot added size/m documentation Improvements or additions to documentation tests protocol:ui tooling labels Aug 17, 2026

os-steve marked this pull request as ready for review August 17, 2026 19:53

os-steve added this pull request to the merge queue Aug 17, 2026

Merged via the queue into main with commit 90c5285 Aug 17, 2026
27 of 30 checks passed

os-steve deleted the claude/issue-9340-listview-map-config branch August 17, 2026 20:14

This was referenced Aug 18, 2026

merge-queue-triage.yml has the same untolerated comment-post as #9373 — and here the lost comment IS the flake evidence #9424

Closed

feat(spec): declare viewMode on GanttConfigSchema (#9463) #9489

Merged

os-elon-musk mentioned this pull request Sep 15, 2026

[PM seat] director(项目总监) — 🟢 os-zhuang · 第 37 场 session_01LqNgdPZB2Jnr5HpGbaqLeB · 开轮 2026-10-11T22:41Z · 第 35–36 场台账在评论 #12708

Open

Navigation Menu

Repository navigation

feat(spec): add the map visualization config block to ListViewSchema - #9370

feat(spec): add the map visualization config block to ListViewSchema#9370
os-steve merged 1 commit into
mainfrom
claude/issue-9340-listview-map-config

os-steve commented Aug 17, 2026

Uh oh!

github-actions Bot commented Aug 17, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

os-steve commented Aug 17, 2026

What landed

Verification (all at dd2cb8d1d)

Out of scope

Uh oh!

github-actions Bot commented Aug 17, 2026

📓 Docs Drift Check

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Verification (all at `dd2cb8d1d`)