mirror of
https://github.com/hanzoai/chat.git
synced 2026-09-30 20:51:17 +00:00
zooqueenandHanzo Dev
b1130806a1
Measured rather than guessed: 186 suites, 69 failing, and TWELVE of those failed
during import having executed zero tests. That distinction is invisible in a
failed/total count and it matters โ a suite that runs and fails tells you
something, a suite that dies at import tells you only that somebody wrote a file.
Same cause throughout, and it cascades: the spec replaces a `@hanzochat/*`
package with the two or three names it expects the subject to want, so the first
thing deeper in the require graph that wants a fourth throws. One file went
through five in a row. Spreading `jest.requireActual` under the overrides fixes
it at the root; `deleteUser` additionally overrode `CacheKeys` with `{}`, which
made the real cacheConfig reject every namespace it was asked to validate.
deleteUser 7 tests modelEndHandler 6 tests
preview 15 tests addedConvo 3 tests
process 49 tests
All red, and left that way โ they are upstream specs whose implementations did
not land, and a red suite that runs is worth more than a green name that does
not. Six remain dead (roles, abort, streamTenant, auth.cloudfront,
imageTools-agent, importers); their blockers are middleware shapes rather than
package stubs. Nothing here gates.
Co-authored-by: Hanzo Dev <[email protected]>