Skip to content

fix(v2.3.1): typed session status, HTTP 500 on DB errors, README sync#12

Merged
ek33450505 merged 1 commit into
mainfrom
fix/v2.3.1-readme-followup
May 18, 2026
Merged

fix(v2.3.1): typed session status, HTTP 500 on DB errors, README sync#12
ek33450505 merged 1 commit into
mainfrom
fix/v2.3.1-readme-followup

Conversation

@ek33450505
Copy link
Copy Markdown
Owner

Summary

  • Type fix: sessions.ts SessionWithStatus type extension replaces as unknown as Record<string, unknown> double-cast
  • Error responses: completenessEvents, codeRefChecks, fileWrites routes now return HTTP 500 on caught exceptions (consistent with costSummary.ts; previously returned HTTP 200 with empty payload)
  • README: Version badge updated to v2.3.1; pages table expanded to 11 pages; agent count updated to 33; new API routes documented; DB tables section updated; System tab description updated
  • Version: Bumped package.json to v2.3.1

Test plan

  • npx tsc --noEmit passes clean
  • GET /api/sessions — response includes status field on sessions with DB fallback data
  • GET /api/completeness-events?limit=abc — returns HTTP 500 (not HTTP 200 empty)
  • README renders correctly on GitHub — version badge shows 2.3.1, all 11 pages listed

🤖 Generated with Claude Code

TypeScript route handlers now return HTTP 500 on caught DB errors instead of silent failures. SessionWithStatus type eliminates double-cast pattern in sessions.ts. README updated to reflect v2.3.1 release: version bump, 33 agents, 11 dashboard pages, new API routes, and full DB table inventory.

Co-Authored-By: Claude <noreply@anthropic.com>
@ek33450505 ek33450505 merged commit 166a751 into main May 18, 2026
1 check passed
@ek33450505 ek33450505 deleted the fix/v2.3.1-readme-followup branch May 18, 2026 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant