Improve dashboard UX clarity for channel settings and dependencies

[builtbyrobben]

Summary\n- add clearer config help/docs for ambiguous channel fields (Allow Bots, Block Streaming, Capabilities, DM policy)\n- add dynamic dependency/risk notices with quick-fix actions for common channel misconfigurations\n- improve +Add UX for arrays/maps with contextual labels and key guidance\n- add Channels health callout recommending openclaw doctor and channels status --probe\n\n## Validation\n- pnpm --dir ui test src/ui/config-form.browser.test.ts src/ui/views/channels.config.test.ts src/ui/views/channels.shared.test.ts\n- pnpm exec vitest run src/config/schema.test.ts\n- pnpm --dir ui build\n- pnpm build\n- pnpm lint\n- pnpm test\n\n## Notes\n- pnpm check still has a pre-existing unrelated type error in src/telegram/bot.ts

Greptile Summary

Improved dashboard UX by adding comprehensive help text, dependency warnings, and contextual guidance for channel configuration. The changes introduce a robust impact tracking system that validates config dependencies and provides quick-fix actions for common misconfigurations.

Key improvements:

• Added 100+ field help entries with clear explanations for ambiguous settings (allowBots, blockStreaming, capabilities, DM policies)
• Implemented dynamic dependency/risk notices with actionable quick-fixes (e.g., open DM policy requiring allowFrom: ["*"])
• Enhanced array/map field UX with contextual labels and platform-specific placeholders (Discord guild IDs, Slack channel IDs)
• Added "Channels health" callout recommending openclaw doctor and openclaw channels status --probe
• Standardized channel headers with docs links derived from channel metadata
• Lazy-loaded LanceDB to prevent crashes on platforms without native module support

Test coverage:

• Added comprehensive browser tests for map guidance, fallback hints, and impact rendering
• New test suites for channel header rendering and config form validation
• Schema tests validate UI hint impacts and dependency logic

The PR successfully addresses configuration clarity issues while maintaining backward compatibility.

Confidence Score: 4/5

• Safe to merge with one workflow condition issue noted
• Well-tested UX improvements with comprehensive test coverage. The only concern is the labeler workflow condition checking secrets.GH_APP_PRIVATE_KEY in the if statement, which won't work as expected. Otherwise, the changes are clean, well-structured, and thoroughly validated.
• .github/workflows/labeler.yml requires fix for secret availability check

Important Files Changed

Filename	Overview
src/config/schema.ts	Added comprehensive field help text, UI hints for channel config, and impact/dependency tracking system for config validation
ui/src/ui/views/config-form.shared.ts	Implemented fallback UI hints, impact resolution logic, and dynamic dependency checking for channel configurations
ui/src/ui/views/config-form.node.ts	Enhanced map field guidance, array item labels, and contextual placeholders for channel-specific config fields
ui/src/ui/views/channels.shared.ts	Added channel metadata resolution helpers and standardized channel header rendering with docs links
ui/src/ui/views/channels.ts	Added health callout with doctor/probe recommendations, collapsed raw data behind details, improved header layout
extensions/memory-lancedb/index.ts	Lazy-loaded LanceDB import to prevent missing native module errors on unsupported platforms
.github/workflows/labeler.yml	Updated job conditions to check secret availability before execution
ui/src/styles/config.css	Added styles for impact callouts, section headers, config field docs links, and improved form layout

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User edits config field] --> B[hintForPath resolves UI hints]
    B --> C{Fallback hints exist?}
    C -->|Yes| D[Merge backend + fallback hints]
    C -->|No| E[Use backend hints only]
    D --> F[resolveConfigImpacts]
    E --> F
    F --> G{Check impact conditions}
    G -->|when=truthy/equals/etc| H{Source value matches?}
    H -->|Yes| I{Has target path?}
    H -->|No| K[Skip impact]
    I -->|Yes| J{Check target value}
    I -->|No| L[Render risk notice]
    J -->|Mismatch| M[Render requires/conflicts notice]
    J -->|Match| K
    L --> N[Display with quick-fix button]
    M --> N
    N --> O{User clicks fix?}
    O -->|Yes| P[onPatch with fixValue]
    O -->|No| Q[User manually edits]
    P --> R[Config updated]
    Q --> R

Loading

_{Last reviewed commit: 9506db5}

[greptile-apps]

_{7 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

secrets.GH_APP_PRIVATE_KEY reference won't work in if condition

Suggested change

	if: github.repository_owner == 'openclaw' && secrets.GH_APP_PRIVATE_KEY != ''
	if: github.repository_owner == 'openclaw'

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/labeler.yml
Line: 13:13

Comment:
`secrets.GH_APP_PRIVATE_KEY` reference won't work in `if` condition

```suggestion
    if: github.repository_owner == 'openclaw'
```

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

_{48 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Condition won't work as intended. Secrets aren't available in if conditions — they're always empty strings in workflow expressions. This check will always evaluate to false on forks.

Suggested change

	if: github.repository_owner == 'openclaw' && secrets.GH_APP_PRIVATE_KEY != ''
	if: github.repository_owner == 'openclaw'

The secret availability will be enforced when the step tries to use it.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/labeler.yml
Line: 13

Comment:
Condition won't work as intended. Secrets aren't available in `if` conditions — they're always empty strings in workflow expressions. This check will always evaluate to false on forks.

```suggestion
    if: github.repository_owner == 'openclaw'
```

The secret availability will be enforced when the step tries to use it.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Same issue — secret check in if won't work.

Suggested change

	if: github.repository_owner == 'openclaw' && secrets.GH_APP_PRIVATE_KEY != ''
	if: github.repository_owner == 'openclaw'

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/labeler.yml
Line: 52

Comment:
Same issue — secret check in `if` won't work.

```suggestion
    if: github.repository_owner == 'openclaw'
```

How can I resolve this? If you propose a fix, please make it concise.