doc: add assistant_view in features

[insomnius]

Summary

Add assistant_view in sample manifest

• Problem: Slack required assistant_view listed in features so that we can use of assistant:write oauth scope
• Why it matters: it matters so that assistant:write oauth access can be used
• What changed: adding assistant_view in list of features
• What did NOT change (scope boundary): -

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

Not applicable

Root Cause (if applicable)

For bug fixes or regressions, explain why this happened, not just what changed. Otherwise write N/A. If the cause is unclear, write Unknown.

• Root cause: assistant_view feature should be listed when assistant:write is in oauth scope
• Missing detection / guardrail:
• Contributing context (if known):

Regression Test Plan (if applicable)

Not applicable

User-visible / Behavior Changes

No behavior changes

Diagram (if applicable)

Not applicable

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No
• If any Yes, explain risk + mitigation: No

Repro + Verification

Not applicable

Evidence

Not applicable

Human Verification (required)

I verified by creating an app with the manifest I just changed, and it doesn't show any warning

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Migration needed? No
• If yes, exact upgrade steps: No

Risks and Mitigations

No risk

[greptile-apps]

Greptile Summary

This PR adds the assistant_view feature block to the Slack app manifest examples in docs/channels/slack.md for both Socket Mode and HTTP Request URL variants. The change is needed because Slack requires assistant_view to be declared in features when the assistant:write OAuth scope is used, preventing a validation warning when creating the app from the manifest.

Confidence Score: 5/5

Safe to merge — docs-only change that adds a required Slack manifest field, verified by the author.

Single documentation change adding a missing manifest field consistently across both manifest variants. No logic, no code, and the author confirmed it resolves the Slack validation warning.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Add assistant_view in features" | Re-trigger Greptile}

[zimeg]

👋 Hey @insomnius! Thanks for taking note of this! 👾

We're aware that these warnings appear in Slack app settings at the moment, but we're holding off on this feature for now with some considerations to the current default experience across the Slack UI.

AFAICT the warning shouldn't cause problems in interactions that use the recommended defaults but please let me know of other findings! 🔭