# Portal v151 — current data and verified coverage

API remains v1.1. Existing v1 paths, authentication, IDs, core collection inventories and field meanings are retained. This release adds compatible metadata and content corrections.

- COD admin-1 gazetteer coverage expands from four Fiji divisions to 79 units in eight countries. This is a verified name/P-code directory, not certification of map polygon equivalence or new local impact observations. See `/api-spec/geography-coverage.json` for all 24 countries and exact remaining needs.
- All 47 outstanding reference mappings were reviewed. Matching original passages were recovered for 25. Six have separately labelled alternative global graphics. Sixteen still require original material for claim verification. The original archive remains incomplete for 22 mappings; alternative sources are not counted as original recovery.
- Historical forecast watches no longer stand in for observed conditions. Forecast tables do not establish action implementation, approval, financing or AA maturity. The approximately 50% Guam/CNMI rainfall labels were withdrawn pending verification; the broad dry classification is unchanged.
- `supporting_passage.alternative_source` is optional. When populated, preserve its `original_cited_issue_recovered: false` and qualification. Main original-passage availability remains unchanged.
- `/api-spec/sync-partner-all.py` receives current core and extension collections in a single bulk response and checks the final manifest before atomic replacement. New optional collections and fields are retained without a hard-coded collection list. Old eight-collection clients continue to work. Clients still need their own presentation logic for newly introduced concepts.
- Matching conditional responses consume no daily data quota. Minute limits still apply to protect the shared service. Limits were not changed in this release.
- Every prepared bundled dataset is now saved under its immutable `data_version` before build. Mutating that version fails the build. The archive records dataset preparation, not verified deployment timestamps, every daily state or dynamic contribution history.

## Proposed next history phase — not yet implemented

Store a public-safe version at each publish, correction and withdrawal event, with UTC time, stable record ID, revision and public reason. Keep submitter identity and internal review messages in restricted audit storage. Store one end-of-day public snapshot or unchanged-state manifest. On withdrawal, remove the record from current exports and preserve only a public-safe withdrawal marker where retention or consent requires content removal. Test history across publish/edit/withdraw sequences before promising a full daily API.

Existing source archives can establish only the states actually retained. Missing earlier days and contribution revisions must not be reconstructed as observed history.

## Source follow-up

See `/downloads/source-follow-up-v151.html` and `/source-documents/outstanding-references.json`. A returned excerpt or trusted publisher does not automatically verify an entire portal inference. Third-party original-document rights are unchanged. API data are current; the stable API version is not a frozen website edition.