Investigate LLMTopic configuration error for issue_root_cause_coaching (POST /ai/coaching/start)

[mottych]

Context

From PurposePath_Web #867: on dev (dev.purposepath.app/operations/issues), Resolve with AI calls:

• POST /ai/coaching/start with topic_id: "issue_root_cause_coaching" and context: { issue_id: "<traction issue id>" } (aligned with OpenAPI PurposePathCoachingStartContext__issue_root_cause_coaching).

The reported failure was an LLMTopic configuration style error referencing that topic id.

Ask

1. Confirm LLMTopic (or equivalent runtime config) in dev includes a valid row for issue_root_cause_coaching (model, prompts, limits) and matches the topic registry / OpenAPI entry.
2. If the row is missing or mis-keyed, add or fix seeding/deployment so conversation coaching can start for this topic.
3. Prefer a clear, stable error code (or machine-readable field) for "topic not configured" so the web client can surface actionable copy if misconfiguration happens again.

References

• Web: ResolveIssueWithAiModal → CoachingConversationModal → apiClient.startCoachingSession.
• Dev OpenAPI lists issue_root_cause_coaching under x-purposepath-topic-contracts as conversation_coaching / category strategic_planning.

Related

• Legacy /api/operations/* migration: PurposePath_Web #868.

[mottych]

Opened from PurposePath_Web #867 (now closed). Legacy /api/operations/* cleanup on the web app: #868.

[mottych]

Work in progress (#327)

Understanding: \issue_root_cause_coaching\ is in \TOPIC_REGISTRY\ and \ opic_seed_data.py, but coaching start loads LLMTopic from DynamoDB. Dev deploy workflows ran Pulumi only and never ran \python -m coaching.src.scripts.seed_topics, so new topics could be missing in \purposepath-topics-{stage}.

Changes (this PR):

1. CI/CD: After each coaching deploy, seed topics (creates missing rows; no --force-update\ so existing admin tweaks stay) on dev, staging, and prod.
2. API: \InvalidTopicError\ now carries \�rror_code. Missing DynamoDB row → \TOPIC_NOT_CONFIGURED\ (plus \ opic_id\ in JSON detail). Unknown topic id in registry → \INVALID_TOPIC\ (unchanged default).

Validation: ruff + mypy on touched modules; pytest unit + integration for start-session error paths.