senke/veza

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.9 KiB

Raw Permalink Blame History

Storybook Audit Report

Summary

Total Stories: 963
Failed Stories: 310 (~32% failure rate)
Total Errors: 1,040 (Network + Console)

Failure Categories

1. Unmocked Network Requests (Critical)

Count: 463 Network Failures Diagnosis: Stories are attempting to hit real production endpoints (api.veza.com) instead of using mocks.

ERR_NAME_NOT_RESOLVED: https://api.veza.com/api/v1/api/v1/logs/frontend
ERR_ABORTED: https://api.veza.com/api/v1/auth/me
ERR_ABORTED: https://picsum.photos/200 (External images)

Impact: Components depending on data stay in "Loading" state indefinitely or crash when data is missing.

2. Missing Context Providers

Count: ~15-20 identified instances (estimated from sample) Diagnosis: Components accessing global state that isn't provided in the story decorator.

Error: useAuth must be used within AuthProvider
TypeError: Cannot read properties of undefined (reading 'name') (Likely missing user object from auth context)

3. Runtime Crashes

TypeError: Cannot read properties of undefined: Cascading failures from missing API data.

Remediation Plan

Step 1: Configure Mock Service Worker (MSW)

Initialize MSW in Storybook.
Create handlers.ts to mock core endpoints:
- /auth/me (User profile)
- /api/v1/logs/frontend (Prevent logging noise)
- Domain specific endpoints for failing stories.

Step 2: Global Decorators

Wrap all stories in preview.tsx with:
- AuthProvider (Mocked)
- QueryClientProvider (React Query)
- MemoryRouter (already likely present but need verification)

Step 3: Fix Specific Issues

Fix double-path URL bug (/api/v1/api/v1/...)
Mock external image services or provide local fallbacks.

Priority

High. 30% of the component library is broken in documentation, making it unreliable for development.

1.9 KiB Raw Permalink Blame History