Replace channel names with chat channels registry

[crazygo]

Summary

• Replace the runtime chat_channel_names flow with a chat_channels registry for channels and thread scopes.
• Add explicit channel/thread archive state via archived_at and route archive through /api/chat/channels/archive.
• Downgrade /api/chat/scopes to activity-only so historical messages do not recreate visible sidebar entities by themselves.
• Keep deprecated chat_channel_names as a rollback backup in migration 025; runtime code no longer reads or writes it.
• Add .agents/skills/bricks-turso-branch-migration-test documenting the Turso branch DB migration validation workflow.

Manual Cloud DB Validation

• Created Turso branch DB bricks-mig-0623a from database-bricks with --from-db.
• Ran migration 025 against the branch DB successfully.
• Verified chat_channels exists and chat_channel_names still exists as deprecated rollback backup.
• Verified branch DB row counts immediately after migration: chat_channels=23, chat_channel_names=23, migrations.version=025 recorded once.
• Started local backend against the branch DB with AUTO_MIGRATE=false and local Flutter Web against http://127.0.0.1:3010.
• User manually verified channel archive and thread archive behavior.

Validation Commands

• npm run type-check in apps/node_backend
• npm test -- src/routes/chat.test.ts src/services/chatAsyncTransportService.test.ts src/services/localAgentLoopService.test.ts in apps/node_backend
• flutter analyze in apps/mobile_chat_app
• Earlier: flutter test test/chat_history_api_service_test.dart test/chat_navigation_page_test.dart in apps/mobile_chat_app
• Code maps YAML loaded successfully with Ruby YAML

Code Maps

• Updated docs/code_maps/feature_map.yaml and docs/code_maps/logic_map.yaml for the chat_session / backend chat registry path.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bricks	Ready	Preview, Comment	Jun 23, 2026 3:01pm