Evidence-aware release notes

Changelog and verification history

Each entry says what changed and which layer was actually checked. Repository implementation, deployment, search submission, indexing, integration import, and destination delivery remain separate.

Inspect repository history ↗How proof is classified

Production status rule

Actor builds, runs, Store defaults, and integration proofs in the entries below are historical primary-organization evidence from before the Job Atlas migration. They are not Job Atlas build numbers. See the current Job Atlas catalog and evidence boundary.

An entry labeled “repository” is not a live release. Production status is added only after the exact approved artifact is deployed and independently read back from the canonical URL. Search submission and indexing are recorded separately.

2026-09-03 · Gate-aware shortlist and audit release

Layer: public Actor deployment plus exact immutable canaries.

Runtime build 0.1.12 introduced default shortlist mode, configurable minDeliveryScore, complete audit mode, and scorer RUN-SUMMARY v4 counts. Four exact runs proved a filtered zero-charge hold, a retained audit hold, a delivery-5 scored row, and a three-source default search whose two filtered rows were not charged. Documentation-only build 0.1.13 uses the identical runtime image and passed a zero-charge smoke before becoming public latest.

At that release, the integration assets pinned verified runtime 0.1.12. Current starters use latest; see the scorer guide for the separate September 5 run. Hosted MCP and authenticated n8n, Make, Zapier, and named Google Sheets writes remain separate unverified layers.

2026-09-03 · Repository website expansion

Layer: repository implementation; production status is recorded separately by the exact successful main workflow receipt.

  • Expanded the catalog from two source Actors to include the public AI Job Search & Fit Scorer.
  • Added Actor, integration, and guide hubs plus task-complete product and integration pages.
  • Added four intent-led implementation guides, contract resolution, About, methodology, privacy, and this changelog.
  • Added consistent canonical, social, breadcrumb, and event metadata.
  • Separated current Store defaults from repository integration-tested pins where they differ.

This repository entry alone does not prove deployment, crawling, indexing, or organic conversions; those proof layers require their own receipts.

2026-09-03 · AI Job Fit Scorer evidence

Layer: exact immutable Actor runs.

Build 0.1.11 (MorUFN0ZFQjpmpytr) passed a fresh Console-form run and a bounded fake-profile canary. In the one-result canary, LinkedIn, remote boards, and JustJoinIT returned source jobs, one AI-scored evaluation was retained, and one $0.02 result event reconciled with a warning-free v3 summary.

This proves the Actor path. Hosted MCP, n8n or Make import, Zapier editor construction, schedule behavior, and named destination writes remain separate checks.

2026-09-03 · Store and integration build split recorded

Layer: current public Store metadata plus repository compatibility evidence.

  • LinkedIn Store default observed as 1.0.6 (9uyPad4O7Zcjp1AVe); maintained integrations remain tested against 1.0.2.
  • EURAXESS Store default observed as 1.0.20 (5n7huEXQYFUBdndQP); maintained integrations remain tested against 1.0.16.
  • Scorer Store default and tested pin are 0.1.11.

Older integration pins are exact compatibility choices, not claims about the latest Store release. A pin move requires a fresh regression and destination proof.

2026-09-02 · Initial SEO page deployment

Layer: deployment and search discovery notification.

The initial nine canonical pages, robots file, and sitemap were deployed to the isolated Firebase Hosting site. Live read-only checks confirmed canonical HTTP responses and the audited homepage bytes. Search Console sitemap and IndexNow automation provide discovery notification; neither receipt is indexing proof.

2026-09-03 · Initial indexing observation

Layer: search-engine inspection.

The latest recorded check found the homepage indexed in Google while the eight new detail pages remained pending; Bing still showed all nine pending crawl and not indexed. The page set was about one day old, so the programme waits through the 72-hour checkpoint before treating unchanged status as actionable.

2026-08-24 · Static website baseline

Layer: local contract tests and browser QA for the then-current two-Actor site.

The baseline verified responsive layout, keyboard interaction, local conversion events, direct attributed Actor links, trust copy, canonical metadata, structured data, local asset integrity, and current production destinations. Those results apply to that dated artifact and do not automatically cover later page additions.