Repository navigation
Description
Filed by epic #154's coordinator (operator-approved, 2026-11-14). Runs after #151, which keeps today's wrapper as its UV_WRAPPER.
Why
deploying-releasesships a shared co-pypi wrapper (init-project-fastapi: replace the find-links wheelhouse with the co-pypi Artifact Registry index (Path C) gregoryfoster/skills#632,cd7471ff). Itsretrofit.md§1 replaces a repo's own wrapper with it:install.sh --co-pypi --replaceinstallsscripts/co-pypi.shandscripts/co_pypi_token.pyas marked copies that are never edited. Watcher, processor and broker each have a wrapper that only runsuv[measured 2026-11-14].- Replicator's wrapper has one extra mode,
wheels OLD NEW DIR(Resolve co-core from the co-pypi Artifact Registry index, retiring the GCS wheelhouse (#169 part 1) #183). It fetches co-core's three wheels at two versions and checks them against the index's sha256, soscripts/co_core_closure_diff.py(Keep the co-core import-closure diff as a script, not a rebuild per pin move #145) can diff the import closure. DEPENDENCIES.md requires that diff before every pin move. The shared wrapper has no such mode [measured: version 1 at skills55ede55f]. - The closure diff stays (operator, 2026-11-14). Of the last 8 pin moves, 6 found changed co-core code inside Replicator's closure [measured from the pin comments]. In Catch up co-core 0.40 → 0.41 (BlobStore reporting twins: keep SweepSafeLocalBlobStore's retry where calls reach it) #179 that changed what shipped: the blob store's reporting twins would have bypassed
SweepSafeLocalBlobStore's retry, which led to the guard intests/storage/test_local_store.py. Thewheelsmode is only the plumbing that feeds it.
Goal
Adopt the shared wrapper unmodified. Move the wheel fetch out of the wrapper into its own tool, built so it can later be proposed upstream as-is (operator, 2026-11-14), alongside the closure diff. No upstream filing in this issue: the proposal comes later, with the operator's consent.
Built for upstream adoption: the fetcher
- No repo-specific names.
- The package list comes from arguments, with no Replicator default.
- The key is read the way the shared wrapper reads it:
CO_PYPI_KEY, else/etc/<[project].name>/co-pypi-reader.json. - No
REPLICATOR_variable, and no path undersrc/.
- Runs through the shared wrapper. Prefer a plain
uvinvocation throughbash scripts/co-pypi.sh uv …, so the token handling isn't duplicated.- First test whether one can fetch a wheel file with its index hash checked.
uvhas nodownloadcommand, so try a--no-depsinstall or a lock-then-fetch. - If no
uvinvocation does it, the tool mints its token throughscripts/co_pypi_token.py's interface and allowlist, never a second copy of them. Say on this issue which path you took, and why.
- First test whether one can fetch a wheel file with its index hash checked.
- Self-contained. One script, plus a test file that needs nothing from Replicator, and a header that states its contract, the way the shared wrapper's does. It should drop into
skills/deploying-releases/assets/co-pypi/unchanged. - The output stays what the closure diff reads:
<dir>/<normalized>-<version>-py3-none-any.whl, each sha256-checked against the index. A failed check, or a version missing from the index, exits nonzero and names the file.
The closure diff: note, don't change
scripts/co_core_closure_diff.py is already parameterised (--root, --package, --wheels), with only its defaults Replicator's. List on this issue what would have to move for it to ship upstream beside the fetcher: the defaults, the docstring's issue refs, and the test fixtures. Don't generalise it here. Change only its error messages, which name co-pypi.sh wheels, to name the new fetch command.
Steps
- Vendored skills at or past
cd7471ff, the commit that ships the co-pypi assets. Run replicator's unit from a release, not/home/exedev/replicator(CannObserv/broker#22's rollout, replicator first) #151's first step bumps the submodule, so check where it landed. - Install the shared wrapper:
install.sh --co-pypi --replace, theninstall.sh --check.- Our
tests/test_co_pypi_token.pygoes, because the skill'stests/test_co_pypi.pycovers the pair (retrofit.md §1). First check that each case it holds is covered there, and list any that isn't.
- Our
- The key variable:
REPLICATOR_CO_PYPI_CREDENTIALS→CO_PYPI_KEY.- The default path
/etc/replicator/co-pypi-reader.jsonexists,root:exedev 640, soexedevcan read it [measured]. A host shell and the deploy need no variable. git grepnames it in [measured on91e87dc]:README.md,docs/COMMANDS.md,docs/DEPENDENCIES.md,docs/ENVIRONMENT.mdand the manifest;- both wrapper scripts, which are replaced in step 2;
docs/plans/2026-11-10-co-pypi-index-design.md, which is history, so it stays.
ci.ymldoesn't name it [measured].- Any env-file entry is production config. Removing one from
/etc/replicator/.envis the operator's write: prepare the exact command.
- The default path
- The fetcher, as above. It needs a test first, red before the script exists. Port
wheels' cases: the sha256 mismatch, the missing version, and the normalized names. - Docs: the fetch line in
docs/DEPENDENCIES.md("Moving the pin", and "Ask the index, not a cache"),docs/COMMANDS.md:9,docs/TESTING.md:24(REPLICATOR_TEST_CLOSURE_WHEELS's fill command), and the manifest entries at.socraticodecontextartifacts.json:101and:151. The manifest edit owes acodebase_update. - Gates:
- the default suite, clean and loaded (baseline on
91e87dc: 2009 passed, 1 skipped); - the closure-diff real-wheel test, with
REPLICATOR_TEST_CLOSURE_WHEELSfilled by the new fetcher (38 passed on Catch up co-core 0.45 → 0.46 (co-pypi index; closure diff version-only) #199); tests/ci;- ruff;
- CI green by job;
- a dry pin move: fetch 0.45.0 and 0.46.1 with the new tool, then reproduce Catch up co-core 0.45 → 0.46 (co-pypi index; closure diff version-only) #199's closure report byte for byte.
- the default suite, clean and loaded (baseline on
Done when
scripts/co-pypi.shandscripts/co_pypi_token.pyare the skill's copies, andinstall.sh --checkis clean.- The fetcher reproduces Catch up co-core 0.45 → 0.46 (co-pypi index; closure diff version-only) #199's 0.45.0 → 0.46.1 report byte for byte.
- No doc names
co-pypi.sh wheelsorREPLICATOR_CO_PYPI_CREDENTIALS, except design-doc history. - The upstream-readiness list (the fetcher, plus what the closure diff would need) is posted on this issue.
- The operator has the env-file command.
Restart: likely none. The service doesn't run the wrapper; it runs a deploy's uv sync [traced]. Step 3 decides, and says so here.
Activity
#151 chore: bump gregoryfoster-skills 4f26e316 → 55ede55f (deploying-…
#151 feat: run both units from a release built by the deploying-relea…
gregoryfoster commentedon Nov 14, 2026
For #201: what #151 changed under this issue (coordinator, 2026-11-14)
/home/exedev/replicator(CannObserv/broker#22's rollout, replicator first) #151, which shipped.shipping-workdeploys on every ship now (.skills/deploy_command=setsid -w scripts/deploy.sh), and each deploy builds a third release mid-run (~+248M).scripts/deploy_hooks.sh.:41-43name this issue and setUV_WRAPPER=scripts/co-pypi.sh.:48exportsREPLICATOR_CO_PYPI_CREDENTIALS, defaulting to/etc/replicator/co-pypi-reader.json, because this repo's wrapper has no default key path (Run replicator's unit from a release, not/home/exedev/replicator(CannObserv/broker#22's rollout, replicator first) #151's pickup correction 2).deploy.shbuilds through the new wrapper, andworker readynames the new sha12.55ede55f(Run replicator's unit from a release, not/home/exedev/replicator(CannObserv/broker#22's rollout, replicator first) #151's bump) already hascd7471ff, so step 1 is met. The 22:52Z note on Run replicator's unit from a release, not/home/exedev/replicator(CannObserv/broker#22's rollout, replicator first) #151 says what the next bump (Wave 8 set D) will show intests/deploy.gregoryfoster commentedon Nov 15, 2026
Pre-flight against
7706bf0(coordinator, 2026-11-15)This is the next child on #154. #204 shipped: root is 30 GiB at 54%, so this ship's deploy has room [measured]. The brief is the body, plus the 2026-11-14 "For #201" note.
What's moved since the body
mainis8f2dbfae, 21 commits past the vendored55ede55f.assets/co-pypi/test_co_pypi.pychanged.deploying-releases-co-pypi: version 1, with the same sha256 (ff3579e0…) [measured].mainfirst, soinstall.sh --co-pypicopies the newest test./home/exedev/replicator(CannObserv/broker#22's rollout, replicator first) #151 says what it changes: no core change, and three newtests/deployunit tests that passed on our units off-host.55ede55f.git grep -nE 'co-pypi\.sh wheels|REPLICATOR_CO_PYPI_CREDENTIALS'outsideskills-vendoranddocs/plans[measured on7706bf0] finds these, beyond the body's list:tests/deploy/test_deploy_hooks.py:66-71,test_the_wrapper_finds_its_key_without_an_env_file. It asserts that the hooks exportREPLICATOR_CO_PYPI_CREDENTIALS. It turns red when the export goes, which is expected. Rewrite it to prove the shared wrapper's own default instead.scripts/deploy_hooks.sh:41-48(the For Adopt the shared co-pypi wrapper; move the wheel fetch to its own upstream-ready script #201 note), and.socraticodecontextartifacts.json:171(release-deploy-hooks), a third manifest entry beside:101and:151.scripts/co_core_closure_diff.py:10,:116,:127,:424, andtests/test_co_core_closure_diff.py:12,:353,:383,:391,:431: the error and help strings that nameco-pypi.sh wheels. They change with the fetcher (the body's "change only its error messages"), and the tests that pin them change too.docs/DEPENDENCIES.md's sites are now:31,:37and:69;README.md:77,:121;docs/COMMANDS.md:6,:9;docs/ENVIRONMENT.md:25,:65;docs/TESTING.md:24./srv/replicator/liveruns7706bf05cc16, and the previous release isb61703aee439(KEEP=0).scripts/deploy.sh <sha12>remains the rollback.deploy.shexits 0 on the merge, andworker readynames its sha12.7706bf0:tests/deploy: 32;tests/ci: 44;gregoryfoster commentedon Nov 15, 2026
Brief review against
origin/main(4ae39d3), before building (implementer, 2026-11-15)origin/mainis4ae39d3, one commit past the pre-flight's7706bf0. Seven corrections. Two of them add work: apyproject.tomlgroup and a ruff exclude. One changes the fetch path from the brief's fallback. The rest of the brief checks out.1. The submodule bump is already on main
4ae39d3("chore: update skills submodules", the refresh hook, 01:17Z) moved skills to8f2dbfae, the then-currentmainthe pre-flight recommends. CI run 43662387983 on it succeeded. This branch bumps nothing. The wrapper is still version 1,ff3579e0…[measured].2. The shared wrapper needs two
pyproject.tomledits the brief doesn't listBoth
install.sh --co-pypi(itswarn_setup) and thetests/test_co_pypi.pyit installs require them:[dependency-groups] co-pypi = ["google-auth[requests]>=2,<3"], then a relock. The wrapper runs the minter asuv run --project <checkout> --frozen --only-group co-pypi. Without the group, every run falls back to resolving google-auth from PyPI and warns.uv.locktherefore moves, which makes this a dependency change, so the worktree gets its own venv. google-auth 2.56.3 and requests 2.34.2 are already locked [measured], so I expect the diff to be the group alone."scripts/co_pypi_token.py"in[tool.ruff] extend-exclude. The minter's lazy google import trips the selectedPLC0415, and a--fixwould break its marker.3. The installed test covers none of
test_co_pypi_token.py's casesThe installed
tests/test_co_pypi.pyonly reads files. It checks the markers, the index, the lock and the group. The behavioural cases are covered upstream, in skills'tests/structural/test_deploying_releases_co_pypi.py, which is the "this repo's suite" in retrofit.md §1.Mapped case by case, every wrapper case of ours is covered there except two. Both run the real google-auth loader, where upstream substitutes a stand-in
googlepackage:GOOGLE_APPLICATION_CREDENTIALS, withgoogle.auth.defaultpatched to fail;{}key file failing the mint through the real loader.One case changes meaning on purpose: "unset key variable → exit 2" becomes "unset →
/etc/replicator/co-pypi-reader.json". Thewheelscases move to the fetcher's test.tests/test_dependency_index.pynow overlapstest_co_pypi.py's index and lock checks. I'm leaving that alone, because it's out of scope.4. Fetch path: under the wrapper, not through the minter's interface
No
uvinvocation writes a.whl[measured, uv 0.13.5]. There's nouv pip download.uv pip install --no-deps --targetleaves an unpacked tree, and so does its cache (archive-v0), with no wheel file anywhere. A lock-then-fetch still needs something other than uv to do the fetch.The brief's fallback is to mint through
co_pypi_token.py's interface. I'm taking a third path that duplicates even less: run the fetcher under the wrapper.UV_INDEX_CO_PYPI_USERNAME/_PASSWORDinto uv's allowlisted environment, anduv runhands that environment to the fetcher. So the fetcher reads the same pair uv would.uvspawns inherits the pair".[[tool.uv.index]]namedco-pypi, the name the two variables encode.5. Four more sites the brief's regex misses
git grepon4ae39d3finds these as well:docs/DEPENDENCIES.md:36-50. It citestests/test_co_pypi_token.py, and its "One key, no fallback … exits 2" no longer holds.docs/ENVIRONMENT.md:65: "there is no fallback".docs/ARCHITECTURE.md:67: the scripts list, which gains the fetcher..socraticodecontextartifacts.json:150: the path entry whose description is:151./etc/replicator/.envholds the variable (one line). The repo.envdoesn't [measured]. The operator's command will follow with the build.6. The real-wheel gate needs 0.36.0 and 0.37.0 too
test_reproduces_136_for_0_36_to_0_37reads those two versions. So the new fetcher fillsREPLICATOR_TEST_CLOSURE_WHEELSwith 0.36.0 and 0.37.0, and fetches 0.45.0 and 0.46.1 separately for the dry run. The reference for "byte for byte" is the pin comment's verbatim block inpyproject.toml, which #199 checked against the script.7. The deploy's first use runs the main checkout's venv
deploy.shcallsbash $SRC/scripts/co-pypi.shwith$SRCset to the checkout and the working directory set to the release.--projectis its own parent directory. So the ship's deploy first runsuv run --project /home/exedev/replicator --frozen --only-group co-pypiagainst the main checkout's dev.venv. That run is inexact and google-auth[requests] is already installed, so I expect a no-op.uv sync --locked --no-dev.co-pypiisn't a default group, so the release venv is unchanged.Proceeding with the build in worktree
201-shared-co-pypi, on4ae39d3.gregoryfoster commentedon Nov 15, 2026
Built: PR #205, gates on
dd94444(implementer, 2026-11-15)Six commits on
201-shared-co-pypi, based on4ae39d3. The brief corrections above still stand. The fetch path is the one correction 4 describes: the fetcher runs under the wrapper and touches nothing in the minter.What changed
install.sh --co-pypi --replaceinstalled it from skills8f2dbfae, andinstall.sh --co-pypi --checkreportscurrent 1 1.pyproject.tomlgainsco-pypi = ["google-auth[requests]>=2,<3"]and the ruff exclude for the minter.env -i PATH HOME), so it minted from the default key path.tests/test_co_pypi_token.pyis gone. Its coverage mapping, with the two real-loader gaps, is in correction 3.scripts/co_pypi_wheels.py.tests/test_co_pypi_wheels.pyfailed 2 and errored 30 with no script, then passed 32 once it existed.wheels' cases: the sha256 mismatch, the missing version, the off-host token and redirect, the dropped connection, and the normalized names.main, and the script run as a command.--wheelshelp, and the docstring's example.:39, "the wrapper'swheelsverb"), which now names the fetcher.test_the_wrapper_finds_its_key_without_an_env_filewas rewritten test-first.*CO_PYPI*variable.key_path({})is/etc/replicator/co-pypi-reader.json.:101,:151and:171.git grep -nE 'co-pypi\.sh wheels|REPLICATOR_CO_PYPI_CREDENTIALS'finds nothing outsidedocs/plans,skills-vendorand one negative assertion in a test.Gates
The full output of each gate is saved on the host under
~/gate-logs/201/.4ae39d3dd94444env -i)REPLICATOR_TEST_CLOSURE_WHEELSfilled by the new fetchertests/deploy, clean and loadedtests/cico-pypi.sh uv lock --check, empty environmentinstall.sh --co-pypi --checkcurrentThe counts reconcile: 2028 − 32 (
test_co_pypi_token.py) + 14 (test_co_pypi.py) + 32 (test_co_pypi_wheels.py) = 2042. The one skip is the real-wheel test, which needs the directory variable.Wheels [measured]:
wheelsverb's, which I fetched before the swap.uv.lock's sha256.co_core-0.99.0-py3-none-any.whl is not on …/co-core/and writes nothing, and a run outside the wrapper exits 2 and names it.Dry pin move:
co_core_closure_diff.py 0.45.0 0.46.1 --wheels <new fetcher's dir>is byte-identical (909 bytes) to the verbatim block inpyproject.toml's pin comment, which is #199's report. The new script sits inscripts/, one of the roots, and leaves the closure unchanged.CI run 43663540530 on
dd94444succeeded in all four jobs: test, lint, gcs and browser.Upstream-readiness list (nothing filed)
The fetcher,
scripts/co_pypi_wheels.pyplustests/test_co_pypi_wheels.py, is ready as-is.[[tool.uv.index]]namedco-pypi.assets/co-pypi/) or in../scripts/(a consumer), and needs no network, key or repo.What adoption would still need, all of it on the skill's side:
deploying-releases-co-pypiversion and sha256 lines.install.sh --co-pypiwould then carry three files, or two plus an optional third. Until this repo reinstalls with--replace,--checkwould call its copy foreign.warn_setupandtest_co_pypi.py's ruff check would have to cover it too.tests/structural/test_deploying_releases_co_pypi.py, not in the consumer's file-read test.The closure diff,
scripts/co_core_closure_diff.py: what would have to move. This is noted only, and nothing here has changed.DEFAULT_ROOTS = ["src", "scripts"]is this repo's layout, andDEFAULT_PACKAGESis co-core's three. Upstream, both should be required flags, or roots could default to the project's own package.pyproject.tomlpin-comment convention its output is shaped for._normalizeonly turns-into_. The fetcher normalizes by the wheel spec (lowercase, runs of-_.→_). They agree for co-core's names. A general tool needs the fetcher's rule, or it will look for files the fetcher never writes.tests/test_co_core_closure_diff.pyimportsfrom scripts.co_core_closure_diff import …. Upstream it would load the script by path, as the fetcher's test does.tmp_pathand portable, but they use co-core's names.test_reproduces_136_for_0_36_to_0_37stays here. It seeds from this repo's livesrc/andscripts/, asserts this repo's counts (57 files, six not identical), and readsREPLICATOR_TEST_CLOSURE_WHEELS.argparse,ast,difflib,zipfile), and it already names the new fetch command.Operator: the env-file line
/etc/replicator/.envline 7 isREPLICATOR_CO_PYPI_CREDENTIALS, and its value is the wrapper's default path [measured by comparison, not printed]. Line 6 above it is a stale comment,# SA key for the wheelhouse mirror (ExecStartPre sync_wheelhouse.py).. Nothing reads either line any more. The shared wrapper ignores the variable and leaves it off its allowlist, and the worker never read it. So no restart is owed, and the order relative to the deploy doesn't matter.Skipped verification
ty: it doesn't gate, per AGENTS.md.-m integration,-m gcsand-m browserlocally: nothing undersrc/changed. CI's gcs and browser jobs cover the latter two, and nothing covers integration in this round.codebase_update: SocratiCode indexes the main checkout, so it runs after the merge.Decisions to flag
BUILD_IDis the one deliberate exception" to theREPLICATOR_prefix.CO_PYPI_KEYisn't a Replicator setting, and nothing here sets it, so ENVIRONMENT.md says that where the variable is documented.tests/test_dependency_index.pyoverlapstest_co_pypi.py's index and lock checks. I left it alone because it's out of scope.--projectis the checkout, and it runsuv run --frozen --only-group co-pypithere (correction 7). That sync is inexact, andgoogle-auth[requests]is already installed there, so I expect no change.#201 docs: CR 1 — CO_PYPI_KEY is read by neither env file, not listed…
#201 docs: CR 2 — the README's override table drops the unset CO_PYPI…
#201 docs: CR 3 — TESTING.md links the fetch instead of quoting it un…
#201 fix: CR 4 — the fetcher turns an unusable dest or a non-UTF-8 pa…
gregoryfoster commentedon Nov 15, 2026
Shipped:
a8900f5, deployed and live (2026-11-15)PR #205, fast-forwarded onto main (
4ae39d3..a8900f5, 10 commits). ItsCloses #201becameRefsbefore the push, so this closes only now, after the deploy.install.sh --co-pypi --checkreportscurrent 1 1on main.scripts/co_pypi_wheels.py. Its 12 real wheels are byte-identical to the oldwheelsverb's, and the dry pin move reproduces Catch up co-core 0.45 → 0.46 (co-pypi index; closure diff version-only) #199's report byte for byte (both in the Built comment above).co-pypi.sh wheelsnor the old key variable outsidedocs/plans.git grepon main finds only a test asserting the old name is absent.df459e0..a8900f5) changed four things:CO_PYPI_KEYis documented as read by neither env file, instead of sitting under the service's.--destor a non-UTF-8 index page into an exit-1 error that names it, where both used to end in a traceback. Its two tests failed first.Proof
a8900f5:tests/deployandtests/ci: 76 passed;scripts/deploy.sh a8900f5…exited 0 and logged "worker ready" ona8900f5d15a2(pid 49915).*CO_PYPI*variable at all. The wrapper mints a token before everyuvit runs, so the release'suv sync --locked --no-devminted from the default key path. That's the first production use of the new wrapper.releases/a8900f5d15a2, and itsco-pypi.shis the marked copy (ff3579e0…).NRestarts=0, and its journal shows no warning since the restart.Follow-up:
/etc/replicator/.env(the old key variable and its stale wheelhouse comment) is still yours. The exact command is in the Built comment above. Nothing reads either line, so this can happen at any time and owes no restart.Known limits:
-m integrationwasn't run this round; nothing undersrc/changed.updatewas refused because this session's server held the index lock. That server's watcher ran the incremental update instead, andcodebase_context_searchreturns the new DEPENDENCIES.md and COMMANDS.md text.gregoryfoster commentedon Nov 15, 2026
Follow-ups done (2026-11-15)
/etc/replicator/.envlost exactly lines 6–7, the stale wheelhouse comment and the old key variable.root:exedev 640), and the backup was removed.load_env.shnow exports no*CO_PYPI*variable.deploying-releases'assets/co-pypi/. It lists what adoption needs (markers, a ruff exclude, where the test goes, docs) and includes the two real-loader cases as an optional extra.install.sh --co-pypi --replace. Until then,--checkwill call the fetcher foreign.gregoryfoster commentedon Nov 15, 2026
Verified (coordinator, epic #154, 2026-11-15T04:3xZ)
Everything below was read during this check-in [measured]:
7706bf0..a8900f5, 11 commits, all fast-forward. The skills-refresh hook's bump4ae39d3came first, then the 10 commits of PR #201 Adopt the shared co-pypi wrapper; fetch wheels with their own script #205.a8900f5./srv/replicator/livepoints toreleases/a8900f5d15a2, and the previous release is7706bf05cc16.b61703aee439was pruned (KEEP=0)./home, andNRestarts=0.BUILD_ID=a8900f5d15a2, and the worker was started at 03:52:41Z.check_redis_floor(Redis 7.0.15).enabled.journalctl -t replicator-failureis empty, and no unit has failed.co-pypi.shis byte-identical to main's.deploying-releases-co-pypiversion 1 markers (ff3579e0…,f6c3fedd…).install.sh --co-pypi --checkreportscurrent 1 1against skills8f2dbfae./etc/replicator/.envhas no line matchingCO_PYPIorwheelhouse. It isroot:exedev 640, no.bak-201is left, and a loaded shell exports no*CO_PYPI*variable.env -i PATH HOME bash scripts/co-pypi.sh uv run --no-project python scripts/co_pypi_wheels.pyfor 0.36.0, 0.37.0, 0.45.0 and 0.46.1. It exited 0 and wrote 12 wheels.uv.lock's sha256.tests/test_co_core_closure_diff.pyran 38 passed.pyproject.toml's pin comment.a8900f5:env -u REPLICATOR_REDIS_URL) and loaded;tests/deployandtests/ci: 76 passed;ruff checkandruff format --check: clean.codebase_context_searchreturns Adopt the shared co-pypi wrapper; move the wheel fetch to its own upstream-ready script #201's new text from DEPENDENCIES.md (the fetcher paragraph) and COMMANDS.md (the fetch command). That discharges the epic's manifest re-embed debt from Run replicator's unit from a release, not/home/exedev/replicator(CannObserv/broker#22's rollout, replicator first) #151.Carried to the epic:
install.sh --co-pypi --replace. Until then,--checkcallsco_pypi_wheels.pyforeign. Also watching Shared import-closure diff for wheelhouse-pinned libraries (co-core pin moves), lifted from CannObserv/replicator gregoryfoster/skills#454.-m integrationwasn't run, and nothing undersrc/changed.test_co_pypi_token.pyare not covered here or upstream. They are offered in skills#652.tests/test_dependency_index.pyoverlapstest_co_pypi.py.*CO_PYPI*variable set. The pre-flight asked for exactly that proof.Nothing is owed. This issue is closed already.