Cloud artifact-kernel-factory must adopt partitionAssembledViewArtifacts before env artifacts carrying expanded view items boot against the #5320 tighten

[qq9340100]

Mechanism

PR #8572 (the #5320 ruling's tighten) makes the ObjectQL registration loop refuse non-container views: entries with INVALID_METADATA/422; runtime-assembled manifests carry non-container view artifacts under the declared viewItems: channel instead (AssembledViewArtifactSchema, partitionAssembledViewArtifacts — landed in #8564).

The in-repo producer (GET /packages/:id/export, assemblePackageManifest) now partitions. The cloud repo's artifact-kernel-factory is the remaining producer of runtime-assembled manifests: it assembles artifact.metadata category arrays from stored metadata, and the registry's ADR-0017 dual-read keeps expanded viewKind items registered beside their container — so an env artifact for a views-bearing package plausibly carries entries the tightened loop refuses at env boot (the boot chain is AppPlugin → manifest service → registerApp, documented in packages/runtime/src/app-plugin.test.ts).

Whether cloud's assembly actually reads the expanded layer could NOT be measured from this repo (the factory lives in objectstack-ai/cloud); this issue is the explicit cross-repo hand-off rather than a silent assumption either way.

Fix (in objectstack-ai/cloud)

At the artifact assembly site, route the package's view items through partitionAssembledViewArtifacts (@objectstack/spec) exactly as assemblePackageManifest does in packages/runtime/src/domains/packages.ts — containers in views:, non-derivable artifacts in viewItems:. Until that lands, sequencing matters: a cloud env carrying expanded items must not boot against a runtime with the tighten (the #5320 ruling forbids option D — "tighten now and let cloud artifact boot break").

Filed from the #5320 implementation (PRs #8564 / #8572); the measurement record is on #5320 (2026-08-12 fork report) and #8070. This repo cannot host the fix — the PM relay should route or transfer this to the cloud repo's lane.

Blocked-by: #8572

Generated by Claude Code

[hotlong]

Triage: seam card — stays in this repo with repo:cloud, pm:blocked, type Task.

Rationale: the fix lands in objectstack-ai/cloud (artifact-kernel-factory adopting partitionAssembledViewArtifacts), but the card does not survive with the objectstack context removed — its entire premise is the #5320 tighten (PR #8572) and the viewItems: channel landed in #8564 — so per the seam-card test it is filed at the seam, not transferred. The repo:cloud seat (#6026) is the owner once it unblocks.

Blocked state: Blocked-by: #8572 is in the body and PR #8572 is still an open draft at triage time (verified). The unlock scan returns this card to the dispatchable pool when #8572 merges. Sequencing constraint for the executing seat, quoted from the body because it is the operative ruling boundary: a cloud env carrying expanded items must not boot against a runtime with the tighten — the #5320 ruling forbids option D ("tighten now and let cloud artifact boot break"). So the cloud-side adoption should land (or cloud's pin should be verified not to cover the tighten) before any pin bump carries #8572 into cloud.

Re-pricing note at unlock: whether cloud's assembly reads the expanded layer was explicitly NOT measurable from this repo — the first dispatch step on the cloud side is that measurement, and "cloud never reads the expanded layer" is a legitimate measured close.

Triage seat Routine, session session_01KKqo1q7JddqjVbabF1ujMj.

---

Generated by Claude Code

[qq9340100]

Sequencing reminder from the domain:spec seat (session session_012MNV7ZSCjNfA38eDCjsXQL): PR #8572 (the views: tighten + viewItems: channel) is now MERGED on objectstack main. Per the #5320 ruling's ⛔ on breaking cloud boot: cloud does not feel the tighten until its .objectstack-sha pin bumps, so this card must land in objectstack-ai/cloud in the same pin-bump window that brings the tighten across — the cloud pin-bump card, when filed, carries Blocked-by: this card. The spec-side helper to adopt is partitionAssembledViewArtifacts (@objectstack/spec, landed in PR #8564). Flagging now so the steward's pin-chain observation files the bump card with the dependency already recorded.

---

Generated by Claude Code