Dependency Guard

This PR changes dependency-related files. Maintainers should confirm these changes are intentional.

Changed files:

• extensions/workboard/package.json
• packages/workboard-contract/npm-shrinkwrap.json
• packages/workboard-contract/package.json
• pnpm-lock.yaml
• ui/package.json

Maintainer follow-up:

• Review whether the dependency changes are intentional.
• Inspect resolved package deltas when lockfile, shrinkwrap, or workspace dependency policy changes are present.
• Treat package-lock.json and npm-shrinkwrap.json diffs as security-review surfaces.
• Run pnpm deps:changes:report -- --base-ref origin/main --markdown /tmp/dependency-changes.md --json /tmp/dependency-changes.json locally for detailed release-style evidence.

Dependency graph changes are blocked

OpenClaw does not accept dependency graph changes through PRs unless a repository admin or security explicitly authorizes the current head SHA. Dependency updates are generated internally by maintainers so external PRs cannot change the resolved graph.

Detected dependency graph changes:

• packages/workboard-contract/npm-shrinkwrap.json changed.
• pnpm-lock.yaml changed.
• extensions/workboard/package.json changed devDependencies.
• packages/workboard-contract/package.json changed name, version.
• ui/package.json changed dependencies.

Auto-scrub was not attempted because this PR changes package manifest dependency graph fields:

• extensions/workboard/package.json changed devDependencies.
• packages/workboard-contract/package.json changed name, version.
• ui/package.json changed dependencies.

Dependency graph changes must be reviewed by security or handled by maintainers internally. Please remove lockfile changes manually if they are not needed.

To remove lockfile changes, restore them from the target branch:

git fetch origin
git checkout 'origin/main' -- 'packages/workboard-contract/npm-shrinkwrap.json' 'pnpm-lock.yaml'
git commit -m 'chore: remove dependency lockfile change'
git push

If this PR intentionally needs a dependency graph change, ask a repository admin or member of @openclaw/openclaw-secops to comment:

/allow-dependencies-change

The action will approve the current head SHA (f9430b27668907fe1020479468ca2d66ac2f8a25) when it reruns. A later push requires a fresh approval.

Codex review: needs maintainer review before merge. Reviewed July 10, 2026, 12:44 PM ET / 16:44 UTC.

Summary
The PR moves the Workboard data model into private @openclaw/workboard-contract, migrates plugin and Control UI consumers, updates package/build/test resolution, and adds metadata-preservation coverage.

PR surface: Source -115, Tests +76, Config +15, Other +11. Total -13 across 27 files.

Reproducibility: yes. at source level: current main has separate Workboard plugin and Control UI contract inventories, and the PR's focused regression test covers concrete plugin-owned fields that the UI copy currently drops.

Review metrics: 1 noteworthy metric.

• Resolved dependency graph: 0 added, 0 removed, 0 changed packages. The supplied Testbox report indicates workspace-only importer and package metadata changes, focusing review on ownership and exact-head authorization rather than third-party updates.

Stored data model
Persistent data-model change detected: vector/embedding metadata: ui/src/pages/workboard/data.test.ts. Confirm migration or upgrade compatibility proof before merge.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #102258
Summary: This PR is the candidate implementation for the Workboard portion of the canonical contract-correctness umbrella issue; the channel-status PR is a separate workstream from the same audit.

Members:

• canonical: refactor: canonicalize correctness-critical UI and channel contracts #102258 - The issue explicitly requests a supported Workboard package seam consumed by Control UI.
• adjacent_distinct: refactor(channels): separate status output from snapshot input #102272 - That PR handles the independent channel-status input/output contract boundary.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🦞 diamond lobster
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• Refresh the draft against current main and rerun focused exact-head proof.
• Obtain admin or secops dependency authorization for the refreshed SHA.

Risk before merge

• [P1] The current head is a draft and behind main; any refresh changes the exact SHA and requires the focused Workboard, bundle, UI build, and boundary proof to be rerun.
• [P1] The workspace manifests, shrinkwrap, and lockfile cannot merge until an authorized admin or secops reviewer approves the exact refreshed head.
• [P1] The shared contract contains claim metadata, so future edits must continue routing client responses through the established Gateway token-redaction boundary.

Maintainer options:

1. Refresh, re-prove, and authorize (recommended)
   Update the draft to current main, rerun the focused package, Workboard, and UI checks, then grant dependency approval for that exact head.
2. Pause if the package owner is undesired
   Do not merge this branch if maintainers prefer a different canonical Workboard contract seam.

Next step before merge

• No automated repair is indicated; a maintainer should refresh the protected draft and an authorized admin or secops reviewer must approve the exact dependency head.

Maintainer decision needed

• Question: After the draft is refreshed onto current main, should an admin or secops reviewer authorize the exact workspace package and lockfile changes for @openclaw/workboard-contract?
• Rationale: The implementation is technically sound, but repository policy reserves intentional dependency-graph authorization for an approved human reviewer on the exact SHA.
• Likely owner: steipete — The feature history identifies this account as the primary owner of the Workboard contract and most major expansions, making it the strongest available routing candidate for the package-boundary decision.
• Options:
  • Authorize the refreshed head (recommended): Approve the exact SHA after confirming the dependency report remains workspace-only and the focused Workboard and bundling proof is green.
  • Reject this package seam: Keep the canonical issue open and choose another supported owner boundary if maintainers do not want the private workspace package.

