fix(objectql, metadata-protocol, runtime): a package's export carries the objectExtensions it was installed with, and the owner's export folds no other package's extension by objectstack-fleet[bot] · Pull Request #29948 · objectstack-ai/objectstack

objectstack-fleet · 2026-11-03T16:40:02Z

Requested by Yibo Wang · project thread

Clause-②: yes (widening)
Metadata-protocol: none

维护者速读

改了什么：通过 install-local 安装（或代码包里声明）的扩展包，导出时现在会带上它自己的 objectExtensions；被扩展对象的拥有者（基础包）导出时，不再把任何其他包的扩展字段并进自己的对象（此前只排除了它自己的 .custom 配对包）。/meta/object、控制台和数据接口读到的对象不变，仍是合并后的。
为什么改：整部署导出恢复到新环境后，每个包都是 install-local 装进来的；它们再次导出时丢掉扩展字段且不报错，第二跳就静默丢数据（卡片复现 E12）。ADR-0146 D8 第 3 条：包导出只带自己的东西，字段只出现一次。
风险与回滚：只影响包导出读的 per-package 层与导出拼装；registry 新增一个只读方法和一个可选参数，已发布的 withoutExtensionsOf 语义不变。回滚即 revert 本 PR。
先看：packages/runtime/src/domains/packages.ts（registeredExtensionsOf，按目标去重）、packages/objectql/src/registry.ts（getObjectExtensionsOf 与 isLeftOutExtension）、packages/metadata-protocol/src/protocol-meta-list-reads.ts（per-package 层改传 onlyExtensionsOf）。
两分钟验证：pnpm --filter @objectstack/runtime exec vitest run --maxWorkers=2 src/domains/packages-export-base-showcase-boot.integration.test.ts -t 29872，预期 2 passed：扩展包导出带 objectExtensions，基础包导出与安装扩展包之前逐字节相同，第二跳再导出不变。
需要你做的：无，席位落地。

What changes

