Backport epic: downstream fixes + features from OpenClaw Workspaces and the Hermes plugin

[100yenadmin]

Boardstate's downstream deployments evolved after extraction: OpenClaw's in-tree Workspaces gained post-vendoring PRs (#101792 charts, #101354 secure preview, #101826 agent status + decisions, #109627 full-bleed tabs, community fix #108204) and the Hermes plugin shipped v1.0→v1.4 (operational-layer hardening + fixes). A systematic audit (every downstream change classified against library source; each backport claim independently adversarially verified with file:line citations) found 21 confirmed backports. This epic tracks them.

Security / trust boundary

• S1 — Secret redaction on agent-facing connector errors. BrokerToolError and connection errors propagate raw error.message (packages/broker/src/broker.ts:295, :239); spawn/HTTP failures embed commands/URLs. Port the Hermes plugin's redaction (config command/url/args/env values + nonce, longest-first, length-agnostic) into the broker error path.
• S2 — Invoke-time manifest-hash re-check on the direct readOnly path. The AND-gate runs at assembly time only (packages/server/src/broker-agent-tools.ts:236); a connector can swap a tool between assembly and execute. Re-verify the grant's toolsHash at invoke time on the direct-read path (mutations already re-check in the engine).
• S3 — Pin + size-cap custom-widget code at approval. Approval doesn't snapshot/pin what was reviewed and has no size cap (TOCTOU / OOM).
• S4 — workspace_replace can mint a fabricated pending registry entry for a name that was never scaffolded; validate registry entries against known scaffolds/installs.
• S5 — Bounded chart point count. No cap anywhere in the chart pipeline; agent-authored data can exhaust the renderer. (OpenClaw caps at 500 — openclaw#101792.)
• S6 — Review: custom-widget manifest binding scope. OpenClaw narrowed manifests to static-only bindings; the library still allows allowlisted rpc/jailed-file bindings from manifests. Decide + document the intended trust posture.

Correctness

• B1 — Overlapping-reload stale-clobber race in loadWorkspace (no ordering guard in packages/host/src/store.ts). Same race fixed downstream by community PR openclaw#108204 — port the newest-wins guard.
• B2 — nearestFreeSlot can return an out-of-range y that schema validation then rejects (packages/core/src/grid.ts).
• B3 — Bar/gauge axis doesn't force-include zero — bars are measured from the series minimum, misrepresenting magnitude.
• B4 — Distinguishable error state for malformed chart input. normalizeSeries/resolveType silently coerce bad input to defaults (packages/core/src/transforms/chart.ts:43-64); port OC's 3-state model (empty/error/ready) + role="status" invalid placeholder + i18n key (openclaw#101792).
• B5 — Re-register connector grants after a doc replace wipes capabilitiesRegistry. The wipe is legitimate document semantics, but nothing re-registers the connector-config-declared grants as requested afterward (the Hermes plugin needed a re-registration listener; template applies hit this).
• B6 — Validate pending-action timeout config (positive, finite; fail safe on garbage).
• B7 — Schema guard: at most one widget when layout: "full" is absent from validateTab.
• B8 — Duplicate-decision guard + reconcile-on-reload for widget approve/reject (openclaw#101826).
• B9 — Chart aria-label || fallback can emit an empty label (use ?? + real fallback).

Features / parity

• F1 — Chart props.min/props.max + numerically-stable degenerate/extreme-range handling (library yScale can hit Infinity at extreme finite values) — openclaw#101792.
• F2 — Binding-driven preview URL (bindings.value precedence over props.url) — openclaw#101354.
• F3 — Permission gate + "permission required" affordance on decision controls — openclaw#101826.
• F4 — Preview toolbar a11y: aria-pressed/aria-label/:focus-visible parity with the library's other pressed-state buttons.
• F5 — Chart aria-label reports observed point count/range, not just the title.
• F6 — CLI: dashboard tabs full/grid layout-toggle verbs (the schema + view already ship full-bleed).
• F7 — Cross-process single-writer guard for a shared state dir (two hosts/CLIs on one BOARDSTATE_STATE_DIR double-write today; the Hermes plugin's port-file adoption pattern is the reference).
• F8 — Fix the OfficeCLI docs/demo tool contract. docs/connectors/officecli.md + examples/operational-demo/fake-officecli.mjs model fictional tools (read_workbook/generate_document); the real officecli mcp exposes a single officecli tool taking {command}. Align docs + fixture (the Hermes plugin hit exactly this).

Verified NOT needing backport

Already upstream (often richer than downstream): full-bleed single-widget tabs; builtin:agent-status; the pending-approval queue/decision flow; sparkline + detail mode (OC's vendored sparkline is a no-op fall-through — the library is ahead there); preview core (URL gate/sandbox/viewports); event-driven binding invalidation. Platform-specific by design: Hermes' color(srgb) token mapping, operator-secret split, embed-policy wiring, tokenized asset route; OC's sandbox-ceiling tier, gateway RPC params. OC's six post-vendoring refactor/tooling commits contain no hidden behavior fixes.

Suggested trains: T1 security (S1-S6), T2 correctness (B1-B9), T3 parity (F1-F8) — one changeset release each.

[coderabbitai]

🔗 Related PRs

#20 - feat: networked WebSocket Transport + browser-standalone bundle (serve-host renders the board) [merged]
#53 - feat(server): grant lifecycle + pending-action engine — the M5 trust layer (M5b-2+M5b-3) [merged]
#57 - feat: OfficeCLI preset + aggregator recipes + live operational-demo host (M5e+M5f-1) [merged]
#65 - feat(chart): sparkline type + optional detail mode (#10, #4) [merged]
#70 - feat(trust): per-tool auto-confirm, grant TTLs, async pending actions (#62, #64, #63) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #77 - Backport epic: downstream fixes + features from OpenClaw Workspaces and the Hermes plugin
State: open

Related issues/PRs: #101792, #101354, #101826, #109627, #108204.
Existing labels: security, widget, mcp, agent-layer, roadmap.
Suggested labels: bug, docs, tests.
Suggested owners: none.

Related context

• #101792 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• #101354 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• #101826 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• #109627 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• #108204 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Backport epic: downstream fixes + features from OpenClaw Workspaces and the Hermes plugin - Boardstate's downstream deployments evolved after extraction: OpenClaw's in-tree Workspaces gained post-vendoring PRs (#101792 charts, #101354 secure preview, #101826 agent status + decisions, #109627 full-bleed
Product fit: Product/UX-sensitive issue; review against repo vision and user flow quality, not only technical P0/P1 risk.
Implementation wedge: Ship the smallest user-visible path or prototype that can be smoke-tested against the intended experience.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.
• Library choice: compare maintenance, API fit, license, bundle/runtime cost, and integration proof.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.
• Current market/product examples, capped and cited, only when they change implementation direction.

Acceptance criteria:

• Add explicit acceptance criteria before implementation is considered done.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• UX/product smoke or screenshot proof when implementation changes user flow.
• Contract or degraded-mode proof before runtime promotion.
• Dependency/license/API-fit note before adding or relying on a package.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• Owner or reviewer signal not detected in issue body.

No labels, owners, reviewers, or roadmap fields were changed by this bot.