chore: add scaffold for post-debate reasoning analysis module

[SoorejS]

This PR introduces a non-invasive scaffold for a future post-debate reasoning analysis system.

What this includes:

• New internal package: backend/internal/analysis
• PostDebateAnalyzer interface
• FallacySignal and AnalysisResult types
• Documentation outlining intended future extensions

Important:

• No existing debate flow is modified
• No database changes
• No performance impact
• No external dependencies added

This lays the groundwork for future PRs that will introduce:

• Fallacy detection signals
• Explainable reasoning feedback
• Post-debate coaching improvements

Summary by CodeRabbit

• Chores
  • Internal infrastructure scaffolding added to support future debate analysis and reasoning diagnostics capabilities. No changes to existing functionality or user-visible features in this release.

[coderabbitai]

📝 Walkthrough

Walkthrough

Introduces scaffolding for a post-debate analysis module with no runtime changes. Adds interface definitions and data structures for future reasoning diagnostics, including conceptual foundations for detecting reasoning issues during debates.

Changes

Cohort / File(s)	Summary
Analysis Module Scaffolding backend/internal/analysis/README.md, backend/internal/analysis/analysis.go, backend/internal/analysis/types.go	Establishes foundational structure for post-debate analysis: documentation overview, PostDebateAnalyzer interface with Analyze method, and FallacySignal and AnalysisResult data structures for capturing reasoning diagnostics.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A burrow is built, not by magic or chance,
With interfaces and types—the foundation's advance!
No logic just yet, just the structural ground,
Where future insights and diagnostics are bound. 🏗️✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: add scaffold for post-debate reasoning analysis module' accurately and concisely describes the PR's main change: introducing a foundational scaffold for future post-debate analysis functionality without runtime impact.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

backend/internal/analysis/analysis.go (1)

5-7: transcript interface{} is an untyped contract — consider introducing a Transcript type.

Even for scaffold code, having the sole interface method accept a bare interface{} means future implementors and callers get zero compile-time guidance on what a "transcript" looks like. Defining a minimal placeholder type now (e.g., in types.go) would make the contract self-documenting and prevent a breaking API change later when the real type is introduced.

At a minimum, prefer any over interface{} for modern Go (1.18+).

♻️ Suggested approach

Add to types.go:

// Transcript is a placeholder for structured debate transcript data.
type Transcript struct {
	// TODO: define fields as implementation progresses
	Raw string
}

Then update the interface:

 type PostDebateAnalyzer interface {
-	Analyze(transcript interface{}) (*AnalysisResult, error)
+	Analyze(transcript Transcript) (*AnalysisResult, error)
 }

If a concrete type is premature, at least switch to any:

-	Analyze(transcript interface{}) (*AnalysisResult, error)
+	Analyze(transcript any) (*AnalysisResult, error)

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[SoorejS]

Hi @bhavik-mangla 👋

Just following up on this PR when you get a chance.
Would appreciate your feedback whenever convenient.

Thanks!