[arko33]

What

• README v2 (professional): screenshots inline (landing hero, replay dashboard, the turn-4 forensic view), capture layer & Ghost marked as shipped/live (cloud, shadow-git, probes, OpenCode plugin), suite status 24/24 with three evidence channels (CLI executions, Actions check on every PR, committed test-code exports under docs/testsprite-exports/), web routes incl. /login /pair /api/v1/*, milestone timeline marked done-where-done, repo layout now includes packages/ghost + docs exports
• Landing page (#quickstart): full setup narrative — 01 install (one curl line, no npm) > 02 record (Mode A plugin / Mode B filesystem / Mode C probes, any agent) > 03 inspect/rollback; 'Full setup docs' button to the README; metadata-only-sync fact chip
• TestSprite transparency: exact Python test code the suite runs committed in docs/testsprite-exports/ (7 files incl. the hardened integration flow)
• Repo hygiene: local TestSprite scratch (.ts-) removed; .gitignore now excludes .ts-* / .testsprite-tests.json; duplicate screenshot removed (landing2 == lanidng1)

Verified

• npm run typecheck green
• TestSprite suite: 23/23 unit-style + integration flow passing (executions ddf5126a, 8ebb6adc, f6b69e19)
• Production smoke green: / 200, /login 200, /pair 200, /playground 200, invoices API 200, pair POST issues codes (Neon write OK)

[vercel]

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

Project	Deployment	Actions	Updated
ghostinthecodebase	Ready	Preview	Oct 21, 2026 5:35pm UTC

[testsprite]

Caution

Widespread failures — 23 failed

The executable subset looks mostly healthy, but the run is too sparse to be highly trustworthy: 1 test passed and 24 tests failed, with no frontend coverage at all. Because every failure reports the same TestSprite internal error reference, the score reflects only the executable subset and does not confirm a product bug for those cases. The lone passing invoice visibility/retrieval flow suggests the core API can respond correctly in at least one path, but the rest of the suite did not produce actionable product signals. Overall stability remains unproven, and the blocked/internal-harness pattern prevents meaningful confidence in auth, validation, and ownership behavior.

Results: 1 passed • 23 failed • 24 total  ·  View Full Report ↗

23 failed tests

Create an invoice then read it back

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Reject invoice listing with unknown user identity

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Create invoice with missing customer returns 422 and creates nothing

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

List alice's own invoices

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Reject invoice listing without authentication

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Return 404 for an unknown invoice id

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Create invoice with malformed JSON body returns 400 invalid_json

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Unknown x-user-id value returns 401 on POST /api/invoices

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

List invoices with a real user session returns only that user's seeded invoice

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Create invoice with non-numeric amount returns 422 and creates nothing

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Reject missing auth before invoice existence is evaluated

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

List invoices does not leak other users' invoice records or fields

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Get own seeded invoice by id as Bob

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Invoice list response shape is stable for seeded invoices

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

List bob's own invoices

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Create invoice without x-user-id returns 401 and no invoice is created

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Unknown invoice id returns not_found even for authenticated user

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Get own seeded invoice by id as Alice

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Unauthenticated request to invoices endpoint should not reveal data even if caller is otherwise valid

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Reject unauthenticated invoice read

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Create and read invoice as Alice, ensuring owner isolation fields

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Read a created invoice using the id captured from create

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

---

Deny access when Alice reads Bob's invoice

Screenshot	Error details
—	TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)

1 passed test

Test Case	Status	Screenshot
Invoice visibility and retrieval flow	Passed	—

Evaluation details

What could be better: The main weakness is test execution reliability rather than a clearly isolated API defect: 24 backend tests all failed with the same message, "TestSprite hit an internal error while running this test; our team has been notified. (ref: 30bc0dd9-8d93-4360-9689-3b26c615ee46)". That means the suite could not validate critical invoice behaviors such as POST /api/invoices validation, auth rejection, ownership checks, and 404 handling. Since the failures are uniform across functional, authorization, and validation cases, the immediate problem is likely harness-side or environment-side, not a single endpoint regression. The one pass indicates some functionality is reachable, but the broader API quality remains unverified.

Recommended next steps: First, rerun the failing backend invoice tests with harness logging enabled to determine whether the repeated TestSprite internal error is caused by test setup, auth configuration, or an environment outage. Verify the invoice routes and seeded-user fixtures separately from the full suite, then re-execute the high-priority cases for create/list/read, auth rejection, and unknown-id handling. If the harness is healthy, investigate the API paths behind POST /api/invoices and the invoice read/list endpoints for status-code or validation mismatches. Use the fix prompt below to target the concrete cases once the runner is producing real responses.

---

_{Automated end-to-end testing powered by}