v1.1.6

Fixed

• A résumé section could print its heading at the bottom of a page with all of
  its content on the next one, leaving most of a page blank. A project was laid
  out as a single indivisible block, which was harmless while a project was one
  line long but not once the previous release restored its full description and
  detail bullets — a block that no longer fit the space left on the page moved to
  the next one in its entirety. Entries now flow across a page break the way work
  history already did, and a heading always travels with the first line beneath
  it.

v1.1.5

Fixed

• A tailored résumé printed its featured project with no description. The
  résumé is asked to choose which projects to feature by name only — on purpose,
  so it can pick what fits the role without an opportunity to reword the project
  itself — but choosing a project that way discarded the description, links and
  tags recorded for it instead of carrying them across. Every part of a chosen
  project is now taken from the master résumé unless it was genuinely rewritten
  for the role. Re-generating an affected résumé restores the description.

v1.1.4

Current model generations, and spend figures that can be trusted.

Added

• Claude Sonnet 5 and Opus 5 are selectable wherever a model can be chosen,
  alongside the previous generation, which is kept so any choice can be reverted
  instantly. Résumé tailoring now runs on Sonnet 5 by default, with its output
  and time limits re-measured against that model rather than the previous one.

Fixed

• A model could be offered for selection without anyone having recorded what
  it costs, in which case everything it did reported no cost at all — silently,
  since an unknown price is deliberately not treated as free. The list of
  selectable models and the list of recorded prices are now checked against each
  other automatically, so a model can no longer be offered without a price, a
  price can no longer be recorded with a missing rate, and neither list can drift
  from the other unnoticed.
• Corrected the recorded price for the previous top-tier model, which had been
  entered at three times its actual rate. It had not yet reached a release, so no
  spend figure was ever overstated.

v1.1.3

An owner-side tool for applying to a specific role.

Added

• Tailor a résumé to a single job lead, from the leads view. Reviewing a
  discovered role and deciding to apply now leads straight into generating a
  résumé aimed at that posting — the same tailoring the public simulator
  performs, held to the same honesty rules: the summary and which
  accomplishments to feature are chosen for the role, while employers, dates,
  bullet wording, skills and education stay exactly as they read on the master
  résumé. The job description can be pasted in from the real posting rather than
  relying on what was scraped, and a short note can steer the emphasis. The
  result downloads as a PDF and can be regenerated without losing earlier
  versions.
• The generated résumé states whether its summary was genuinely tailored or fell
  back to the master summary, so it is clear what is being sent before it goes
  out.
• Click-throughs from a tailored résumé attribute to the company it was written
  for, so a recruiter opening the portal from a submitted application is
  visible as such.
• Tailored résumés are removed together with their lead when leads are purged.
  Archiving a lead keeps them.

Fixed

• Cost reporting for work done by the more capable model read as unknown
  rather than as a figure. Only the fast model had list pricing recorded, so
  anything the capable model did — the interview-kit redaction pass, and now
  résumé tailoring — contributed nothing to the spend view.

v1.1.2

A correction to 1.1.1, found while repairing real leads.

Fixed

• Some job-board reposters were being trusted as the employer. Sites that
  list themselves as the hiring company — on a generic hosting platform, with
  the company name only as a subdomain — were marked as a direct company link
  and shown with the "direct" badge. That hid exactly the leads whose real
  employer is unknown, which is the opposite of what the previous release set
  out to do. A lead now only counts as the employer's own site when the company
  name is in the domain itself, not merely somewhere in the hostname.
• Y Combinator job pages are recognised as direct company listings rather than
  being flagged as reposters.

v1.1.1

Job leads now link where you can actually apply.

Fixed

• Lead links went to job-board reposters instead of the employer.
  When a posting was discovered through an aggregator, that aggregator's
  URL was stored as the lead's link — often putting a mandatory signup
  between you and the actual application — even when a direct link to the
  company or its applicant-tracking system was already available in the
  same data. Leads now prefer the employer's own site, then a real
  applicant-tracking system, and fall back to a reposter only when
  nothing direct exists anywhere.
• A lead sourced only through a reposter is now flagged as such, in
  the admin leads view and by the agent when it surfaces one. That flag
  also warns that the company name on the lead is unverified: reposted
  listings are where the sourced company is least reliable, and one was
  observed filed under a different company than its own description
  described. The system flags rather than guessing — it will not infer a
  company name from the posting body.
• Existing leads can be repaired in place with no re-scrape and no API
  spend, since the necessary data was already stored.

Changed

• The agent no longer promises behavior changes it has no way to keep.
  When something is wrong at a structural level, it now says so and
  offers to record it, instead of committing to "do better next time" in
  a conversation that won't outlive the session.

v1.1.0

Pausing the search, and clearing the decks.

Added

• Standby mode. A deliberate, reversible pause for when the job search
  isn't running: the public site becomes a single page that says so plainly
  and still offers a way to make contact, and the cloud VM behind it is
  stopped rather than left idling. Controlled from an owner-only console that
  runs entirely at the edge, so it keeps working while the backend is off —
  which is what makes coming back a single click. Resuming waits for a health
  check before the live site returns, and rolls any scheduled work that came
  due during the pause forward to its next occurrence instead of firing a
  backlog. Nothing is destroyed: databases, credentials and configuration all
  survive the pause untouched.
• Batch lead cleanup. The admin leads view can now archive or permanently
  remove leads in bulk, acting on exactly the rows the current filters show,
  with a new "older than N days" filter for clearing out a stale pool. Both
  actions confirm before running; permanent deletion skips any lead already
  promoted to a real application.
• A settable "searching since" date. The month shown on the landing page
  can now be set by the owner instead of always being derived from the oldest
  application, so a deliberate break in the search doesn't read as a long
  stretch of inactivity.

v1.0.7

Job-search reliability and monitoring fidelity.

Fixed

• The job-search index's slower responses could exceed the client's
  20-second timeout and be discarded as errors even though the query had
  actually succeeded — which both dropped fresh job leads and made the
  "Job search API" and "OneCLI gateway" nodes on the architecture page read
  as degraded. The timeout is now 45 seconds, matching how long that source
  can legitimately take, so those results land and the nodes reflect real
  health.

v1.0.6

Pipeline-accuracy hardening (continued) and monitoring fidelity.

Fixed

• An application could be pushed to the final round when the automated
  mail reader saw a "next round" email that actually named an earlier
  interview round (for example, a system-design round) — which also generated
  a spurious final-round prep kit. The deterministic mail-to-board converter no
  longer guesses the target round from a generic "next round" signal; that
  placement is now owned by the agent, which reads the specific round named in
  the email and on the calendar. A genuine rejection or offer still closes the
  board as before.
• The "Job search API" node on the architecture page could show a false
  "Down" status or elevated error rate caused by dead or renamed job-board
  tokens returning 404s. A board that has moved or been renamed is now treated
  as skippable configuration drift rather than a request failure, and the
  node's health reflects only the job-search index it is labeled for.

v1.0.5

Interview-kit rendering fidelity.

Fixed

• Interview-kit pages now render their formatting faithfully: numbered
  criteria count up correctly instead of every item showing "1.", emphasized
  text renders as italics rather than showing raw asterisks, and nested lists,
  tables, and links display properly. The kit's title block no longer surfaces
  as an empty "additional section," and an anonymization marker can no longer
  render as a broken chip.

Changed

• The interview-kit Google Doc is now produced by native Markdown import, so
  the document a candidate opens preserves headings, tables, nested lists, and
  emphasis instead of a lossy approximation.