senke/veza
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
veza/docs/archive/v0-history/SMOKE_TEST_V0502.md
senke 0e7097ed1b chore(cleanup): J1 — purge 220MB debris, archive session docs (complete) 
First-attempt commit 3a5c6e184 only captured the .gitignore change; the
pre-commit hook silently dropped the 343 staged moves/deletes during
lint-staged's "no matching task" path. This commit re-applies the intended
J1 content on top of bec75f143 (which was pushed in parallel).

Uses --no-verify because:
- J1 only touches .md/.json/.log/.png/binaries — zero code that would
  benefit from lint-staged, typecheck, or vitest
- The hook demonstrated it corrupts pure-rename commits in this repo
- Explicitly authorized by user for this one commit

Changes (343 total: 169 deletions + 174 renames):

Binaries purged (~167 MB):
- veza-backend-api/{server,modern-server,encrypt_oauth_tokens,seed,seed-v2}

Generated reports purged:
- 9 apps/web/lint_report*.json (~32 MB)
- 8 apps/web/tsc_*.{log,txt} + ts_*.log (TS error snapshots)
- 3 apps/web/storybook_*.json (1375+ stored errors)
- apps/web/{build_errors*,build_output,final_errors}.txt
- 70 veza-backend-api/coverage*.out + coverage_groups/ (~4 MB)
- 3 veza-backend-api/internal/handlers/*.bak

Root cleanup:
- 54 audit-*.png (visual regression baselines, ~11 MB)
- 9 stale MVP-era scripts (Jan 27, hardcoded v0.101):
  start_{iteration,mvp,recovery}.sh,
  test_{mvp_endpoints,protected_endpoints,user_journey}.sh,
  validate_v0101.sh, verify_logs_setup.sh, gen_hash.py

Session docs archived (not deleted — preserved under docs/archive/):
- 78 apps/web/*.md     → docs/archive/frontend-sessions-2026/
- 43 veza-backend-api/*.md → docs/archive/backend-sessions-2026/
- 53 docs/{RETROSPECTIVE_V,SMOKE_TEST_V,PLAN_V0_,V0_*_RELEASE_SCOPE,
          AUDIT_,PLAN_ACTION_AUDIT,REMEDIATION_PROGRESS}*.md
                        → docs/archive/v0-history/

README.md and CONTRIBUTING.md preserved in apps/web/ and veza-backend-api/.

Note: The .gitignore rules preventing recurrence were already pushed in
3a5c6e184 and remain in place — this commit does not modify .gitignore.

Refs: AUDIT_REPORT.md §11
2026-04-14 17:12:03 +02:00

1.7 KiB
Raw Blame History

Smoke Test — v0.502 Chat Server Rewrite

Pre-requisites

  • go build ./... passes in veza-backend-api
  • go test ./internal/websocket/chat/... -v passes (15 tests)
  • Frontend builds without new errors (npx tsc --noEmit)

Backend Chat WebSocket

  • Backend starts without errors (go run ./cmd/server)
  • POST /api/v1/chat/token returns {token, ws_url: "/api/v1/ws", expires_in}
  • WebSocket connects at ws://localhost:8080/api/v1/ws?token=<jwt>
  • Receives {"type":"ActionConfirmed","action":"connected","success":true} on connect
  • Sending {"type":"Ping"} returns {"type":"Pong"}
  • Missing/invalid token returns 401

Message Flow

  • JoinConversation -> ActionConfirmed
  • SendMessage -> ActionConfirmed + NewMessage broadcast
  • EditMessage -> ActionConfirmed + MessageEdited broadcast
  • DeleteMessage -> ActionConfirmed + MessageDeleted broadcast
  • FetchHistory -> HistoryChunk with messages array

Real-time Features

  • Typing -> UserTyping broadcast to other room members
  • MarkAsRead -> ActionConfirmed + MessageRead broadcast
  • Delivered -> ActionConfirmed + MessageDelivered broadcast
  • AddReaction -> ActionConfirmed + ReactionAdded broadcast
  • RemoveReaction -> ActionConfirmed + ReactionRemoved broadcast

Call Signaling

  • CallOffer relayed to target user
  • CallAnswer relayed to caller
  • ICECandidate relayed to target
  • CallHangup relayed to target
  • CallReject relayed to caller

Docker

  • docker-compose up starts without chat-server service
  • Backend still starts and serves WS endpoint

Frontend

  • Chat connects to /api/v1/ws instead of old port 8081
  • Messages sent and received correctly
  • Typing indicators work