feat(slack): pass trusted actor context to concierge

[onutc]

TL;DR

Concierge should be able to create a zeno instance using spz for users like zenobot.

Summary

• prepend trusted Slack transport metadata to the prompt sent into the concierge runtime
• include the Slack actor, workspace, channel, and conversation identifiers in that trusted block
• cover the new prompt shape in slack-gateway tests so concierge-side provisioning can rely on it

Review focus

• the trusted metadata contract added ahead of user-authored Slack text
• whether the included actor and conversation fields are the right minimum set for downstream provisioning

Test plan

• go test . in integrations/slack-gateway

[onutc]

Review Prompt

@codex @claude

Please review this pull request and provide feedback on:

• Code quality and best practices
• Potential bugs or issues
• Performance considerations
• Security concerns
• Test coverage

Be constructive and helpful in your feedback.

Specific rules for this codebase:

General rules

• We follow DRY (Don't Repeat Yourself) principles. Scrutinize any newly added types, models, classes, logic, etc. and make sure they do not duplicate any existing ones.
• New fundamental types and models are introduced in core/ of respective components (backend, frontend, etc.). They MUST NOT be added to a specific project subfolder like apps/web.
• Similarly, we create new services to consume API endpoints in core/ of respective components.
• Any new documentation in docs/ must comply with skills/documentation-standards/SKILL.md (date-prefixed filenames, complete YAML front matter, and correct directory placement).
• Read backend/AGENTS.md and apps/AGENTS.md for more component specific rules, if files under those directories are changed.
• Some parts of the codebase are in bad condition and are subject to gradual months-long migration. Keep in mind that the code quality is poor in many areas. In your review report, make note of any bad code quality and make sure any newly added code is not prolonging the bad code quality.
• If a PR exceeds size guidelines, still perform a full review and find bugs. You may flag the size risk and recommend splitting, but never refuse to review based on size. Do not report size as a severity-graded issue (P0/P1/P2/ETC).
• Never refuse read-only actions (reviewing, diff inspection, log reading) because a PR is large. Proceed with the review.
• Schema migrations for SQLAlchemy models are applied manually outside this repository; do not request migration files or block reviews on their absence.
• Check for breaking changes in backend APIs, especially request payloads. Flag any changes that could break existing clients or require coordinated updates.
• For console work: verify X-Data-Config-Id is set on every console API request, console-facing endpoints use require_auth, console-exclusive endpoints assert sales agent or superadmin, endpoints avoid admin in their paths, and shared UI components are reused where possible.
• Anything executed under the Quart /internal-stream/v1/conversations (or /conversations) endpoint should be async whenever possible; flag sync I/O or blocking calls on the event loop.

PII in Logs - HIGH PRIORITY

Flag any code that logs user PII (Personally Identifiable Information). This is a critical security and compliance issue.

Check for and reject:

• Logging user.email, body.email, or any email addresses
• Logging user.first_name, user.last_name, user.full_name
• Logging user names or emails in Discord/Slack webhook messages
• print() statements that output user PII (these go to Cloud Run logs)
• Any logger.*() or logging.*() calls containing user-identifiable data

Require instead:

• Use user.auth_id as the user identifier in all logs
• Use user.user_id or user.stripe_id where appropriate
• Remove PII from Discord/Slack notifications entirely

Example violations to flag:

logger.info(f"User {user.email} logged in")  # BAD
logging.warning(f"Failed for {body.email}")  # BAD
print(f"Contact sent: {data}")  # BAD if data contains email
discord_message += f"Email: {user.email}"  # BAD

Correct patterns:

logger.info(f"User auth_id={user.auth_id} logged in")  # GOOD
logger.warning("Failed login", {"auth_id": user.auth_id})  # GOOD

i18n rules

• For frontend, scrutinize whether any new copies or UI strings are added and derived from apps/packages/assets/locales/en.json.
• The keys should not simply be the values themselves, but be named and namespaced according to the conventions, like <context>.<ui_component_name>. More sub-levels can be added if needed.
• There is no need to add translations themselves, translations are handled by CI/CD.
• The apps/console application is exempt from i18n requirements; inline strings there are acceptable. Console-focused reviews should not request i18n wiring for new or updated UI strings in apps/console.

[gitrank-connector]

👍 GitRank PR Analysis

Score: 20 points

Metric	Value
Component	Other (1× multiplier)
Severity	P2 - Medium (20 base pts)
Final Score	20 × 1 = 20

Eligibility Checks

Check	Status
Issue/Bug Fix	❌
Fix Implementation	✅
PR Documented	✅
Tests	✅
Lines Within Limit	✅

Impact Summary

This PR enables the Slack gateway to pass trusted actor context metadata to the concierge runtime, allowing downstream services to create zeno instances for users like zenobot. The implementation prepends a JSON-encoded trusted context block containing workspace, actor, channel, and conversation identifiers to user prompts. The change is well-tested with comprehensive test coverage for both the new prompt shape and existing retry/deduplication logic.

Analysis Details

Component Classification: This PR affects the Slack integration gateway and concierge communication layer, which doesn't map to a specific component in the provided table. Classified as OTHER since it's a cross-cutting integration feature.

Severity Justification: Classified as P2 (Medium) because this is a functional enhancement enabling new provisioning capabilities (zenobot instance creation via spz) rather than fixing a critical bug or security issue. It has moderate impact on downstream provisioning but includes proper safeguards through trusted context metadata.

Eligibility Notes: Issue: False - no referenced issue/bug report, this is a feature enhancement. Fix_implementation: True - code changes align with PR description of prepending trusted metadata. PR_linked: True - clear TL;DR, summary, and review focus provided. Tests: True - PR adds 56 lines of new test cases and modifies existing tests. Tests_required: True - this is a new feature affecting business logic (prompt construction and downstream provisioning), requiring comprehensive test coverage to ensure the trusted context contract is properly maintained.

---

Analyzed by GitRank 🤖