resume-team

Resume Team

1. Resolve the plugin root two directories above this file. Require macOS or Linux, candidate_fit_preflight.py, native_resume_team.py, config.json, and the configured master resume. Fail closed if any is unavailable. Put the exact job description in a private temporary UTF-8 file, and generate a safe run_id, safe case_id, and strict ISO as_of_date. Before invoking the native team or creating an output directory, screen only master_resume_path from config.json (never a previous tailored resume):

   python candidate_fit_preflight.py --resume <CONFIGURED_MASTER> --job-description <PRIVATE_EXACT_JD.txt> --run-id <RUN_ID> --case-id <CASE_ID> --as-of-date <YYYY-MM-DD> --json

   Continue only on exit 0 and a valid digest-bound candidate-fit-policy-v3 report with threshold 70.0, score at least 70, trustworthy extraction, zero hard knockouts, passed: true, and no codes. Canonically hash the exact report as candidate_fit_report_digest. Exit 1, any score below 70 (including 60–69), or any hard knockout is REJECTED:CANDIDATE_FIT; report it and create no output, draft, DOCX, or tracker row. Exit 2 or an unavailable, malformed, stale, non-canonical, or digest-mismatched report is FAILED:CANDIDATE_FIT_PREFLIGHT. Neither condition has a bypass. ATS/HR scores are advisory and cannot override candidate fit.

2. Only after candidate fit passes, run the non-model host preflight. Windows is not supported by the hardened runtime; its host preflight returns POSIX_RUNTIME_REQUIRED:

   python native_resume_team.py --host codex --check-host --config config.json

   Continue only when it exits 0 and returns ready: true with every check passing.

3. Choose only a prospective new output path. Use a user-supplied path only when it does not exist; otherwise derive a sanitized, non-existing applications/<Company> - <Role> path from the job description. Do not create it. Never reuse, replace, or clobber an existing output or resume.md; the runtime intentionally has no replacement mode.

4. Capture the runtime's exact stdout in a private temporary result file so the result-provided authorization sidecar path and digest remain available to finalization:

   runtime_result_file="$(mktemp)"; python native_resume_team.py --host codex --job-description-file <PRIVATE_EXACT_JD.txt> --output-dir <APP_DIR> --config config.json --run-id <RUN_ID> --case-id <CASE_ID> --as-of-date <YYYY-MM-DD> >"$runtime_result_file"

   Preserve and check the Python process exit status before parsing the single JSON result from that file. Do not reconstruct result fields from logs or filenames. The runtime independently recomputes the same fit report before constructing an output or role adapter. Require its report and canonical digest to exactly match the caller-validated preflight. Only then does it create <APP_DIR> and atomically bind that exact text to <APP_DIR>/job_description.txt; it accepts only a byte-identical pre-existing regular file and never clobbers a different one. The Researcher contract admits only nonblank, alphanumeric requirements that each cover one exact, unique, complete non-separator JD line; substrings are rejected so surrounding negation, scope, bounds, and qualification cannot be trimmed before the Writer or Auditor sees the rubric.

   Omit --model and --reasoning-effort by default. The hardened subprocess ignores user configuration and transient parent-session settings, so report its effective model/reasoning selection as the isolated managed CLI default and unknown—not as an inherited model, Ultra setting, or profile. Only when the user explicitly requests a Codex pin may you append --model <exact-model> and/or --reasoning-effort ultra. There is no runtime profile or replacement option; always choose a new output directory and fail closed rather than clobber an existing artifact.

5. Accept draft-stage success only when the process exits 0, the captured result is resume-team-result/v2 with terminal_class: PUBLISHED, its candidate_fit_report and candidate_fit_report_digest exactly match the independently validated preflight, and <APP_DIR>/resume.md exists with the reported final_draft_digest. Independently hash resume.md. Resolve the exact authorization_receipt_path from that result against <APP_DIR> when relative and require the resolved path's parent to equal the resolved output directory. Then invoke the code-bound acceptance gate with the exact result-provided digest and require exit 0 plus verified: true: