Repository navigation
feat(positions): show the position page around the hiring process (G#10) - #11
Merged
Merged
Conversation
Build goal G#10. The position page was a long stack of text and links. It now leads with where the search stands and what to do next: - Header with status badge and key facts as chips - Six-step process bar (JD, success profile, sourcing, matching, outreach, submission) from a new read-only GET .../progress - A rule-based "next" card linking to the page to act on; no AI, nothing runs by itself (brief 1.1) - Candidate numbers, links grouped into four cards, and the JD and intake, details, weights, status and activity folded below Generated with AI assistance Co-Authored-By: Interactor Build <peter@interactor.com>
Generated with AI assistance Co-Authored-By: Interactor Build <peter@interactor.com>
…tten Generated with AI assistance Co-Authored-By: Interactor Build <peter@interactor.com>
…shed candidates The position page was not Prettier-formatted, which failed CI before any test ran. The next-step card also counted every pipeline entry that had no analysis, so candidates already rejected or closed kept it suggesting an analysis. It now counts only people still in play (toAnalyze). Generated with AI assistance Co-Authored-By: Interactor Build <peter@interactor.com>
The two earlier format commits were written without running Prettier and CI kept failing on this one file; this is its actual Prettier output. Generated with AI assistance Co-Authored-By: Interactor Build <peter@interactor.com>
1 task done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Build goal G#10. Product owner feedback: the position page was a long stack of plain text and underlined links. It now leads with where the search stands and what to do next. The layout was agreed from a mockup in the session.
Brief: §1.1 (principles unchanged), §2 (process order), §3, §4, §5.3.
Changes
<details>): job description and intake, position details, matching weights, change status, activity.GET /positions/:positionId/progress(permission matrix entry, api-contracts).Deviation to flag
Testing
position-progress.test.ts(steps, next action)progress.db.test.ts(JD and profile states, pipeline counts, pending drafts, tenant isolation)Generated with AI assistance
Co-Authored-By: Interactor Build peter@interactor.com