Repository navigation
Publish release builds into their own folders through the emitter, while UK releases stay on the pointer files - #1505
Merged
Merged
Conversation
Failing tests first for hand-over step H2c. UK national, dense and local-area release manifests name `release` and `build` as strings, record `built_at` and the built-with packages at the top level, and give each artifact a `role` without a `revision`; the build module hands a build to the emitter's `publish_release` and treats it as current only when a published receipt names it; the loader reads `releases.json`; the tagged publisher refuses UK releases and offers no line promotion. The fake emitter client applies release changes with the interface's shared checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hand-over step H2c. The UK national, dense and local-area releases hand each build to the separately installed emitter with the interface's `publish_release` call (`microcosm-publish-release-build`, in `microcosm.build.release_publication`). The emitter's release writer puts it in `releases/<release>/<build>/` and records it in `releases.json`; Microcosm no longer commits, tags or writes pointer files for them, and treats a build as current only when the receipt is `published` and names it as `current`. Both manifests name `release` and `build` (the calibration attempt) as strings; the release manifest records `built_at` and the built-with packages at its top level and a `role` per artifact, with no `revision`. The contract checks that layout for UK releases, the assemblers write it and print the new commands, and `microcosm-data`'s loader reads each UK release's current build from `releases.json`. US releases keep tags and `latest.json`; the tagged publisher refuses UK releases and loses line promotion. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The stable releases proposed for US builds are not agreed with the US data builder, so the contract should record them, with their `releases.json` roles, in one place while no US release publishes into build folders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`PROPOSED_US_RELEASES` names `populace-us-2024-national` (role `national`, the default) and `populace-us-2024-acs-local` (role `local_area`), the stable releases proposed for US builds. They are not agreed with the US data builder, so `publishes_to_build_folder` names no US release and US releases keep tags and `latest.json`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…names `RELEASE_ROLES` and `PROPOSED_US_RELEASES` are read-only mappings, as the shared constants guidance asks, and the contract's `__all__` lists the build-folder names other modules import. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The proposal now names one national and one local-area release in the one `populace-us` repository: `populace-us-2024-national` and `populace-us-2024-local`, still awaiting the agreement with the US data builder. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`PROPOSED_US_RELEASES` follows the adjusted proposal: one `policyengine/populace-us` repository with `populace-us-2024-national` (role `national`) and `populace-us-2024-local` (role `local_area`). Build IDs and the `populace_us_2024_acs_local.h5` file name are unchanged, and nothing reads the names until the US data builder agrees them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CI's engine-free jobs failed `test_assembler_stages_a_graph_built_dense_candidate`: the synthetic graph records engine versions as `unavailable`, and the build-folder layout's new compatibility-list check refused the dense release's `==unavailable` specifiers, which the local-area contract never checked. This test holds the local-area contract to its old scope. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The build-folder layout moved `built_at` and the built-with packages to the release manifest's top level. The national contract still requires the compatibility lists to include the built-with versions; the local-area contract, as before, checks only that the built-with packages are there, so a graph-built dense candidate whose engines read `unavailable` assembles again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the pointer files go Review round 1 of the build-folder publication. These tests fail on assertions until the fix: - the dense assembler prints a publication without --make-current and a separate --promote command, since the emitter refuses every change to a current build while the latest*.json pointer files exist; - a --promote refused for those pointer files says to promote again once they are deleted, not to publish without --make-current; - with HF_HUB_OFFLINE or TRANSFORMERS_OFFLINE set, the command refuses before starting an emitter; - the command runs the emitter's write-access check and hands nothing over when the credential is missing or read-only. They also add command tests for the pending, refused and unavailable receipts, and a test that publishes an assembled UK national directory with the release contract itself; those pin behaviour that already holds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t a dense promotion The publication command now makes the two checks the staged-bundle hand-over makes before it hands anything to the emitter: - with HF_HUB_OFFLINE or TRANSFORMERS_OFFLINE set it refuses before starting an emitter (staging_dataset.hub_offline), since the emitter inherits the variable and the change would stay pending until it expired an hour later; - it runs the emitter's write-access check (staging_dataset's write_access_problem, which now takes the wording of the change it checks for) and hands nothing over when the emitter is missing or outdated, or the credential is missing, read-only or cannot reach the repository. While the repository keeps its latest*.json pointer files the emitter refuses every change to a current build, so the dense assembler prints a publication without --make-current and a separate --promote command, as the national assembler does. A promotion refused for those files says the build stays published and to promote it again once they are deleted, instead of advising a publication without --make-current. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…their alerts return Only the UK national, dense and local-area releases publish into build folders. The June 2023 UK release and populace-uk-<year>-<tier>-k<N> releases still publish with tags, latest.json and their Slack alert, so the README, the agent guide, the data package's README and docstrings, tools/publish_release.sh and the changelog fragment now say so, and the wrapper and tools/release.env.example keep SLACK_WEBHOOK_POPULACE_UK for them. Publications into build folders send no alert until the dashboard posts one from releases.json. The runbooks describe the up-front refusals, the unavailable receipt and, for the dense release, listing each build first and promoting it once the pointer files are deleted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
UK releases keep publishing through the tagged publisher and the pointer files until their repository switches to releases.json, so the contract must accept the national, dense and local-area releases in the tagged layout again. These are main's tests for that layout, beside the build-folder tests, which now build their fixtures in that layout explicitly. The test that a UK release refuses the tagged layout moves to the switch. Part of the split for the switch: reverting this commit and the next one re-applies the contract's build-folder-only rule for UK releases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The contract checks a UK national, dense or local-area release in the layout its release manifest uses: the tagged layout today's assemblers write, with its per-build tags and the dense release's attempt_id, or the build-folder layout the emitter's publication uses. Every other release stays tagged. dataset_role_for_line and the dense per-build tag pattern, which the tagged path reads, come back. Part of the split for the switch: reverting this commit and the one before re-applies the build-folder-only rule for UK releases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er files Until the switch, the tagged publisher publishes the UK national, dense and local-area releases again, and promotes them through latest-<line>.json with line= and --promote-line, sending the release alert. These are main's tests for that path, beside the build-folder preparation tests. Part of the split for the switch: reverting this commit and the next one re-applies the removal of the old UK path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The tagged publisher accepts the UK national, dense and local-area releases again, and line= / --promote-line promote them through latest-<line>.json with the release alert, so UK Slack alerts keep being sent. tools/publish_release.sh and tools/release.env.example are main's again, with SLACK_WEBHOOK_POPULACE_UK. The build-folder preparation (prepare_build_folder_release) and the shared publication refusals stay. Part of the split for the switch: reverting this commit and the one before re-applies the removal of the old UK path and its alerts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Until the switch the UK national and dense assemblers keep writing the tagged manifests (build_id, attempt_id, cut_tag and per-build revisions) and printing tools/publish_release.sh commands. These are main's assembler tests again; the build-folder assembler tests, and the test that publishes an assembled national build through the emitter, move to the switch. Part of the split for the switch: reverting this commit and the next one re-applies the assemblers' move to the emitter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The UK national and dense assemblers are main's again: they write the tagged manifests, take --cut-tag, and print tools/publish_release.sh commands, so a UK build is published and promoted through the pointer files as today. This also takes out the dense assembler's separate --promote command added in review round 1. Part of the split for the switch: reverting this commit and the one before re-applies the assemblers' move to the emitter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The README's release section, the agent guide, the UK national and dense runbooks and microcosm-data's README are main's again: UK builds are assembled with tags, published and promoted through latest*.json pointer files with tools/publish_release.sh, and announced in Slack, until their repository switches to releases.json. This also takes out review round 1's wording for that period, which a narrower plan replaces. Part of the split for the switch: reverting this commit re-applies the documentation of the UK flow through the emitter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
So that no UK release is ever left without a way to change its current
build, each publication path refuses a repository in the other's layout:
- the tagged publisher refuses a repository that has releases.json, before
it writes a tag, a commit or a pointer file;
- microcosm-publish-release-build refuses a repository that still has any
latest*.json file, or whose files it cannot list, before any emitter
starts.
For a registry entry that names a release, the loader reads releases.json
where the repository has one and otherwise follows its pointer file as
before (main's line-pointer tests come back for that path), so load("uk")
no longer fails for want of releases.json; only the file's absence, not any
other error, falls back. The root-file escape hatch is refused only once
releases.json exists. A POINTER_FILES_PRESENT refusal now points to
tools/publish_release.sh, and review round 1's separate promotion advice
goes, since the up-front refusal covers that case.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… files No UK release can now reach a state where no build can be made current: - the tagged publisher reads releases.json at the main revision it commits on, and refuses a repository that has one before it writes anything; - microcosm-publish-release-build lists the repository's files with huggingface_hub and refuses, before the build is checked or any emitter starts, while any latest*.json file is there (the interface's is_pointer_file rule) or when the files cannot be listed. The loader reads releases.json for a registry entry that names a release only where the repository has one; otherwise it follows the entry's pointer file as before, latest-national.json for the UK national release, with main's line-pointer reading and role check. Only the file's absence falls back. build= needs releases.json, and unverified_root is refused only once it exists. A POINTER_FILES_PRESENT refusal now points to tools/publish_release.sh, and review round 1's separate promotion advice is gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…y's switch The README and microcosm-data's README describe the build-folder command beside today's UK flow: it refuses a repository that still has latest*.json pointer files, the tagged publisher refuses one that has releases.json, and UK releases keep publishing, promoting and sending Slack alerts through the pointer files until their repository's switch, which waits until the dashboard posts alerts from releases.json. The loader reads releases.json where a repository has one and the pointer files otherwise. The changelog fragment describes the narrowed change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…11-04 incident Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review round 2 found that the tagged publisher's releases.json check, and the loader's, treat huggingface_hub's LocalEntryNotFoundError as absence. huggingface_hub 1.18 raises it, as an EntryNotFoundError and a FileNotFoundError, when it could not ask the Hub: after a 5xx outlasted its retries, or on a 403. The fake Hubs now raise the Hub's own 404 error for a missing file, and these tests fail until the fix: - the tagged publisher refuses, writing nothing, when the read fails that way (no answer, 503, 403); - the loader does not fall back to the pointer file then, online; - the new command refuses an httpx network error while listing the repository, instead of a traceback; - its listing passes the credential the emitter reads, HF_TOKEN then HUGGINGFACE_TOKEN. Tests that already pass pin behaviour that holds: an offline load still falls back when releases.json was never cached, and each publisher refuses the other's manifest (a UK build-folder build through the tagged publisher, a tagged UK build through the new command). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The tagged publisher's releases.json check and the loader's now share microcosm.data.release.missing_on_hub: a download failure means the file is absent only when it is the Hub's EntryNotFoundError for a 404, not LocalEntryNotFoundError, which huggingface_hub raises when it could not ask the Hub (a 5xx after its retries, a 403) and nothing is cached. So during an outage the tagged publisher refuses before writing anything, instead of possibly writing a tag and a pointer file beside a releases.json, and the loader does not fall back to the pointer file. In offline mode, a releases.json that was never cached still reads as absent for the loader, as an offline load did before. The new command's listing turns httpx transport errors, such as a refused connection, into its "could not list" refusal, and passes HF_TOKEN, then HUGGINGFACE_TOKEN, as the emitter reads them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each publisher refusing the other's layout keeps a path for the UK national, dense and local-area releases. After the UK repository's switch, its June 2023 release (pointer latest.json) and populace-uk-<year>-<tier>-k<N> releases have none yet; the README says that is open for the switch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
anth-volk
marked this pull request as ready for review
November 5, 2026 13:41
This was referenced Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #1504
Hand-over step H2c, narrowed (tracker 1b · 3). Microcosm can publish a release build into its own folder through the separately installed emitter, while UK releases stay on today's tagged publisher and
latest*.jsonpointer files until their repository's switch (tracker 2c). Each publication path refuses a repository in the other's layout, so the UK national, dense and local-area releases always keep one way to change their current build. That does not yet hold for the UK repository's other releases after its switch; see Open for the switch below.Why it was narrowed
The first version moved the UK assemblers to the emitter and removed the old UK path. But the emitter refuses every change to a current build while any
latest*.jsonfile exists, so from its merge until the pointer files were deleted no UK build could have been made current, and UK Slack alerts would have stopped. Now UK releases keep publishing, promoting and alerting through the pointer files until one switch commit writesreleases.jsonand deletes them (2c · 4); only then do the UK assemblers move to the emitter (2c · 2).What this PR does
Publication into build folders (
microcosm.build.release_publication, commandmicrocosm-publish-release-buildinmicrocosm-build).publish_releasecall. The emitter's release writer writesreleases/<release>/<build>/andreleases.jsonin one commit.--make-currentpublishes the build as current,--promotemakes a published build current, and--preflight-onlychecks the build without starting an emitter.publishedand, when current was asked for, names the build ascurrent.HF_HUB_OFFLINEorTRANSFORMERS_OFFLINEset (staging_dataset.hub_offline);latest*.jsonfile (the interface'sis_pointer_filerule), or when its files cannot be listed, httpx network errors included. It lists them withhuggingface_hubin its own process, passingHF_TOKENor elseHUGGINGFACE_TOKEN, as the emitter reads them.staging_dataset.write_access_problem, which now takes the wording of the change it checks).build_folder_identity), and the tagged publisher refuses a build-folder one (it pins no revision); tests cover both.The tagged publisher (
microcosm-publish-release,tools/publish_release.sh) refuses a repository that hasreleases.json. It checks before writing a tag, a commit or a pointer file, reading the file at themainrevision its commit builds on. Only the Hub's 404 for the file (microcosm.data.release.missing_on_hub) lets it go on; huggingface_hub'sLocalEntryNotFoundError, which it raises when it could not ask the Hub (a 5xx after its retries, a 403), and every other error stop it before anything is written. Otherwise it is as onmain: it publishes the UK national, dense and local-area releases, promotes them withline=/--promote-linethroughlatest-<line>.json, and sends their Slack alerts.The release contract checks a UK release in the layout its release manifest uses:
attempt_id;releaseandbuildas strings in both manifests;built_at,built_with_model_packageandbuilt_with_core_packageat the top level; aroleon each artifact; and norevision.Every other release stays tagged.
The loader (
microcosm.data.load,download), for a registry entry that names a release (UK 2025 national and dense):releases.jsonwhere the repository has one: the current build, or a listed build thatbuild=pins (a withdrawn one loads with a warning, unchanged).latest-national.jsonfor the national release, with its role check), soload("uk")no longer fails for want ofreleases.json.releases.jsonfalls back to the pointer file (and, in offline mode, areleases.jsonnever cached, as an offline load did before). Any other error propagates, a server error included.build=needsreleases.json, andunverified_root=Trueis refused only once it exists.The UK assemblers are
main's: tagged manifests,--cut-tag, andtools/publish_release.shcommands.Kept from review round 1: the up-front offline and write-access checks, and command tests for the
pending,refusedandunavailablereceipts.Undone from review round 1: the dense assembler's separate
--promotecommand and the documentation for the pointer-file period. APOINTER_FILES_PRESENTrefusal now points totools/publish_release.sh, since the up-front refusal covers that case.The split for the switch (tracker 2c · 2)
These commits take the UK assembler, UK contract, old-path removal and alerts-stop changes out. Tracker 2c · 2, stacked on this PR, re-applies them by reverting them, newest first:
666dfbd90660873b3aline=,--promote-line,latest-<line>.json,tools/publish_release.sh,tools/release.env.examplefc324c8a8900a927a242bb85771ea2310c13microcosm-dataREADME)392deaaeaThe code and test reverts apply without conflicts (review round 2 tried them). What else 2c · 2 has to do when it reverts them:
dataset_role_for_line.660873b3abrings it back, and the loader's pointer-file fallback (d7bce422f, kept) imports it. Without itimport microcosm.datafails, because the package imports the loader, so every module and test of the package fails, not only the fallback. Keep the function, or remove the fallback in the same change.test_the_tagged_publisher_refuses_a_uk_promotion_once_releases_json_exists(fromae0e3271a) uses the helpers for UKlatest-<line>.jsonpromotion (_as_uk_national_line_release,_uk_hub) that the revert offc324c8a8removes; drop or rewrite it.test_an_assembled_national_build_publishes_through_the_emitter, which the revert of42bb85771restores, callspublish_release_build, which now lists the repository's files. Onlytest_uk_release_publication's fixture stubs that listing, so without a stub (_repository_files) the test would query the private UK repository: offline it fails with "could not list", and in CI's engine-free jobs it sends an anonymous request and fails on the 401.test_the_tagged_publisher_refuses_a_uk_build_folder_release(froma7a039ec0) only asserts aValueErrorand no Hub request, so it holds after the revert of900a927a2, whose refusal by release name comes first.392deaaeaconflicts with0592245b2in themicrocosm-dataREADME, whose paragraphs both edit; take round 1's text there.0592245b2's root README section and changelog fragment, and651e94d99's note on the other UK releases, describe the time before the switch and outlive the reverts, so 2c · 2 rewrites them.POINTER_FILES_PRESENTadvice (d7bce422f) sends the operator totools/publish_release.sh. After the switch that script refuses the repository and, by name, the three releases, so 2c · 2 changes the advice; the remedy then is deleting the stray pointer file. Round 1's separate advice for a promotion does not come back with the reverts.Release alerts
UK and US release alerts do not stop. Until a repository's switch, its releases publish through
tools/publish_release.shand the tagged publisher sends their Slack alerts as today (SLACK_WEBHOOK_POPULACE_UK,SLACK_WEBHOOK_POPULACE_US). The switch (2c · 4) waits until the dashboard posts alerts from changes toreleases.json(tracker 1b · 6). Publications throughmicrocosm-publish-release-buildsend none of their own, and none can happen before the switch.Open for the switch (tracker 2c)
After the UK switch, the UK repository's releases other than the three have no publication path, and
load("uk", 2023)loses its pointer:is_pointer_filematches everylatest*.json, so the switch has to deletelatest.json, the June 2023 release's pointer, as well aslatest-national.json;("uk", 2023)registry entry names no release and reads onlylatest.json;microcosm-publish-release-buildrefuses the June 2023 release andpopulace-uk-<year>-<tier>-k<N>IDs by name.This needs a decision for 2c, and it is being raised with Anthony; this PR does not change the code for it.
Pending
populace-us-2024-national, rolenational;populace-us-2024-local, rolelocal_area) are recorded inmicrocosm.data.contract.PROPOSED_US_RELEASESand read by nothing until they are agreed with the US data builder (tracker 2c · 5).datasetandcalibration_diagnostics:calibration_weightsfor the calibration weights, and the artifact's key otherwise.Environment variables
HF_TOKEN, thenHUGGINGFACE_TOKEN, then the tokenhf auth loginsavedmicrocosm-publish-release-buildhf auth loginon the build machineenv) and inherits its environmentHF_TOKEN, thenHUGGINGFACE_TOKEN, then huggingface_hub's own order (HUGGING_FACE_HUB_TOKEN, then the saved token underHF_TOKEN_PATHorHF_HOME)huggingface_hubinmicrocosm-publish-release-build's own process, listing the repository's filesHF_TOKENorHUGGINGFACE_TOKENtoHfApi, since huggingface_hub does not read the latterHF_HUB_OFFLINE,TRANSFORMERS_OFFLINEstaging_dataset.hub_offlinein the command, which refuses when either is true;huggingface_hubin the command and the emitterHF_ENDPOINT(optional)huggingface_hubin the command and the emitterMICROCOSM_EMITTER_COMMAND(optional)PATHXDG_CACHE_HOME(optional)MICROCOSM_UK_TERMINAL_GATE_SIGNING_KEY,POPULACE_UK_TERMINAL_GATE_SIGNING_KEY--preflight-onlytools/release.envon the build machine, or the operator's shelltools/publish_release.shsourcestools/release.env; formicrocosm-publish-release-build, the operator exports themSLACK_WEBHOOK_POPULACE_US,SLACK_WEBHOOK_POPULACE_UKnotify_release, from the tagged publishertools/release.envor the operator's shellmain: the wrapper sources the file and warns when neither is setHF_TOKEN(loading)huggingface_hubinmicrocosm.data.loadfor the private UK repositoryNo workflow, Docker, Terraform or Modal configuration changes, and no secret is added. PR CI receives no credential. Its tests use in-memory fakes for the emitter, the Hub file list and the Hub downloads, which raise huggingface_hub's own errors (
test_support/microcosm_data/hub_errors.py), and the shared fixture refuses to start a real emitter. As onmain, the live-Hub loader test reaches the Hub anonymously from CI's engine-free jobs; the UK cases skip on the 401.Tests
Tests first, then the change. Locally I ran only the tests these commits add or modify, each by node ID, from an explicit list that the run script refuses when empty. I ran them with
HF_HUB_OFFLINE=1and without the live-Hub loader test. CI runs the rest.aef137600merge ofmain(6874a31cb)325c0e278tests for review round 1 (offline and write-access checks, receipt outcomes)857e7cdde,4b3f1b36cthe review round 1 fixes666dfbd90contract tests (tagged UK layout)ReleaseContractErrorfrom the contract refusing the tagged UK layout, 6 assertions, 1AttributeErrorfor_UK_DENSE_CUT_TAG_RE, whichmain's mirror test reads), 150 passed660873b3afc324c8a8old UK path testsTypeErrorfor the removedline=keyword and 1SystemExitfor the removed--promote-line, the options being restored; 4 assertions; 1ValueErrorfrom the publisher refusing the UK release), 37 passed900a927a242bb85771assembler testsKeyError: 'cut_tag', 2 assertions), 62 passedea2310c13ae0e3271arefusals and loader fallbackDID NOT RAISE, 1DID NOT WARN, 9FileNotFoundErrorfrom the loader reading the missingreleases.jsonwithout falling back), 50 passed; none on a missing named7bce422f0592245b2a06f3d83bempty commit (re-push after GitHub's incident)6ab56bb13merge ofmain(0f0e777b2)a7a039ec0tests for review round 2 (only the Hub's 404 is absence; the listing's errors and credential; the two layout crossings), with the fake Hubs now raising huggingface_hub's 404 errorDID NOT RAISEfor the tagged publisher and the loader, 2 assertions for the credential, 1httpx.ConnectErrorraised from the command), 230 passed. Passing already: the offline fallback and both layout crossings, which pin behaviour that held9f3367cbethe fix651e94d99(head) README note on the other UK releasesruff checkandruff format --checkpass on the changed Python files, andpython3 tools/ci_test_plan.py verifypasses.🤖 Generated with Claude Code