Add Zyra Job Readiness command center - #35
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7e2e177485
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| label: "Production engineering", | ||
| score: 88, |
There was a problem hiding this comment.
Derive readiness scores from verified evidence
Every installation, including a fresh tenant with no portfolio evidence or a currently failing build, receives the same hard-coded scores and an overall value of 86, even though the UI labels this as “Current readiness” and presents it as employer-facing evidence. These values should be calculated from verifiable repository/account state, or clearly presented as non-evaluative guidance rather than readiness measurements.
Useful? React with 👍 / 👎.
| <Route path="/job-readiness">{() => <ProtectedRoute component={JobReadinessPage} />}</Route> | ||
| <Route path="/career">{() => <Redirect to="/job-readiness" />}</Route> |
There was a problem hiding this comment.
Add the workspace to application navigation
Authenticated users who navigate through the Layout sidebar have no way to discover this route: navGroups contains no Job Readiness entry, and a repository-wide search finds no other link to /job-readiness or /career. Registering the route alone therefore leaves the new first-class workspace accessible only to users who already know and manually enter its URL.
Useful? React with 👍 / 👎.
| {proofRoutes.map(({ label, href, icon: Icon, detail }) => ( | ||
| <Link key={href} href={href}> |
There was a problem hiding this comment.
Add stable test IDs to the portfolio links
The six proof tiles are interactive navigation elements but lack unique data-testid attributes, so browser tests following the project's selector convention cannot reliably identify or exercise each destination; the final “Review proof” action has the same omission. Add a route- or label-derived test ID to each link/action.
Useful? React with 👍 / 👎.
What this adds
/job-readinessworkspace for AI/software, cloud/DevSecOps, cybersecurity, and platform career tracksdocs/JOB_READINESS.mdengineering standardJob ReadinessCI gate requiring clean install, TypeScript validation, and production build/careerredirect for a simple entry pointGoal
Make Zyra easier to present as verifiable engineering work to recruiters and hiring managers without weakening its existing security/enterprise focus. The standard emphasizes reproducible evidence, clean builds, secure public portfolio material, and honest claims.