Phase 1: Assess CoffeeScript codebase & identify critical paths

[jessefreeman]

Scope:
Audit all .coffee files, count, map directories, and flag critical runtime paths (server core, API, DB, session).

Key Actions:

• Inventory CoffeeScript sources (count & list)
• Classify by subsystem (db, session, api, build, content, forum, relay, filestorage, frontend)
• Mark high-risk (startup / request path) files
• Produce baseline metrics (file count, LOC) for later progress tracking

Acceptance Criteria:

• Markdown report committed (docs/ts-migration/01-audit.md)
• List of critical path files referenced in subsequent issues
• Baseline metrics recorded in report

Deliverables:

• Audit report file
• Updated master migration doc with issue links (done in later doc update pass)

Risks & Mitigation:

• Hidden CoffeeScript in unexpected dirs → use recursive find
• Generated artifacts mistaken for source → filter by *.coffee only

[jessefreeman]

Parent epic: #6