Honor configured API paths in board recovery test - #2437
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
[Codex independent review disposition] Fresh-context review found no CRITICAL/HIGH direct blocker. The configured origin guard remains, the exact target-board predicate now preserves the configured API pathname, and focused coverage pins /api, /taskdeck/api, and trailing-slash normalization. Focused Vitest 3/3, scoped ESLint, typecheck, production build, default-path Paper recovery Playwright 1/1, and diff check passed. Hosted exact-head CI and automatic review are pending. |
|
Current-base independent review at dc7c549 against f59b854 found no CRITICAL/HIGH defect. Verified: the net diff remains the three E2E/helper files, current main has no overlapping frontend change, the route-path regression passed 3/3, and diff hygiene passed. Non-blocking and declined for this PR: older recovery scenarios retain /api suffix predicates. They support the documented /taskdeck/api shape and are outside #2431's Paper board-recovery acceptance. |
Summary
Closes #2431
Evidence
Red first on base d3a3f7a:
Green at dc7c549 on current base f59b854:
Review disposition
Hosted CI
Boundaries