feat(spine): synthetic journeys — probe the product, not just the port #5474
ccantynzAI Reviewcommented 23d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 23d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
Final piece of the five-move reliability build. The core suite asks "does this endpoint answer?" — which stays green through a broken session pipeline or a page rendering its chrome with no content. Three journeys now run in the same monitor tick, inheriting persistence, owner alerting, and incident sync:
spine-probeuser (unloginable password hash, owns nothing), fetch /dashboard + /notifications with the cookie, require logged-in chrome; session deleted infinally.Journey failures are user-facing by definition, so they deliberately count toward the public /status incident feed. Unit tests pin each red/green decision via the injected fetch.
This PR is also the first merge to face the new CI gate — its branch CI run must be green before the gated chain will merge it.
🤖 Generated with Claude Code