Portback — port Act-1/Act-2 fixes upstream to OpenClaw

[100yenadmin]

Act-2 · Portback lane (parallel). Port fixes made here back to the OpenClaw dashboard (the extraction source):

1. stream-binding normalizer strip — verify OpenClaw's client normalizer has the same rpc/file/static-only bug that dropped stream/computed bindings (task chip pending), port the fix + regression if so.
2. browser-safe tools split (createDashboardCoreTools).
3. lift-and-carry drag UX.
4. reviewWorkspace / design-review tool.

Each as its own upstream PR; verify the bug exists upstream before porting.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #29 - Portback — port Act-1/Act-2 fixes upstream to OpenClaw
State: open

Related issues/PRs: none detected from issue metadata.
Existing labels: roadmap.
Suggested labels: bug.
Suggested owners: none.

Related context

• No same-repo issue/PR references detected in issue metadata.

Agent-start packet

Problem shape: Portback — port Act-1/Act-2 fixes upstream to OpenClaw - Act-2 · Portback lane (parallel). Port fixes made here back to the OpenClaw dashboard (the extraction source): 1. stream-binding normalizer strip — verify OpenClaw's client normalizer has the same
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.

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.

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: No explicit same-repo references detected; still safe as bounded local context.
• [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

• Acceptance criteria or validation evidence not detected in issue body.
• Owner or reviewer signal not detected in issue body.

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

[100yenadmin]

Status: item 1 resolved — no port needed (verified upstream's client normalizer does NOT have the stream/computed-binding strip; it was introduced during extraction here). The widget_update fix is ported as openclaw#15 (mergeable — failing checks there are that repo's bot/secret gates, not code; owner merges). Remaining: (2) browser-safe tools split, (3) lift-and-carry drag UX, (4) design-review tool. Keeping open to track those three.