Better answers for resumes, PRDs, and a few other specialties

Portail v2.2.3 shipped on 2026-09-24 as a patch release focused on better answers for resumes, prds, and a few other specialties. Portail's chat model now has access to a small library of domain playbooks it can quietly pull in mid-reply: resume and CV formatting, cover letters, content and copywriting frameworks, product management frameworks like RICE scoring and PRD structure, presenting data to stakeholders, and spreadsheet formulas. The model only sees a short list of what is available up front. It fetches the actual guidance only when a request calls for it, the same on-demand technique already used for personal memory and project files, so the improvement costs nothing on ordinary turns that never touch these topics. The lookup and the guidance it returns are never shown to the user, only a more informed answer. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.

The main changes were direct: chat replies about resumes, cover letters, prds, marketing copy, spreadsheet formulas, and presenting data to stakeholders now draw on a small built-in library of specialist guidance when it is relevant, and the lookup is invisible and on-demand: the model only asks for a playbook when a request genuinely needs one, so nothing changes for requests that do not touch these topics. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.

This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.2.3 moved that contract forward in its own narrow lane.

The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.

The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.