Release candidate 1.0.0 prepared from verified develop.
Breaking change: client adopts the updated investment resource/sync contract and may require re-login for cross-tab auth state.
Verification: clean npm audit and full frontend verify including types, lint, 453 tests with coverage, dependency boundaries, production build and Storybook build.
Release candidate 1.0.0 prepared from verified `develop`.
Breaking change: client adopts the updated investment resource/sync contract and may require re-login for cross-tab auth state.
Verification: clean npm audit and full frontend verify including types, lint, 453 tests with coverage, dependency boundaries, production build and Storybook build.
Repair investment recovery, draft preservation, date validation,
currency presentation, accessibility, and route error recovery.
Correct Docker and dependency checks and consume explicit income roles.
Enable every plugin recommended preset and replace Biome with ESLint formatting.
Preserve API contracts and JSX whitespace; verify source, tests, builds and tooling.
Use owner enums for known codes; preserve wire values and unknown fallbacks.
Verified npm ci and verify: 379 tests, 5 lint checks, app and Storybook builds.
Use Query cancellation and native mutation results instead of HTTP
registries, access epochs and copied scope state.
Keep local auth ordering and mutation identity fences.
Allow staged generated files to remain excluded from ESLint.
Backend contract: WealthLedger/backend@d698ed9
BREAKING CHANGE: drop investment stateVersion/progress/resources
from the client contract and use data/metadata readiness instead of
rewritten query status. Cross-tab auth may require re-login.
During active screen sync, status checks and observe reads run every 5s
instead of 1s; terminal state observes resources immediately.
OpenSpec change: WealthLedger/specs#21
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Release candidate 1.0.0 prepared from verified
develop.Breaking change: client adopts the updated investment resource/sync contract and may require re-login for cross-tab auth state.
Verification: clean npm audit and full frontend verify including types, lint, 453 tests with coverage, dependency boundaries, production build and Storybook build.