v0.8.1-beta: Stabilization, UX Polish & Upgrade Safety

[DeepZone]

Motivation

• Stabilize the v0.8.x beta line by adding end-to-end workflow coverage, polishing UX for Change Cases / Watch Mode / check forms, and making upgrade/migration state clearer and actionable for operators.

Description

• Added an end-to-end backend test that walks a full Change Case workflow (create case → BGP visibility → ROA preflight → create Watch Target → run Watch Target → validate WatchRun, reports and audit events) and asserts audit events are present.
• Ensured Change Case reports are returned newest-first and improved report attachment audit events and report generation logging.
• Improved system/migration visibility by exposing current schema/head revision and adding explicit Alembic guidance when the DB is behind (alembic current, alembic heads, alembic upgrade head), plus a documented SQLite/dev-mode note about Base.metadata.create_all() vs Alembic stamping in docs/operations/upgrades.md.
• Frontend UX polish: added Run Due Watches button and run-due summary, newest-first run history, visual highlight for changed runs, report-id links from run history, consistent status badges and clearer empty/loading/error states across ChangeCasesView and WatchModeView, and bumped UI version strings to v0.8.1-beta.
• Bumped package/project version references to 0.8.1 / v0.8.1-beta, updated README/ROADMAP/RELEASE_NOTES with the release rationale and known limitations.

Testing

• Backend tests: ran cd backend && pytest -q and fixed a version-string expectation; final test run resulted in 102 passed, 0 failed.
• Frontend build: ran cd frontend && npm run build and observed a successful production build (Vite build completed); non-blocking npm warning about an env config was emitted but build succeeded.
• Commands used for verification were cd backend && pytest -q and cd frontend && npm run build and both verification steps completed successfully.

---

Codex Task