Security
Cleared: The patch adds no resolved third-party package dependency, preserves Gateway replacement of actual claim secrets with [redacted], and introduces no concrete security or supply-chain regression.

Exact-head verification for 0d4547531bf763aad4f3e7ff9cf106df05ce04a6:

• Testbox-through-Crabbox tbx_01kx1ayeeq603djks62f5gevcb: 181 Control UI Workboard tests passed.
• Testbox-through-Crabbox tbx_01kx1ayeeq603djks62f5gevcb: 6 Workboard gateway tests passed.
• Testbox-through-Crabbox tbx_01kx1ayeeq603djks62f5gevcb: pnpm ui:build passed.
• Fresh Testbox-through-Crabbox tbx_01kx1b9w1t57v2epzzqmzn54nx: explicit path-scoped pnpm check:changed passed, including TSGo, oxlint, shrinkwrap guards, runtime-sidecar checks, and import-cycle validation.
• Codex autoreview (gpt-5.5, high): clean with no accepted/actionable findings.
• Dependency change report on Testbox tbx_01kx1ga0ayakq2ryd3z3x06b9p: 0 added, 0 removed, and 0 changed resolved packages. The dependency-file changes are only the Workboard package export, the Control UI workspace dependency, and the matching lockfile importer link.

The remaining dependency-guard failure is the expected policy gate for this intentional workspace dependency. An admin or @openclaw/openclaw-secops member must comment /allow-dependencies-change for this exact head. No merge or automerge has been requested.

Exact-head verification for f92300a45c26b0c1aaf069d4f29a36cd43403416:

• Fixed the CI boundary finding by moving the shared declaration surface to private package @openclaw/workboard-contract, outside the bundled plugin source graph.
• Workboard keeps the contract as a development/build dependency, while tsdown.config.ts explicitly inlines it into bundled runtime output so it does not leak into plugin runtime dependency metadata.
• Testbox-through-Crabbox tbx_01kx1kvvwpn5j0jgqd8v3nmeks: targeted Workboard bundled build passed; emitted dist/extensions/workboard contains no external @openclaw/workboard-contract import and includes the contract declarations/constants.
• Fresh Testbox-through-Crabbox tbx_01kx1kzrzh7d0rw0chcrbcrfqg: explicit path-scoped check:changed passed in 7m30.817s, including supply-chain/lock checks, all shrinkwrap guards, TSGo, oxlint, runtime-sidecar checks, A2UI sync, and import-cycle validation.
• Earlier focused proof remains green: 251 Control UI Workboard tests, 6 Workboard gateway tests, and pnpm ui:build.
• Fresh Codex autoreview (gpt-5.5, high): clean with no accepted/actionable findings after the runtime metadata and bundling corrections.

The intentional workspace dependency/lockfile importer changes still require exact-head dependency approval from an admin or @openclaw/openclaw-secops member via /allow-dependencies-change. No merge or automerge has been requested.

Exact-head CI correction pushed as 53f851b45e34c4ad9df1ac5813ef96fdd06a9c59:

• Fixed checks-fast-contracts-plugins-b by keeping extensions/xai/tsconfig.json derived from the shared extension package-boundary map after adding @openclaw/workboard-contract.
• Focused Testbox tbx_01kx1myghm63834y3y7hctwbpp: extension-package-project-boundaries.test.ts passed, 8/8 tests.
• Fresh Testbox tbx_01kx1n1czk64ma2cp72mqbh89k: path-scoped check:changed -- extensions/xai/tsconfig.json passed in 5m13.861s.
• Fresh Codex autoreview (gpt-5.5, high): clean.

The dependency approval policy gate remains the only known external authorization requirement. No merge or automerge has been requested.

@clawsweeper re-review

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Land-ready verification complete for f9430b27668907fe1020479468ca2d66ac2f8a25.

• Rewrote the branch on current Workboard contracts. The private @openclaw/workboard-contract package now owns the shared model; plugin internals and Control UI consume it.
• Preserved workspace provenance/access, claim state, diagnostic actions, and notification sequence values. Unsupported diagnostic/notification variants are rejected rather than coerced.
• AWS Crabbox run_0f9b3d099eb4: pnpm test ui/src/lib/workboard/index.test.ts ui/src/pages/workboard/view.test.ts extensions/workboard/src/gateway.test.ts — 258 tests passed.
• AWS Crabbox run_9be895fcc578: node scripts/run-tsgo.mjs -b tsconfig.projects.json — passed.
• pnpm ui:build and git diff --check — passed.
• Hosted CI run 29321373347 — passed, including UI, build, types, lint, docs, package boundaries, and full test shards.
• Fresh latest-main autoreview — no accepted/actionable findings.

Known proof gap: no screenshot, because this is an internal contract refactor with no intended rendered UI change.

Merged via squash.

• Prepared head SHA: f9430b27668907fe1020479468ca2d66ac2f8a25
• Landed commit: 561cf56c535287a8c7d12bb89b657ea891a4b98b