Repository navigation
[WIP] Fix incorrect links in docs/components - #146
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: huangyiirene <7665279+huangyiirene@users.noreply.github.com>
huangyiirene
marked this pull request as ready for review
January 22, 2026 06:26
Copilot stopped work on behalf of
huangyiirene due to an error
January 22, 2026 06:27
This was referenced Sep 20, 2026
os-elon-musk
pushed a commit
that referenced
this pull request
Sep 21, 2026
…e (objectui#10061) Ruling batch #146 item 5 letter A (objectstack#18012) declares a between pair with one blank bound incomplete: not emitted, AND shown as incomplete. The first half has held since objectui#5025 — every write path folds the row through the builder's arity-aware isFilterValueComplete — but the drop was silent: the author saw a bound they had typed while the row counted for nothing. The blank bound now carries aria-invalid, an aria-describedby description naming the missing side, and a destructive border. A diagnostic, never a refusal: the completeness rule is untouched, nothing gates on the marker, and the group's other rows keep applying. Only the asymmetric state is marked. Both bounds blank is the untouched row Add filter draws; both filled is a complete range; a non-pair operator never renders it. isValueUnset, never !bound (objectui#4873): [0, ''] is marked on its upper bound and [0, 10] is complete. The description reuses the shared validation.required key rather than declaring a new one, mirrored verbatim in this file's createSafeTranslation defaults table as form.tsx already does, so no locale pack has to move. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xr7APep6jm1Zta3KUzPzZf
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…e (objectui#10061) (objectstack-ai#10189) Fixes objectstack-ai#10061 Clause-②: no — an accessibility diagnostic on an input this component already accepts. No new exported prop, no new published key, no widening of any accepted set. Ruling batch objectstack-ai#146 item 5 letter A (objectstack#18012, maintainer 「146 同意」) declares a `between` pair with one blank bound **incomplete: not emitted, AND shown as incomplete**. ## What was already true, measured before writing anything The 「not emitted」 half has held since objectui#5025. Every write path reachable from this builder folds the row through the builder's own arity-aware `isFilterValueComplete`, and each one has its own pin — all five files below are green on this branch, unchanged: | write path | what it feeds | its pin | |---|---|---| | `foldFilterGroupToSpecRules` (`app-shell/src/views/viewFilterFold.ts`) | saved / shared view rules, and metadata-admin's `FilterBuilderField`, which folds through it | `viewFilterFold.pairValue.test.ts`, `viewFilterFold.builderSetOperators.test.tsx` | | `sanitizeViewOverride` (`app-shell/src/views/ObjectView.tsx`) | the personalization overlay | `ObjectView.overlayPairValue.test.ts` | | `convertFilterGroupToAST` (`plugin-list/src/ListView.tsx`) | the live grid query | `convertFilterGroupToAST.test.ts`, `convertFilterGroupToAST.canonicalSpelling.test.ts` | | `groupToCondition` (`app-shell/.../inspectors/datasetFilterCondition.ts`) | a dataset's stored `filter` | `datasetFilterCondition.unmappedInert-9372.test.ts` | The fourth is the dataset-filter bridge, which drops `between` **wholesale** — mapped by nothing, inert by objectui#9372, and its own card. Firing control for that census: a tree grep for the predicate also lands on `packages/fields`' `FilterConditionField`, which only *mentions* it in prose while keeping a second rule of its own (objectui#9914, landed). So the deliverable here is the other half only, and it was entirely unbuilt: the file carried zero `aria-invalid` (control: four `aria-label` hits in the same file). An author who typed one bound saw their value sitting on screen while every write path discarded the whole row, with nothing anywhere saying so. ## What this adds The blank bound of a half-filled pair now carries `aria-invalid`, an `aria-describedby` description naming the missing side (「To is required」), and a destructive border — the shadcn `Input` this file renders carries no `aria-invalid` styling of its own, so the attribute alone would show a sighted author nothing. ⛔ A diagnostic, never a refusal. The completeness rule is untouched, `reshapeFilterValue` and `toPairBounds` are untouched (the render-side padding is inert draft state and stays), nothing gates on the marker — the only non-test reader of `aria-invalid` in this tree is a CSS `has-[]` selector in `plugin-chatbot` — and the group's other rows keep applying. **Only the asymmetric state is marked.** Both bounds blank is the untouched row `Add filter` draws, and is no more half-written than an `equals` row with no value yet; both filled is a complete range; a non-pair operator never renders it.⚠️ **A blank bound is not a zero bound.** `isValueUnset`, never `!bound` (objectui#4873): `[0, '']` is marked on its **upper** bound and `[0, 10]` is complete and marked nowhere. A truthiness reading would mark the `0` the author had just typed and leave the blank side clean — exactly backwards, and the way this fix goes wrong. ### Why `aria-invalid` and not a new spelling Asked, not assumed. This tree has one structural spelling for 「the editor will not take what is in this control」 — `aria-invalid`, pinned that way in `CelPredicateField`, `ConditionWidget`, `ConditionalFormattingEditor` and `ConditionBuilder` — and no separate 「not finished yet」 idiom exists to use instead. `LocationField` is the precedent for a widget computing its own, rather than receiving a host's error slot. The one caveat found while checking: `celAuthoring.ts` ties `aria-invalid` to a severity the save gates count, so the attribute reads as 「refused」 in that region. It is defensible here because the gate half does not exist on this surface — nothing reads the attribute — and because the marked value genuinely fails validation: objectstack#18012's spec half, merged, now refuses `{$between: [1, '']}` at parse. Firing only on the **asymmetric** state is what keeps it off the 「invalid while the user is still typing」 anti-pattern. ### i18n No locale pack moves. The description reuses the shared `validation.required` key (`{{field}} is required`, already in all ten packs) with the bound's own label filled into the hole, mirrored verbatim in this file's `createSafeTranslation` defaults table exactly as this package's `form.tsx` already mirrors that same row. Declaring a private `filterBuilder.*` sentence would have been a new string for ten translators and a second authority on the wording. ## Ablation — two legs, each discriminating The two halves are pinned in two files on purpose, so a single mutation cannot red both and prove neither. Both legs: anchor matched exactly once, the write verified on disk in both directions, restore by `git checkout HEAD -- path` verified by blob hash. - **Leg A — delete the marker** (`missingBound` forced to `null`): the new affordance file goes **7 failed**, `filter-builder-pair-completeness.test.tsx` stays green. `Test Files 1 failed | 1 passed (2)`. - **Leg B — delete the completeness rule** (the pair arm back to the shape-blind length reading): `filter-builder-pair-completeness.test.tsx` goes **5 failed**, the new affordance file stays green. `Test Files 1 failed | 1 passed (2)`. ## Verification - `pnpm exec vitest run packages/components/src/__tests__/` — `Test Files 169 passed`, `Tests 1656 passed` (run from the repo root, with the two `viewFilterFold` fold tests). - The five write-path pins above, run together: `Test Files 5 passed`, `Tests 103 passed`. - `packages/components`' own `type-check`, both legs: `tsc --noEmit` exit 0 and `tsc -p tsconfig.test.json` exit 0, after building the dependency closure (`pnpm --filter '@object-ui/components^...' build`) — without it `tsc` cannot resolve the workspace `.d.ts` and reports a prerequisite failure, not a type error. - `pnpm check:i18n-keys` · `check:i18n-drift` · `check:i18n-dead-keys` · `check:control-bytes` · `check:test-path-roots` · `check:changeset-claims` · `check:new-line-citations` · `node scripts/check-changeset-presence.mjs` — all exit 0, each captured to a file and read back rather than judged through a pipe. - Lint, narrowed to this package and declared: `eslint packages/components --format json` selected **501 files** by eslint's own config resolution and reported **0 errors** (962 pre-existing warnings; this repo deliberately sets no `--max-warnings`). The narrowing is safe to state because no type-aware linting is configured — `eslint.config.js` declares no `projectService` and no `parserOptions.project` — so this diff cannot move the verdict on any file it did not touch. The repo-wide run is CI's. All readings above are from the tree at `d31d17177`. ## Acceptance notes - **Noted, not filed — `plugin-list`'s `UserFilters` is a second range surface with a different answer.** An authored `date-range` user filter lowers a half-filled pair to a **one-sided** query in `emitFilters` (only the bound that is filled becomes a `>=` or `<=`), so nothing is dropped and no `between` is emitted — a different mechanism, not this defect, and arguably correct on its own terms. What is left is an inconsistency between two surfaces: half-typing a range means 「open-ended」 in one and 「nothing yet」 in the other. Not a reproducible defect, no declared contract broken, no trap that makes an AI author refused metadata ⇒ outside the three filing classes. Carrier: none named — no open PR or queued card touches that file. `session_01Xr7APep6jm1Zta3KUzPzZf` is the seat session behind this branch. --- _Generated by [Claude Code](https://claude.ai/code/session_01Xr7APep6jm1Zta3KUzPzZf)_ Co-authored-by: Claude <noreply@anthropic.com>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…`, both bounds required (objectui#10062) (objectstack-ai#10253) Fixes objectstack-ai#10062 Clause-②: yes The Studio dataset-filter bridge now stores a `between` row as the spec's own `{ $between: [lo, hi] }`, and only when both bounds are present. This executes ruling batch objectstack-ai#146 item 5, letter A (maintainer 「146 同意」, objectstack#18012): the `between` arm maps once a both-bounds completeness rule exists. One does: the builder's own `isFilterValueComplete` (objectui#5025). Implemented by `domain:ui` seat objectstack-ai#1's dispatched dev, session `https://claude.ai/code/session_01BA3nKVUwKQJf8DBxrSVtNC`. Diff: 7 files. Round 1 was one commit `83eb57f0` on base `a78cd378`; round 2 adds fix `8850829b` and merge `a30e42bf` (of `origin/main` `6099dd87`). ## What changed in `datasetFilterCondition.ts` | | before | after | |:--|:--|:--| | `OP_TO_MONGO` | no `between` | `between` writes `$between` | | `MONGO_TO_OP` | no `$between` | `$between` reads back as `between` | | write-half completeness | inline `v == null`, `v === ''`, empty array: length-blind, so `['2026-01-01', '']` passed | `isFilterValueComplete(c.operator, v)`: the builder's arity-aware rule. For scalar and list operators its non-pair branch is the same three tests. | | read half, stored `$between` | non-representable (unmapped), so it went to the Source tab | representable only when `isFilterValueComplete('between', value)` AND (no field list is supplied, or `operatorsForFieldType(column type)` offers `between`). Anything else goes to the Source tab (round 2). | **What a half-filled pair emits instead: nothing.** It is an unfinished row. If it is the only row, `isClearedGroup` still sees rows on screen, so the inspector patches nothing and the stored filter stays. Beside other rows, only those rows are stored. **Why the read-half guard.** Without it, mapping `$between` would turn a stored half pair (the installed spec's comparand door, `@objectstack/spec` 17.4.0, still accepts `[1, '']`) from a Source-tab filter into an editable row. The next commit of any other row would then drop it silently. The guard is scoped to the pair arity. The same question for stored scalars and lists predates this card and is not answered here (see Acceptance notes). ## Deliverables 1. **The arm maps with both bounds required, and the objectui#9381 pin is flipped.** The last block of `datasetFilterCondition.unmappedInert-9372.test.ts` used to read 「`between` stays unmapped — and is now unmapped INERT」. It now reads 「`between` maps, with BOTH bounds required」. 2. **objectui#9372's pending changeset is amended, prose only.** The frontmatter is untouched: `check-changeset-overwrite` prints `declared at base: @object-ui/app-shell: patch` and `declares now: @object-ui/app-shell: patch`, which is its deliberate-correction case. The paragraph that said 「`between` stays unmapped」 now says why `between` was held back and that objectui#10062 maps it behind `isFilterValueComplete`. Authority to edit another card's changeset: this card, because the ruling supersedes that sentence. 3. **The `$between` conformance reading.** The leg `expect(covered).not.toContain('$between')` is inverted. `covered` now reads the Filter Protocol's temporal driver tables (`TEMPORAL_CASES`, `TEMPORAL_TIME_CASES`) beside `FILTER_TEXT_CASES`, and it contains `$between`. Attribution legs keep the union honest: `$between` comes from the temporal tables, the text table still lacks it, and `$beginsWith` is in none of them. `$between` also got the other readings the three text operators got: - membership in `FILTER_OPERATORS`; - the comparand door: `FieldOperatorsSchema` accepts the emitted pair and refuses a scalar, a one-member list, a three-member list and a null bound; - the builder offers `between` only on `date`, `datetime` and `time`, which are the kinds the temporal rows cover. 4. **`Clause-②: yes`**, carried from the claim: the bridge now writes `$between` into stored `dataset.filter` and `measure.filter`. **Read-half rule (round 2):** a stored `$between` opens as an editable row only as a complete pair, and, when a field list is supplied, only on a column whose builder bucket offers `between` (today `date` / `datetime` / `time`). Untyped and unlisted columns are refused too, because the builder draws the text bucket for them. Field-less reads are unchanged. **The emitted shape is the one the consumer reads.** In objectstack's `service-analytics` (read at `c1641868`), the preview evaluator's `$between` arm returns false unless `Array.isArray(expected) && expected.length === 2`, and the filter normalizer handles `$between` only as an array. ## Pins In `datasetFilterCondition.unmappedInert-9372.test.ts`, the new block 「`between` maps, with BOTH bounds required」: - both bounds give `{ closed_at: { $between: [lo, hi] } }`, and `[0, 10]` is emitted, so `0` counts as a bound, not a blank; - a missing lo or hi is not emitted, over 11 shapes: either side blank, both blank, empty array, one member, a bare scalar, empty string, null, undefined, and a null bound on either side; - what a half pair does instead: as the only row it holds; beside a complete row, only that row commits; - parity: for every probe, emitted if and only if `isFilterValueComplete('between', value)` is true, so a second local rule cannot drift; - round trip, alone and inside a flat `$and`; - a stored `$between` this bridge would not have written is non-representable; - the conformance sub-block (deliverable 3). The (ii) gestures in the same file keep their meaning. The operator-route gesture now switches to `between` through the builder's own `reshapeFilterValue`, which yields `['acme', '']`, and still holds. The partial-group gesture uses a half pair. A new pin keeps the unmapped arm itself live with `containsCaseInsensitive`, an opt-in this inspector does not grant. Other test files: - `nullOperators-9363`: `DECLARED_UNEXPRESSIBLE` is now empty, so no offered operator drops. The unmapped-arm fixture moves to `containsCaseInsensitive`. - `datasetFilterCondition.test.ts`: same fixture move. - `dateRoundTrip-9382`: the `between` skip is gone. A dropped offered operator is now a break, and `between` carries two days. New pins: `date`, `datetime` and `time` columns store `$between` and reopen as `between` with the bounds intact. The real `FilterBuilder` draws the stored range as "Between" with both days on screen, no `aria-invalid`, and no write-back. ## Red first The new tests ran against the base source (`a78cd378`): **11 failed, 56 passed**. The failures are the mapping pins and nothing else. The missing-bound, half-pair and non-representable pins passed. ## Ablation, after commit (HEAD `83eb57f0`) Each leg ran through objectstack's `scripts/ablation-replace.mjs` in wrap mode. The anchor hit exactly once, the mutation was verified on disk (anchor count 1 to 0, blob changed), and the restore was proven: blob equals the HEAD blob `22ca8b6f`, and `git diff HEAD` is empty. The subject is imported relatively from source, so there is no `dist` leg. Each leg's prediction was written down before it ran. | leg | mutation | red | green that matters | |:--|:--|:--|:--| | A1 (the card's) | delete `between: '$between',` from `OP_TO_MONGO` | 10: the 9363 partition; both-bounds, zero-bound, parity, round-trip and door in the new block; the 9382 sweep and its three column pins | missing lo or hi, half-pair-instead, non-representable, operator-route gesture, partial group, panel draw (read half only) | | A2 | disable the read guard | 1: non-representable stored `$between` | everything else | | A3 | restore the old inline length check | 5: operator-route gesture, partial group, missing lo or hi, half-pair-instead, parity | the mapping pins | A3 is the answer to objectui#9695's point that the delegation "alone is behaviourally unobservable": with `between` mapped, it is observable, and five pins read it. ## Verification at HEAD `83eb57f0` Commands ran from the repo root, heavy runs through `os-verify-lock.sh`. - `pnpm exec vitest run packages/app-shell/src/views/metadata-admin/inspectors/`: **88 files passed; 1070 tests passed, 1 skipped.** The skip is a `skipIf` already in `flow-node-config.spec-reconciliation`. - `@object-ui/app-shell` `type-check`, meaning `tsc --noEmit && tsc -p tsconfig.test.json`: exit 0. The dependency closure was built first (turbo, 28 tasks). `--listFilesOnly` on the test project lists all four edited test files. - `pnpm check:control-bytes`: OK. - `pnpm check:new-line-citations`: 0 new. - `node scripts/check-changeset-presence.mjs`: 1 changeset declared. - `check-changeset-overwrite`: reports only the objectui#9372 edit, with its declaration unchanged. - `pnpm check:changeset-claims`: no pending changeset names a touched file; no self-contradiction. - Also exit 0: `check-changeset-no-major`, `check-changeset-fixed`, `check:pending-changeset-literals`, `check:spec-symbols`, `check:test-path-roots`, `check:installed-pin-claims`. - `check-governed-queue-guard --test` on the 7 paths: NOT GOVERNED. - **Lint, narrowed, with proof it excludes nothing.** - Population: CI runs `turbo run lint`, which runs each package's `eslint .` under the root `eslint.config.js`. This run covered the 5 touched `.ts`/`.tsx` files. - Count, from `--format json`: 5 files, 0 errors, 3 warnings. All three are `no-explicit-any` on existing `as any` casts in `conditionToGroup` (2 at base, 2 at HEAD). - Invariance: `eslint.config.js` has no `parserOptions.project` or `projectService`, so there is no type-aware linting. No rule module under `eslint-rules/` reads the filesystem (0 hits; control: 11 rule modules match `create(`). So this diff cannot change the verdict on any file it does not touch. - Docs: nothing in `content/docs` or the app-shell README describes this bridge (grep: 0 hits), so there is no docs change. ## Round 2 (head `a30e42bf` = fix `8850829b` + a merge of `origin/main` `6099dd87`) Answers contract review `5815806788`. - **Pins** in `dateRoundTrip-9382`, block 「a stored `$between` opens as a row only where the column's bucket offers `between`」: - a number column is refused; - the date control stays representable; - an every-bucket sweep equals `offeredBy(type).includes('between')`; - untyped and unlisted columns are refused; - the field-less read is unchanged; - the WHY leg: `reconcileOperatorForField` → `equals`, reshape → `1`; - the real `DatasetDefaultInspector` shows the Source-tab note for a number-column `$between`, and, as control, opens the builder drawn as 「Between」 with both bounds for a date column. - The completeness pin is retitled to what it measures. - **Red first**, on the `83eb57f0` source: 4 failed / 48 passed. - **Ablation R2** (bucket rule dropped): 4 red / 71 passed, date controls green. Restore proven. - **Verification at `a30e42bf`:** inspectors 88 files, 1078 passed / 1 skipped; app-shell `type-check` exit 0; the changeset and vi-mock gates exit 0; governed guard NOT GOVERNED. - **Changesets:** the `10062` sentence now lists exactly what is refused. The `9372` clause now reads 「as the only row, leaves the stored filter alone」, with frontmatter byte-identical. ## Acceptance notes - **Out of scope, class (a), round 2, routed to objectui#10257.** The same bucket gap exists for OTHER stored tokens: `$in` on a date or number column and `$gt` on a text column read back as operators the column does not offer, and one field-picker touch reconciles to `equals`. The seat added it to objectui#10257, the read-half card from round 1, as comment `5817965568`, because both are the read half accepting a row the builder cannot hold faithfully. - **Out of scope, class (a), not filed here.** The read half accepts a stored scalar or list that the write half drops. `{ $and: [{ stage: { $eq: 'won' } }, { name: { $eq: '' } }] }` reads as representable. Editing the `stage` row then commits `{ stage: { $eq: 'lost' } }`, which silently removes the untouched `name` condition. The same happens to `{ region: { $in: [] } }`, and there the loss widens the result set from nothing to everything. This was confirmed with a temporary probe test, since deleted. It predates this card; the new `$between` guard deliberately does not widen to cover it. It is in the report for the seat to file. - The JSDoc of `DatasetFilterField.commitFilterGroup` in `DatasetDefaultInspector.tsx` still names `between` as its example of an unmapped operator. That file is outside this claim's declared surface, so it was left untouched. Carrier: none. - `plugin-list`'s `ListView` comment 「Matches groupToCondition in datasetFilterCondition.ts」 was only half true for pair arity before this change, and is fully true now: both call `isFilterValueComplete`. - An observation, not filed: the spec's `DatasetSchema` accepts any operator object under `filter` at parse (a scalar `$between`, a one-member `$between`, an invented `$betweenx`). The value door is `FieldOperatorsSchema`, not the dataset schema. The runtime's answer to those shapes was not measured. - The spec half, objectstack#18012, refusing a blank `$between` bound at parse, is not in the installed spec. This bridge does not depend on it, and no pin asserts the spec's current acceptance of `[1, '']`, so that tightening will not turn anything red here. - **NOT MEASURED: CI**, including the `Spec Main Shape Gate`, because it had not run when this was written. CI convergence belongs to the seat. <sub>Body refreshed by `domain:ui` seat objectstack-ai#1 with the round-2 corrections, and the routing made true · 2026-09-24T16:33Z</sub> --- _Generated by [Claude Code](https://claude.ai/code/session_01BA3nKVUwKQJf8DBxrSVtNC)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Oct 7, 2026
… bare apiMethods-card number (objectui#10803, batch 7) (objectstack-ai#10962) Part of objectstack-ai#10803 Clause-②: no Dispatched implementation of the `domain:ui` seat objectstack-ai#1 claim (comment `5867587761`) on objectui#10803, batch 7, session `https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk`. Citations only: no sentence's claim moves, and every edited pending changeset's frontmatter is byte-identical. The only runtime text that moves is two console warnings, one in `@object-ui/app-shell` and one in `@object-ui/plugin-detail`, which lose their dead pointer and nothing else (amendment `5860244997`, Q1 = A; `patch` changeset). No test pins any changed text: the literal-anchor sweep below finds no specific anchor, so no test file is edited. This batch carries release `5866922219`'s two lists: - the **30 `objectstack#N` citations that answer 404**, in the card's two classes (pending changeset prose and non-test `packages/*/src`); - the **28 bare `objectstack-ai#3391` lines in 10 files** that mean objectstack's apiMethods whitelist card, which batch 6 fixed at 2 other sites. ## Why `Part of`, not a closing line Both lists read **0** after this batch (**Census**). The brief's rule was a closing line if the card's lists all read 0. They do, but reading the sentences found **10 more lines in the same two classes that cite a dead objectstack number written bare**, three numbers in all (**Acceptance notes** 1). Triage item 3 puts a dead number found later in these classes on this card, so the card is not finished. Whether it carries them as a batch 8 or closes is the seat's call. ## Premise, re-measured on `origin/main` `3b469c8ea` (the branch point) - **Every distinct `objectstack#N` in the two in-scope classes.** 372 numbers (the one objectstack issue URL in these classes names 6227, which is among them). Each was read once with REST `GET /repos/objectstack-ai/objectstack/issues/N`: - 341 answer 200; - 1 answers 301: objectstack#14026, transferred to objectui#10102, which batch 6 re-qualified; - **30 answer 404**, exactly the 30 batch 6 listed. - **The 30, read again.** A second `issues/N` read of each answers 404 (30 of 30), and `pulls/N` answers 404 for all 30. Lit controls in the same run: objectstack#3391, objectstack-ai#3720 and objectstack-ai#3546 answer 200 as issues, and `pulls/13267` answers 200. - **objectstack-ai#3391 and objectstack-ai#3546, both repositories.** - objectui#3391 is the record-header api-action placeholder card, unrelated. - objectstack#3391 is the apiMethods whitelist contract card: "UI 操作按钮与 apiMethods 白名单一致性契约落地". Its body names the effective operation set, `/me/permissions`, the 405 import refusal and export derived from list, which is what each of the 28 sentences says. - objectui#3546 is the missing-i18n-keys card, unrelated. - objectstack#3546 is "detail/form 面的 edit/delete 按钮接入服务端 effective 操作集", the inline-edit gate the two paired lines describe. - **objectstack history.** Read from a full, not shallow, treeless clone of objectstack `main` (`git rev-parse --is-shallow-repository`: false). - Every objectstack sha this PR cites is an ancestor of objectstack `main` (`git merge-base --is-ancestor`, exit 0): the 24 this PR adds to the tree, the 3 its edited sentences already cited (`c459da6bc`, `89448a52b`, `9bd4344e4`), and the 7 this body names besides. - `git rev-parse --short=9` returns the same 9 characters for each. - Control legs in the same clone: the head of the open PR objectstack#20421 (`a22b90fc0`) answers exit 1; the known ancestor `51789064` answers exit 0. - **The one objectui sha.** `7a197e7c5` is an ancestor of the branch point, exit 0. Control legs: the head of PR objectui#10945 answers exit 1, and `5f789538d` answers exit 0. This checkout is not shallow. - **A cross-check, not the method.** objectstack's own sweep of dead tracker citations in its tree (objectstack#19123's landing `66e266c93`, its stages `21ab41041`, `5cf58eb16` and `0d7ed5a37`, and `f415bcf18`) anchored eight of these numbers in its own files. For each of the eight (objectstack-ai#5970, objectstack-ai#6483, objectstack-ai#9934, objectstack-ai#10485, objectstack-ai#11330, objectstack-ai#11846, #12868 and #17147) it chose the same commit this PR cites. - Every edited changeset is pending: it is present in `.changeset/` on `main`. ## Census (the enumeration pin for this batch) The 30 numbers (REF = a commit or tree): ``` git grep -nE 'objectstack#(5970|5976|6038|6124|6281|6331|6450|6483|6515|9933|9934|10354|10485|10695|11330|11507|11513|11658|11703|11753|11846|12009|12868|13117|13670|16126|17147|17762|17987|18012)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | wc -l ``` The bare `objectstack-ai#3391`, with the same pathspec: ``` git grep -nE '(^|[^0-9A-Za-z_#/])objectstack-ai#3391([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | wc -l ``` | REF | the 30 | bare `objectstack-ai#3391` | |:--|:--|:--| | `3b469c8ea` (branch point) | **82**: 26 changeset lines in 24 files, 56 src lines in 39 files | **28** in 10 files | | `c292a6400` (this head) | **0** | **0** | | this head merged with `main` `5c94589f0` (`git merge-tree --write-tree`, clean, tree `bba27eece`) | **0** | **0** | | `5c94589f0` (`main` alone) | 82 | 28 | - Lit controls on the same instruments at this head: live objectstack#10856 reads 4 lines (4 at the branch point); `objectstack#3391` reads 32 lines, against 3 at the branch point (28 re-qualified here, and this PR's sweep changeset names it once). - **Out of scope, as it stands** (whole tree at this head, unfiltered): - the 30 numbers: 84 test lines in 47 files, 1 scripts line, 2 lines in 2 `apps/console` files, 2 package READMEs (`auth`, `react`), 11 lines of published `CHANGELOG.md` history in 8 files; 0 `.github`, 0 governed, 0 `content/docs`; - bare `objectstack-ai#3391`: 12 test lines in 9 files and 23 `CHANGELOG.md` lines in 8 files. ## Citation form - **An objectstack commit** is written the way batch 6 wrote its stand-ins: objectstack and the 9-character backticked sha of the commit on objectstack `main` that landed the change the sentence rests on. - **A dead card beside its own dead pull request** collapses to that pull request's squash commit (objectstack-ai#5970 with PR objectstack-ai#6450, objectstack-ai#10485 with PR objectstack-ai#10695). - **A dead number beside the live landing it already names** is dropped: objectstack-ai#11846 beside PR objectstack#12718, #16126 beside PR objectstack#16920, #12868 beside objectstack `c459da6bc`, and objectstack-ai#12009 beside objectstack `89448a52b` (**Special cases** 3). - **A ruling the dead card carried** is cited by its date, with the commit that executed or recorded it, as batches 3 to 6 did for objectui rulings. - **One sentence cites this repository's commit**, `7a197e7c5`, because the change it names landed here (objectstack-ai#6331). - **Runtime text carries no sha.** In the two console warnings the dead pointer is dropped (**Special cases** 8). - **The bare `objectstack-ai#3391`** becomes `objectstack#3391`, and on the two lines that write `objectstack-ai#3391/objectstack-ai#3546`, `objectstack#3391/objectstack#3546`. ## Mapping, the 30 numbers Lines / files are the branch-point census for that number (a line naming two of them counts under both). | dead number | resolution | what that commit carries | lines / files | |:--|:--|:--|:--| | objectstack-ai#5970 | objectstack `97e7e3caa` | "unify ActionSchema.visible/disabled on one condition shape (objectstack-ai#6450)", body "(objectstack-ai#5970)": `visible` gains the boolean arm | 2 / 1 | | objectstack-ai#6450 (PR) | the same `97e7e3caa`, its squash | as above; the card / PR pair collapses | 2 / 1 | | objectstack-ai#5976 (PR) | objectstack `795b6e1aa`, its squash | "5 值子集改名 `HttpMethodSubset`" | 1 / 1 | | objectstack-ai#6038 | objectstack `7618ee814` | "key a container's default `list` `_views` name by the runtime identity": leg 2 of 3 of the objectstack#5164 ruling, the `packages/lint` half | 1 / 1 | | objectstack-ai#6124 (PR) | objectstack `b3c1f3cd5`, its squash | "key `_views` translations by the runtime view identity"; "The extractor now ASKS the composer for the key" | 1 / 1 | | objectstack-ai#6281 (PR) | objectstack `85ec26d28`, its squash, 2026-08-07 | "SDUI props — enforce or remove (objectstack-ai#5775) (objectstack-ai#6281)": the shared `PageContainerProps`, whose single key is `children`, for `page:section` / `page:footer` / `page:sidebar`, which were `EmptyProps` | 1 / 1 | | objectstack-ai#6331 | objectui `7a197e7c5` | this repository's "SchemaForm reads the canonical `visibleWhen`, reviving every metadata-form predicate (objectstack#6331)" | 1 / 1 | | objectstack-ai#6483 | objectstack `ee58392e1` | "ADR-0005 白名单强制 … (objectstack-ai#6483)"; its diff carries the sentence the comment quotes, "Runtime-created sets … ride `allowRuntimeCreate` (still `true`) and keep working" | 1 / 1 | | objectstack-ai#6515 (PR) | objectstack `2fdb36eb9`, its squash | "SpecifierSchema gains a closed `valueDomain` enum": "`bcp47_locale` is deliberately not in the vocabulary", because `localization.locale`'s options ARE the shipped catalogs | 1 / 1 | | objectstack-ai#9933 | objectstack `d5552ca13` | "admit columnState as an explicitly runtime-only view-overlay key" (subject ending "(objectstack-ai#9996)"; "(objectstack-ai#9933)" is on the message's first body line), on the overlay faces including `viewItemWireFields` | 3 / 3 | | objectstack-ai#9934 | objectstack `79c46da90` | "producer-side user-facing marking for hook refusal messages — userMessage channel (objectstack-ai#9934)": `ApiErrorSchema.userMessage`, the contract half of the objectui#5210 split | 10 / 9 | | objectstack-ai#10354 (PR) | objectstack `9e04c3e35`, its squash | "let the publish door state the package it is promoting"; its changeset and code comment carry the key-presence / `no_draft` warning `ResourceEditPage.tsx` points at | 4 / 3 | | objectstack-ai#10485 | objectstack `35ad101bc` | "retire the `themes` carrier key and ThemeSchema (objectstack-ai#10485, ADR-0049) (objectstack-ai#10695)": "Ruled B (退役授权面, 2026-08-21)", "delete ui/theme.zod.ts whole" | 15 / 13 | | objectstack-ai#10695 (PR) | the same `35ad101bc`, its squash | as above; the card / PR pair collapses | 6 / 6 | | objectstack-ai#11330 | objectstack `a9ee98992` | "manifest.runtime trust-tier text states publish-gate-only enforcement truthfully", the trust-tier half (**Special cases** 2) | 1 / 1 | | objectstack-ai#11507 | objectstack `88b9d749a` | "declare sys_activity.type as an open, author-extensible vocabulary": "Maintainer ruling 2026-08-24, direction 4" | 13 / 9 | | objectstack-ai#11513 | objectstack `e170b0ae5` | "lock package-declared permission sets at the save door; clone to customize", quoting the 2026-08-24 ruling 「同意 第一步(创业阶段,Salesforce 式)」 | 3 / 3 | | objectstack-ai#11658 | objectstack `1a6a19c31` | "open RecordActivityProps.types to author-contributed activity kinds"; its message names objectstack-ai#11658 as the card it settles, and it executes the 2026-08-24 ruling | 1 / 1 | | objectstack-ai#11703 | objectstack `5cb62d88b` | "make clone_permission_set carry all five copied facets"; its message names objectstack-ai#11703 as the card it settles: the silent-grant-loss shape | 1 / 1 | | objectstack-ai#11753 | "the 2026-08-25 ruling whose spec half is objectstack `0e4e51b0a`" | `ActionParamSchema.carryOver`, whose changeset reads "(objectstack-ai#11753 ruling, spec half; objectstack-ai#11992)" and "The maintainer's 2026-08-25 ruling on objectstack-ai#11753" | 2 / 2 | | objectstack-ai#11846 | objectstack `0c2334f6c`; dropped beside PR objectstack#12718 | "retire preview mode — the RuntimeMode 'preview' value and the whole PreviewModeConfig block (#12718)" | 3 / 3 | | objectstack-ai#12009 | dropped beside objectstack `89448a52b` | the card of the `AUTH_SSO_PROVIDER_SCHEMA` removal, whose landing the line already cites (**Special cases** 3) | 1 / 1 | | #12868 | dropped beside objectstack `c459da6bc` | the line already cites the commit that executed the ruling; objectstack's own `f415bcf18` anchors #12868 to the same `c459da6bc` | 1 / 1 | | #13117 (PR) | objectstack `225e7690f`, its squash | "Readiness read for the Phase-2 members … global:search and global:notifications both have shipped platform data sources, so per the ruling both STAY declared" | 1 / 1 | | #13670 | "maintainer ruling 2026-08-31, option 2, recorded in objectstack `8c6a7fc0b`" | "The #13670 ruling settled the question: text's intended evaluation channel is `content` alone" | 1 / 1 | | #16126 | dropped beside PR objectstack#16920 | PR objectstack#16920 (200) names #16126 in its body as the card it settles; merged 2026-09-08 as `859ded3ec` | 2 / 2 | | #17147 | objectstack `aaacf1d5c` | "the install-time granted permission set is REGISTERED at load and refuses nothing — say so, and pin the measurement (#17147)", the measurement on `9bd4344e4` | 2 / 2 | | #17762 | objectstack `4342c9923` | "guard three data lookups against Object.prototype fall-through"; its message names #17762 as a card it settles, `classifyFilterToken` among the three lookups | 1 / 1 | | #17987 | objectstack `e233db9db` | "declare element-level `navigation` on object-kanban / object-calendar …"; its message names #17987 as the card it settles, and its Downstream note: objectui#8652 waits on it, unlock criterion a released, installable `@objectstack/spec` (**Special cases** 1) | 2 / 2 | | #18012 | objectstack `176b03582` | "`$between` requires two non-blank endpoints (#18012)": "Ruling executed: decision batch objectstack-ai#146 item 5, **letter A**" | 3 / 3 | The 28 `objectstack-ai#3391` lines, all now `objectstack#3391`: `ObjectDataPage.tsx` (3) and `ObjectView.tsx` (2) in app-shell; `managedBy.ts` (5); `MePermissionsProvider.tsx` (2), `PermissionContext.ts`, `PermissionProvider.tsx`; `fieldWriteGate.ts`; `ImportWizard.tsx` (6), `ObjectGrid.tsx` (4); `ListView.tsx` (3). Each was read: every one names the server's effective API operation set, `/me/permissions` `apiOperations`, or the 405 import refusal. ## Special cases (the judgement calls) 1. **#17987, two sentences.** - `ObjectTree.tsx`: "blocked on objectstack#17987, whose unlock criterion is a released `@objectstack/spec` carrying the declaration being installable here" becomes "blocked on objectstack `e233db9db`, whose unlock criterion …". That commit's Downstream note states the same criterion. - `ObjectCalendar.tsx`: "that card is `pm:blocked` on objectstack#17987" becomes "that card waits on objectstack `e233db9db`". The label word is not kept, because objectui#8652's label reads `pm:on-hold` today (measured); "waits on" is the phrase `e233db9db`'s own note uses for that card. 2. **objectstack-ai#11330.** "it is objectstack#11330's half of the same panel" becomes "it is the trust-tier half of the same panel, which objectstack `a9ee98992` settled separately". `aaacf1d5c`'s message calls objectstack-ai#11330 "the sibling half of this very sentence", ruled the same way on 2026-08-30, and `a9ee98992` (2026-08-30) is that half's landing. 3. **objectstack-ai#12009 collapses into the sha beside it.** objectui#6910's body and ruling comment `5534414562` name "objectstack#12009 / PR #13413" together as the one `AUTH_SSO_PROVIDER_SCHEMA` precedent, a card and its pull request. Batch 6 replaced PR #13413 with its squash `89448a52b`, so the card goes the way of batch 3's objectstack-ai#5401 / objectstack-ai#5505 pair. 4. **objectstack-ai#11753, two sites.** The card carried the ruling, and `0e4e51b0a` is its spec half. Both sites keep "ruling" as the antecedent that `ActionParamDialog.tsx`'s next paragraph ("The ruling's point …") reads. 5. **objectstack-ai#10354 in `ResourceEditPage.tsx`.** "since objectstack#10354 `doPublish` states" gains a comma, "since objectstack `9e04c3e35`, `doPublish` states", so two adjacent code spans do not read as one. 6. **objectstack-ai#11507 in the 8137 changeset.** "objectstack#11658 executing the maintainer's 2026-08-24 ruling on objectstack#11507" becomes "objectstack `1a6a19c31` executing the maintainer's 2026-08-24 ruling": the executing commit is named, and the ruling is cited by its date. 7. **Line breaks moved** where the stand-in is longer or shorter: `ActionRunner.ts` (two sites), `ActionParamDialog.tsx`, `theme.ts`, `theme.zod.ts` (two sites), `index.zod.ts` and the metadata-admin `i18n.ts` comment, where "ruling on" became "ruling of 2026-08-24,". 8. **The runtime strings.** Only the listed text moves. | file | member | before | after | |:--|:--|:--|:--| | `app-shell/src/layout/activityItemType.ts` | the `console.warn` in `warnUnmappedActivityType` | "… `sys_activity.type` is author-extensible (objectstack#11507, ruled 2026-08-24) and is not validated on write …" | "… `sys_activity.type` is author-extensible (ruled 2026-08-24) and is not validated on write …" | | `plugin-detail/src/renderers/recordActivityFeed.ts` | the `warnOnce` message in `warnUnknownActivityType` | "… `sys_activity.type` is author-extensible (objectstack#11507, ruled 2026-08-24) and is not validated on write …" | "… `sys_activity.type` is author-extensible (ruled 2026-08-24) and is not validated on write …" | No test, doc or changeset quotes either message with the pointer: the census reads 0 in `.changeset/`, and the anchor sweep finds no test literal that drops. 9. **`objectstack-ai#3391/objectstack-ai#3546`.** On the two lines that pair them (`managedBy.ts`, `ObjectGrid.tsx`), both halves are qualified, as batch 6 qualified both halves of "#13337/#13086". The other bare `objectstack-ai#3546` lines are not in this batch's lists and are left (**Acceptance notes** 2). ## The literal-anchor sweep (both test-pin classes, ruling `5861900779`) - **Instrument.** Every string, template and regex literal in all 4073 tracked test and script files (106544 distinct literals), read with the TypeScript scanner. - **Candidate filter.** A literal is a candidate if it matches the diff's removed lines with two lines of context, raw or comment-flattened: 1983. - **Test.** Does its occurrence count DROP between `3b469c8ea` and `c292a6400` in any of the 74 changed files, raw or comment-flattened? 136 do. - **Every one is generic:** digits, punctuation, single words ("object", "blocked", "locked"), character classes, and two regexes that read no changed file: `/objectui#\d+|objectstack#\d+/` in `registry-inputs-spec-parity`, which asserts over its own ledger's reasons, and the older spelling of the three submitRedirect tests' ruling matcher, quoted in their own doc comments (the live `CITES_ITS_RULING` asserts over their own refusal text). None is a changed phrase, a dead number or a changed warning. ## Held **By the serial rule: nothing.** Open PRs were mapped at branch time (9 open) and again after the push, before this PR opened (11 open). The second mapping came after the push, not before it; the same three files were shared both times. Three open PRs share a file with this PR: - _Both PRs below have merged since this PR opened (objectui#10945 as `06a96e948`, objectui#10908 as `b45d463a9`). The trial merge with today's `main` is clean, and both censuses read 0 on it (contract review `5870922323`), so nothing is owed. The two rows are kept as the record at the time._ - **objectui#10945, `RecordDetailView.tsx`.** The blob at its merge-base equals the branch point's. Its hunks are the imports and one block far below; this PR's one changed line in that file is far from both. - **objectui#10908, `types/src/zod/index.zod.ts`.** Its one insertion is in the export list, far below this PR's two changed comment lines. - **objectui#10278, `plugin-grid/src/ObjectGrid.tsx`.** The file drifted between its merge-base and the branch point, so this PR's four changed lines were mapped onto its merge-base by a line alignment: the nearest of its hunks is more than 150 lines from any of them. Trial merges with this head (`git merge-tree --write-tree`): - clean for objectui#10952, objectstack-ai#10950, objectstack-ai#10949, objectstack-ai#10947, objectstack-ai#10945, objectstack-ai#10944, objectstack-ai#10930, objectstack-ai#10908 and objectstack-ai#10777; - objectui#10278 conflicts in `ObjectGrid.tsx`, `plugin-grid/README.md` and `content/docs/plugins/plugin-grid.mdx`, and conflicts in the same three files against `main` alone; - objectui#5400 (Version Packages) regenerates and is not a hold. `.changeset/9954-read-rate-banner.md` is held by this seat's objectui#10913 dispatch (PR objectui#10949) and is untouched here. It carries none of this batch's numbers. ## Changesets - `.changeset/10803-dead-citation-sweep-seventh-batch.md`, EMPTY frontmatter. It covers the comment-only edits in 17 released packages; no published behaviour changes through them. It points at the second file for the runtime text. - `.changeset/10803-seventh-batch-runtime-strings.md`, `'@object-ui/app-shell': patch` and `'@object-ui/plugin-detail': patch`: the two warnings lose their pointer. What renders, and when and how often each warning fires, are unchanged. ## Proof of prose-only (C4), against `3b469c8ea` - **Source.** Each of the 48 touched `.ts` / `.tsx` files was parsed at `3b469c8ea` and at this head with TypeScript 6.0.3's `createSourceFile`, and re-printed by `createPrinter({ removeComments: true })`. - 46 of 48 prints are identical. - `activityItemType.ts` and `recordActivityFeed.ts` are equal once the one listed substitution each (**Special cases** 8) is applied to the base print, each matched once. - 0 parse diagnostics. - Lit controls on the same instrument: editing a string literal moves the print; re-spacing a comment does not. - **Changesets.** The frontmatter block of every one of the 24 edited changesets is byte-identical at `3b469c8ea` and this head (24 of 24, md5). The overwrite gate below agrees. - **Scope of the diff:** 74 files, +157 / −115: 24 edited and 2 new changesets, and 48 non-test source files in 17 released packages. No test file. ## Gates, on this head `c292a6400` Each line is the gate's own verdict and exit code, captured by redirect-then-`$?`. - `node scripts/check-changeset-presence.mjs`, exit 0: "48 source file(s) of 17 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-seventh-batch.md, .changeset/10803-seventh-batch-runtime-strings.md." - `pnpm changeset:check`, exit 0: "All workspace packages are in the changeset fixed group." / "No changeset declares a `major` bump." - `node scripts/check-changeset-overwrite.mjs` (report-only), exit 0: "2 changeset(s) added, 24 modified, 0 deleted". `declared at base` equals `declares now` for each of the 24. - `pnpm check:changeset-claims` (report-only), exit 0: - "Every one of those 1 address(es) either names the tree it was read from, or points at a line this change does not move"; - "Every package declared across those 22 body(ies) is either not negated …"; - the standing notice "87 pending changeset(s) describe a file this change touches". Read against the diff: a pending changeset quoting a replaced pointer would itself carry a dead number and sit in the census, which reads 0. - `pnpm check:control-bytes`, exit 0: "check-control-bytes: OK (scanned 9229 tracked text file(s); skipped 85 binary)." A `grep -P` control-byte self-scan of the 74 files finds none. - `pnpm check:new-line-citations`, exit 0: "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0". - `pnpm check:pending-changeset-literals`, exit 0: "No test source names a pending changeset." - Also run over the touched comments: - `pnpm check:spec-symbols`, exit 0: "spec member citations: 1421 sources + 184 documentation pages; nothing cites a key its spec symbol does not declare."; - `pnpm check:installed-pin-claims`, exit 0 ("OK"); - `pnpm check:comment-mask-corpus`, exit 0 (1 disagreeing file, within the ceiling objectui#7882 holds open); - `node scripts/check-hand-rolled-comment-mask.mjs`, exit 0 ("OK every carrier is a DEBT entry, and every DEBT entry still carries one."); - `pnpm check:handler-key-reads`, exit 0 ("every judged read is a declared member of it"). - The governed-surface predicate over the 74 paths, exit 0: "NOT GOVERNED — 74 path(s) checked against 5 governed surface(s); none matched." Lit control `AGENTS.md`: exit 3. **Tests and type-check**, through the shared verify lock, on `c292a6400`. Each is `VERDICT command-exit 0`. - `scripts/__tests__/`, the whole directory, whose whole-tree scanners read the touched files and changesets: `Test Files 177 passed | 2 skipped (179)`, `Tests 5332 passed | 2 skipped (5334)`. The two skipped files are the network-escape fixtures that run only as a child. - `packages/types/`, `core/`, `react/`, `i18n/`, `providers/`, `permissions/` and `data-objectstack/`, whole packages, in one run: `Test Files 704 passed (704)`, `Tests 13170 passed | 13 skipped (13183)`. - The eight touched plugin packages (calendar, designer, detail, form, grid, kanban, list, tree): `Test Files 787 passed | 1 skipped (788)`, `Tests 7521 passed | 27 skipped (7548)`. - `packages/components/`: `Test Files 324 passed | 1 skipped (325)`, `Tests 3148 passed | 24 skipped (3172)`. - `packages/app-shell/`: `Test Files 854 passed | 1 skipped (855)`, `Tests 8789 passed | 9 skipped (8798)`. - Type-check: `turbo run build` of the 28-package dependency closure (`Tasks: 28 successful, 28 total`), then `pnpm --workspace-concurrency=2` with the 17 package filters `run type-check`: 17 script echoes, 17 `Done`. A first attempt before the build exited 2 on an unbuilt dependency (`Cannot find module '@object-ui/types'`) and measured nothing. - No red leg: the sweep found no anchor to move, so there is no pin whose old copy should fail. CI on `c292a6400`: 43 check-runs, 40 success, 3 skipped, 0 failed; `Spec Main Shape Gate` success. ## Acceptance notes 1. **Dead objectstack numbers written bare: 10 more lines in the same two classes.** A bare number resolves to this repository, where each of these is a live, unrelated card, so no `objectstack#` census sees them. - **Measurement.** The bare-number instrument of PRs objectui#10875 / objectstack-ai#10892 / objectstack-ai#10914 reads 965 distinct numbers at this head. The 916 between 100 and 25000 were each read once as objectstack issues: 877 answer 200 and 39 answer 404. Reading the sentences of those 39, three mean an objectstack card or pull request (below); the other 36 cite objectui cards or objectui pull requests. - **objectstack-ai#9934**, 7 lines in 7 files: `.changeset/7980-agent-key-envelope-read.md`, and in app-shell `index.ts`, `apiErrorEnvelope.ts` (2), `PackageFormDialog.tsx`, `StudioDesignSurface.tsx` and `packages-io.ts`. All mean the `userMessage` channel, objectstack `79c46da90`. - **"PR objectstack-ai#6281"**, 2 lines in `containers.tsx`, beside objectstack#5775. The landing is objectstack `85ec26d28`. - **"objectstack PR objectstack-ai#8452"**, 1 line in `useRecordCrudVerdicts.ts`. The landing is objectstack `27358d517` ("add batch recordIds to security/explain (objectstack-ai#8326) (objectstack-ai#8452)"). - None of them sits in a sentence this PR edits, so they are outside this batch's lists and left. Carrier: this card, triage item 3. 2. **The rest of the bare `objectstack-ai#3546` population.** Five more comment lines write objectstack#3546 as a bare `objectstack-ai#3546` (`RecordDetailView.tsx` 2, `RelatedRecordActionsBridge.tsx`, `record-details.tsx`, `fieldWriteGate.ts`), and one writes it as `objectui#3546` (`plugin-detail`'s `index.tsx`). Each names the server's effective API operation set on a detail or form surface. It is live-but-wrong, not a 404, like the `objectstack-ai#3391` class this batch closed. Carrier: none. 3. **A stale label in a comment.** The `ObjectCalendar.tsx` sentence said objectui#8652 is `pm:blocked`; that card reads `pm:on-hold` today. **Special cases** 1 says how the repaired sentence avoids the label. 4. **Filenames are not citations.** `.changeset/17147-plugin-disclosure-not-enforced.md` carries one of the 30 numbers in its name; it stays, as in PRs objectui#10707, objectstack-ai#10797, objectstack-ai#10854, objectstack-ai#10869, objectstack-ai#10875, objectstack-ai#10892 and objectstack-ai#10914. --- _Generated by [Claude Code](https://claude.ai/code/session_01DuWo5bdP9SdVebamn99GGk)_ _Tests block completed by the `domain:ui` seat objectstack-ai#1 from the dev report `5870507620` (the suites that finished after this PR opened), and three figures corrected after contract review `5870922323` (the objectstack-ai#9933 and objectstack-ai#6515 quotes, and the Held rows); no code claim moved._ Co-authored-by: Claude <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix Incorrect Links in docs/components and Related Files
Problem
The links in the documentation were using incorrect paths. The site uses
/docsas the baseUrl (configured inapps/site/lib/source.ts), but the links throughout the documentation were missing the/docs/prefix.Changes Made
docs/components/index.mddocs/components/index.mddocs/components/index.mddocs/guide/interactive-demos.mddocs/guide/interactive-demos.mddocs/guide/interactive-demos.mddocs/guide/index.mddocs/guide/studio.mddocs/plugins/index.mdOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.