The defect (measured on origin/main 21510bb). assemblePackageManifest built a package's objectExtensions from the object_extension items of the protocol's per-package layer. install-local (and a code package) registers a manifest's objectExtensions straight into the registry as 'extend' contributors (ObjectQL.registerApp) and files no item, so such a package exported no extension. Its fields were folded into the OWNER's export instead (the per-package layer left out only the owner's .custom pair since #29930). A deployment restored from an export therefore lost every extension field on its next export, and a .custom pair installed from its export no longer re-exported its extension.

Half 1: the extender's export carries its extensions, however they were installed.

SchemaRegistry.getObjectExtensionsOf(packageId) (new, @objectstack/objectql): every extend contribution the package makes, read back as the objectExtensions entry it was registered from, the inverse of registerObjectExtension. extend is the key it is filed under; priority is written only when it is not the default 200 (the value an entry without one parses to), so a second hop exports the same bytes as the first; name and every envelope key (_packageId, _provenance, ...) are left out.
assemblePackageManifest (@objectstack/runtime) appends those entries (registeredExtensionsOf) to the per-package layer's object_extension items, skipping any target an item already names: a published extension keeps exporting as it is stored (metadata-protocol + objectql: an object extension is an authorable item of a writable package — saved and published through the existing doors, registered as 'extend', exported as objectExtensions #28574, packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 pins unchanged). A registry double without the method adds nothing, as before.

Half 2: the owner's export carries its object without ANY other package's extension (the seat's carrier note 6605292329).

listItems / getAllObjects / foldObjectExtendersOnto take an onlyExtensionsOf option: only that package's own extend contributions fold, every other package's is left out. Both options live in one ObjectExtensionFoldOptions and one predicate (isLeftOutExtension).
The per-package layer (readFlattenedMetaItems, layer: 'per-package') passes onlyExtensionsOf naming the listed package to both the registry list and the overlay-row fold, in place of withoutExtensionsOf naming its pair.
withoutExtensionsOf is kept with its meaning: it shipped in the published @objectstack/objectql@18.3.0 tarball (5 hits in dist/index.js, measured with npm pack), so removing it would be a narrowing of a published surface. No in-repo caller passes it any more; its unit pin stays.

Served and effective reads are untouched: neither option is passed outside the per-package layer, and the controls in every new pin read GET /meta/object/NAME and GET /meta/object with every extension folded in.

Tests

packages/objectql/src/registry-extension-field-patches.test.ts: the packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 describe now pins onlyExtensionsOf (owner listed with neither the pair's nor a third package's extension; an extender folds its own only; an un-extended object is the cached object; byte-equal to a registry with no extender; the stored-body fold) and keeps a withoutExtensionsOf case. A new describe pins getObjectExtensionsOf: a manifest entry through ObjectQL.registerApp comes back as written and parses under the strict ObjectExtensionSchema; a stored extension through registerObjectExtension comes back with its own priority and re-registers on a fresh registry to a byte-equal served object.
packages/runtime/src/domains/packages-export-base-showcase-boot.integration.test.ts (the shared showcase-boot harness; new top-level describe): an extender registered the way install-local registers it exports its entry; the base's export is byte-identical to its export before the extender was installed, with the pair's extension published beside it, and after a restart; the pair exports its own item only; an extender installed from its own export re-exports the same bytes (the second hop).
packages/qa/dogfood/test/package-export-bundle-round-trip.dogfood.test.ts: the first describe asserts the install-local extender's objectExtensions by name and in full on the source bundle AND the target bundle, and that the base's object carries the extender's field on neither; the third describe asserts the pair installed on the target from its entry re-exports its extension. The same-inventory pin stays and is green.

Acceptance notes

The inventory pin alone could not see the defect, and it still cannot see half 1 alone: with half 1 ablated and half 2 in place, the inventory test stayed green (both hops lose the field identically) while the new runtime: a package export omits the objectExtensions of a package installed through install-local, so an exported .custom pair loses its extension fields on the second export hop #29872 dogfood assertions went red. That is why the halves ship together and why the new assertions read the field by name.
Dedupe is by the item's extend spelling against the registry key. A stored row spelling a short name that the registry files under a legacy folded key (objectql: a manifest objectExtensions entry or hydrated row whose extend folds to a legacy key opens a second, owner-less object entry #28858) would export twice; the save door refuses that spelling (metadata-protocol: an object_extension item's refusal sentences, row comment and folded target spelling misfit the item door #28834), so no stored row carries it today. Noted, not filed.
The pending .changeset/29903-base-export-without-pair-extension.md still says an extension from any other installed package "is still folded into the base's object in the base's export, as before", which this PR makes false. I first corrected it, and check-empty-changeset refused (it guards another PR's pending note); I restored it byte-for-byte from the merge base instead, and this PR's changeset carries a "Supersedes, in the same release" paragraph naming that sentence. The seat may still prefer to correct the packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 note on the release side.
A code package's export (not in the whole-deployment bundle, which skips source: 'code' rows) now also carries its manifest objectExtensions, and a platform-owned object's export no longer folds in plugin extensions. Both follow from the same rule.

Verification

Ablations (each: mutation through scripts/ablation-replace.mjs, anchor 1 → 0, blob restored == HEAD, `git diff HEAD` empty)

A, half 1 (packages.ts: drop the registeredExtensionsOf append) against the runtime integration file -t 29872: 2 failed. the extender's export carries its manifest entry: expected undefined to deeply equal [ { extend: 'showcase_task', …(1) } ], and the second-hop test the same. Restored.
A on dogfood (runtime resolves from src there): the round-trip file 2 failed / 11 passed: source: com.dogfood.exportext: expected { extends: [], objectCarries: false } to deeply equal { …(2) } and [#29872] target: the pair installed from its entry re-exports its extension: expected undefined to deeply equal [ { …(3) } ]. Restored.
B, half 2 (protocol-meta-list-reads.ts: onlyExtensionsOf never set; marker ablated-29872-b; metadata-protocol rebuilt, ablation-dist-preflight found the marker in dist) against the runtime integration file -t '29872|29903': 2 failed / 1 passed. expected [ 'organization_id', …(11) ] to not include 'acme_billing_code' and the packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 the base's object with the extension live equality. Restored, rebuilt, preflight --absent exit 0.
C, registry (isLeftOutExtension's onlyExtensionsOf clause → false) against registry-extension-field-patches.test.ts -t 29872: 4 failed / 4 passed (the four onlyExtensionsOf cases). Restored.

Local runs (code head 2e498fb; final head 7b1145a changes only this PR's changeset)

Build: pnpm --filter '@objectstack/dogfood^...' build (closure), then objectql + metadata-protocol + runtime rebuilt: VERDICT command-exit 0.
pnpm --filter @objectstack/objectql test: 547 files / 10827 tests passed.
pnpm --filter @objectstack/metadata-protocol test: 311 passed, 4 skipped files / 22320 passed, 26 skipped tests.
pnpm --filter @objectstack/runtime test: 538 files / 8599 passed, 19 skipped tests.
typecheck for objectql, metadata-protocol, runtime (incl. each check:test-typecheck): exit 0.
Dogfood package-export-bundle-round-trip.dogfood.test.ts: 13/13.
eslint --no-inline-config over the 8 changed source/test files: exit 0 (the repo-wide pnpm lint is CI's Lint & Repo Gates).
dispatch-gates --commands (67 families), each run and its exit recorded: 67 exit 0 after three reruns. check-plugin-teardown-shape --self-test first exited 3 (shallow clone; its pinned fixture commit fetched, then 48 cases pass); check:dual-build-cjs-loads first exited 3 (seven unbuilt dists: client-react, embedder-openai, knowledge-memory, knowledge-ragflow, service-cluster-redis, service-knowledge, studio; built, then exit 0); check-empty-changeset first exited 1 on my edit of the packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 note (see Acceptance notes; restored, then exit 0). The changeset gates (check-empty-changeset, check-changeset-no-major, check-adr-0087-registration) were rerun on 7b1145a: exit 0. dispatch-gates --ran: 67 derived, 67 run, 0 NOT-MEASURED, 0 UNRUN.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm

…ts manifest objectExtensions, and an owner export folds only its own extensions Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

…s on both hops (#29872) Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

…nlyExtensionsOf; changeset (#29872) Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

…29872) Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

objectstack-fleet · 2026-11-03T16:43:17Z

domain:server#6 · os-support-ai · session_01WGufzibcN9oHa8kDbTTnL5

Contract review

Served-tier: TIER_DEFAULT
Head-sha: 7b1145ab6d56f676c27faefc9405b4c8df5cfdab
Local-runs: none

Face: declaration (Clause-②: yes (widening) on the PR body and changeset). No published schema and no governed path in the committed tree (9 files). Read: the full diff, card #29872 and its triage audit 6600517038, the seat's carrier note 6605292329, dev report 6609855338, and the per-package layer's other reader (packages/rest/src/form-routes.ts, views only).

① Derived judgments

Half 1, the extender's export: SchemaRegistry.getObjectExtensionsOf(packageId) reads each extend contribution back as its objectExtensions entry (extend = registry key, priority only when not the default 200, name and _-envelope keys dropped). assemblePackageManifest appends only entries whose target no object_extension item names, so a stored extension still exports as stored (metadata-protocol + objectql: an object extension is an authorable item of a writable package — saved and published through the existing doors, registered as 'extend', exported as objectExtensions #28574/packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 pins unchanged). A registry double without the method adds nothing. Second hop pinned byte-equal. Correct.
Half 2, the owner's export: the per-package layer now passes onlyExtensionsOf: <listed package> to both the registry list and the stored-row fold, so the owner's export folds no other package's extension (pair or not); one predicate (isLeftOutExtension) serves both options; the base layer (own/overlay) is never left out. Served and effective reads pass neither option. Correct, and it closes both halves of carrier note 6605292329.
withoutExtensionsOf kept: it is in the published @objectstack/objectql@18.3.0 dist; removing it would narrow a published surface. Kept with its meaning and its unit pin. Correct.
Ablations: red at all three seams (runtime integration + dogfood for half 1, the per-package layer through a dist-preflighted build for half 2, the registry clause), each restored to HEAD's blob.

② Semver level

'@objectstack/objectql': patch, '@objectstack/metadata-protocol': patch, '@objectstack/runtime': patch. New exported method, interface and optional option on SchemaRegistry ⇒ widening; Metadata-protocol: none ⇒ patch (AGENTS.md Post-Task Checklist step 3). Consistent with both declaration lines.

③ Boundary flags

No open_questions. Behaviour moves beyond the card on purpose, by the same rule: a code package's export now carries its manifest objectExtensions, and a platform-owned object's export no longer folds plugin extensions. Both follow ADR-0146 D8 item 3.
Dedupe compares an item's extend spelling to the registry key; a stored row spelling a legacy folded short name could export twice, but the save door refuses that spelling (metadata-protocol: an object_extension item's refusal sentences, row comment and folded target spelling misfit the item door #28834). Not filed.
The pending packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 changeset sentence this PR makes false is carried by a "Supersedes, in the same release" paragraph in this PR's changeset; check-empty-changeset guards the other note. Accepted.

Implemented-by: claude/project-thread-fh6dvf
Reviewed-by: session_01WGufzibcN9oHa8kDbTTnL5

VERDICT: PASS

objectstack-fleet · 2026-11-03T16:45:26Z

domain:server#6 · os-support-ai · session_01WGufzibcN9oHa8kDbTTnL5

席位核对

Verdict: ACCEPT at head 7b1145ab6d56f676c27faefc9405b4c8df5cfdab · 2026-11-03T16:44Z

Shape: 9 files (objectql registry, metadata-protocol per-package layer + fold, runtime export assembly + integration test, dogfood round trip, one changeset); no published schema, no governed path ⇒ not Tier H. Declaration face (Clause-②: yes (widening)): TIER_DEFAULT review PASS 6609898569 at this head.
Premise measured: the dev reproduced it on main 21510bba (an install-local extender exported no objectExtensions, and its field folded into the owner's export). Both halves of carrier note 6605292329 shipped together, which the acceptance notes show is required: half 1 alone stays green on the inventory pin.
Gates: objectql 10827, metadata-protocol 22320, runtime 8599 pass; typecheck x3 and eslint exit 0; dogfood round trip 13/13; dispatch-gates 67/67 exit 0 (dev report 6609855338). Ablations red at all three seams, restored. Landing waits for every check on this head to be green or an expected skip.
Accepted deviations: harness-pinned branch claude/project-thread-fh6dvf; body line 2 links the card thread (session attribution rule); the packages export: a read-only base's own export carries its .custom pair's object extension merged into the object, where ADR-0146 D8 item 3 says the base exports unchanged #29903 changeset note is superseded by a paragraph rather than edited (guarded by check-empty-changeset). The signed trailer was appended by the seat through the relay.
Landing: on all-green at this head, the seat sends pr_ready + automerge_enable through the relay.

github-actions · 2026-11-03T16:48:22Z

📓 Docs Drift Check

This PR changes 3 package(s): @objectstack/metadata-protocol, @objectstack/objectql, @objectstack/runtime, touching 16 documentable anchor(s).

5 hand-written doc(s) NAME something this change touched and may need an implementation-accuracy re-verification:

content/docs/concepts/metadata-lifecycle.mdx (via SchemaRegistry (symbol, a top-level class))
content/docs/deployment/environment-variables.mdx (via SchemaRegistry (symbol, a top-level class))
content/docs/kernel/services-checklist.mdx (via SchemaRegistry (symbol, a top-level class))
content/docs/plugins/adding-a-metadata-type.mdx (via SchemaRegistry (symbol, a top-level class))
content/docs/protocol/kernel/plugin-spec.mdx (via SchemaRegistry (symbol, a top-level class))

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

content/docs/releases/v17/17-4.mdx (via SchemaRegistry (symbol, a top-level class))

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

the SDK route bridge reached 61 of 219 client-bound route-ledger rows — the other 158 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 158: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 103 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 42 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 6a4737abae46e1d6847d7abfe430e5d62cd927f0 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 73273c8fd7765fd5e94580032b831b6c40df38c9 — the merge of head 7b1145ab6d56f676c27faefc9405b4c8df5cfdab into base 6a4737abae46e1d6847d7abfe430e5d62cd927f0, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin 73273c8fd7765fd5e94580032b831b6c40df38c9 && git checkout 73273c8fd7765fd5e94580032b831b6c40df38c9
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 6a4737abae46e1d6847d7abfe430e5d62cd927f0 7b1145ab6d56f676c27faefc9405b4c8df5cfdab && git checkout -B drift-repro 6a4737abae46e1d6847d7abfe430e5d62cd927f0 && git merge --no-ff 7b1145ab6d56f676c27faefc9405b4c8df5cfdab

node scripts/docs-audit/affected-docs.mjs --json 6a4737abae46e1d6847d7abfe430e5d62cd927f0

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

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 6a4737abae46e1d6847d7abfe430e5d62cd927f0 → pass the list as
args.docs, on the commit named under Which tree this was computed on.

claude added 5 commits November 3, 2026 15:57

wip(objectql, metadata-protocol, runtime): a package export carries i…

2933324

…ts manifest objectExtensions, and an owner export folds only its own extensions Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

test(dogfood): the install-local extender exports its objectExtension…

9cba7cb

…s on both hops (#29872) Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

fix(objectql): keep the published withoutExtensionsOf option beside o…

15cb79e

…nlyExtensionsOf; changeset (#29872) Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

chore(changeset): leave the pending #29903 release note as it stands (#…

2e498fb

…29872) Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

chore(changeset): name the #29903 note this change supersedes (#29872)

7b1145a

Claude-Session: https://claude.ai/code/session_01WGufzebqeaeGkaTWGnN9bm Co-authored-by: Claude <noreply@anthropic.com>

github-actions Bot added size/m documentation Improvements or additions to documentation tests tooling labels Nov 3, 2026

objectstack-fleet Bot mentioned this pull request Nov 3, 2026

fix(lint)!: a type mismatch in a record-triggered flow condition or an advisory validation rule is served a verdict that says what really happens #29953

Merged

objectstack-fleet Bot marked this pull request as ready for review November 3, 2026 17:34

objectstack-fleet Bot enabled auto-merge November 3, 2026 17:34

objectstack-fleet Bot added this pull request to the merge queue Nov 3, 2026

Merged via the queue into main with commit 3b8c724 Nov 3, 2026
53 of 54 checks passed

objectstack-fleet Bot deleted the claude/project-thread-fh6dvf branch November 3, 2026 18:14

github-actions Bot mentioned this pull request Nov 4, 2026

4-hourly full run: red on main (CI) #29494

Closed

Navigation Menu

Repository navigation

fix(objectql, metadata-protocol, runtime): a package's export carries the objectExtensions it was installed with, and the owner's export folds no other package's extension - #29948

fix(objectql, metadata-protocol, runtime): a package's export carries the objectExtensions it was installed with, and the owner's export folds no other package's extension#29948
objectstack-fleet[bot] merged 5 commits into
mainfrom
claude/project-thread-fh6dvf

objectstack-fleet Bot commented Nov 3, 2026 •

edited

Loading

Uh oh!

objectstack-fleet Bot commented Nov 3, 2026

Uh oh!

objectstack-fleet Bot commented Nov 3, 2026

Uh oh!

github-actions Bot commented Nov 3, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

objectstack-fleet Bot commented Nov 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

维护者速读

What changes

Tests

Acceptance notes

Verification

Uh oh!

objectstack-fleet Bot commented Nov 3, 2026

Contract review

① Derived judgments

② Semver level

③ Boundary flags

Uh oh!

objectstack-fleet Bot commented Nov 3, 2026

席位核对

Uh oh!

github-actions Bot commented Nov 3, 2026

📓 Docs Drift Check

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

objectstack-fleet Bot commented Nov 3, 2026 •

edited

Loading