docs: record cli 0.1.9 publish

Author: rohans0509

docs/codealmanac-launch/next-agent-brief.md

@@ -45,10 +45,10 @@ cloud setup flow.
   `28671661249`; a fresh public `uv tool install --python 3.12 --refresh
   --no-cache --force codealmanac==0.1.8` smoke passed for version, root help,
   and signed-out human/JSON `codealmanac status`.
-- Local package `0.1.9` is ready for publish. Slice 79 removes root
-  `uninstall`'s stale scheduled-automation coupling; wheel smoke proved root
-  uninstall has no `--keep-automation` flag or automation JSON fields, while
-  `codealmanac automation uninstall` still exists.
+- PyPI `codealmanac` `0.1.9` is published from GitHub Actions run
+  `28672818638`; a fresh public `uv tool install --python 3.12 --refresh
+  --no-cache --force codealmanac==0.1.9` smoke passed for version, root
+  uninstall help/JSON, and explicit `codealmanac automation uninstall`.
 - Chrome verified the production CLI setup handshake again from an isolated
   temp `HOME`; `codealmanac setup --no-browser --target codex --yes` approved
   through `/cli-login` and completed as `rohans0509`.
@@ -658,8 +658,10 @@ repaired.
 - Distribution gates passed: clean `dist/`, Twine checks, isolated Python
   `3.12.9` wheel install, version smoke, root uninstall help/JSON smoke, and
   explicit automation uninstall help smoke.
+- PyPI `0.1.9` is live from GitHub Actions publish run `28672818638`, and a
+  fresh public install smoke passed with `--refresh --no-cache`.
 - Chrome production retry passed from a temp `HOME`: `/cli-login` rendered
   `CLI login approved`, and `codealmanac setup --no-browser --target codex
   --yes` completed as `signed_in` for `rohans0509`.
-- Next step: commit and push the slice, run the manual PyPI publish workflow
-  for `0.1.9`, then do a fresh public install smoke and RelayForge update.
+- Next step: send the RelayForge update if not already sent, then continue into
+  the next substantial launch slice.

docs/codealmanac-launch/progress.md

@@ -8,7 +8,7 @@ Percentages are planning estimates, not accounting metrics.
 
 ## Latest RelayForge Update
 
-Sent: 2026-07-03 after Slice 78 root status publish and smoke.
+Sent: 2026-07-03 after Slice 79 root uninstall split publish and smoke.
 
 Route:
 
@@ -19,19 +19,19 @@ doppler run --project almanac --config dev -- \
   --binding rohan-almanac-main "..."
 ```
 
-Published CLI `0.1.8` adds root `codealmanac status` as the one-command
-cloud diagnostic for identity, current checkout repository, triggers, and
-capture state. GitHub Actions publish run `28671661249` passed full tests,
-lint, diff hygiene, build, Twine checks, artifact upload, and PyPI upload.
-Fresh public PyPI install smoke passed after index propagation with
-`--no-cache`.
+Published CLI `0.1.9` removes root uninstall's stale local-scheduler coupling.
+GitHub Actions publish run `28672818638` passed full tests, lint, diff hygiene,
+build, Twine checks, artifact upload, and PyPI upload. Fresh public PyPI
+install smoke passed with `--refresh --no-cache`: root uninstall no longer
+shows `--keep-automation` or automation JSON fields, and explicit
+`codealmanac automation uninstall` remains available.
 
 ## Percentages
 
 | Area | Latest | Previous | Basis |
 | --- | ---: | ---: | --- |
-| CodeAlmanac backend/local | 97% | 97% | No local engine change in Slice 77; previous full suite passed with the repo-list service/workflow additions. |
-| CodeAlmanac CLI/public UX | 100% | 100% | Published CLI `0.1.8` passed public install smoke; root `status` now reports cloud identity, current repo, trigger count, and capture state. |
+| CodeAlmanac backend/local | 97% | 97% | No local engine change in Slice 79; full source gates still passed after the setup/uninstall split. |
+| CodeAlmanac CLI/public UX | 100% | 100% | Published CLI `0.1.9` passed public install smoke; root uninstall is now scoped to setup-owned artifacts, while automation teardown remains explicit. |
 | CodeAlmanac-hosted backend/auth/API | 100% | 100% | Slice 75 added production `/v1/repositories`; production repo list and repo status pass without per-repo permission fanout. |
 | Hosted frontend/onboarding | 100% | 99% | Slice 76 shipped repository readiness, capture handoff, maintained branches, and per-branch delivery to Vercel; Chrome verified production with no console errors. |
 | Infra/deploy rename | 99% | 99% | Hosted frontend deployed to Vercel production at `bff009b` and aliased to `https://www.codealmanac.com`. |

docs/codealmanac-launch/verification-matrix.md

@@ -67,6 +67,12 @@ Current evidence:
   works after the uninstall split: `codealmanac setup --no-browser --target
   codex --yes` from an isolated temp `HOME` rendered `CLI login approved` in
   Chrome and completed as `signed_in` for `rohans0509`.
+- Slice 79 published PyPI `codealmanac` `0.1.9` through GitHub Actions run
+  `28672818638`. A fresh public install with `uv tool install --python 3.12
+  --refresh --no-cache --force codealmanac==0.1.9` returned version `0.1.9`,
+  omitted `--keep-automation` from root uninstall help, omitted automation
+  fields from root uninstall JSON, and kept explicit
+  `codealmanac automation uninstall --help`.
 - `tests/test_cloud_auth_service.py` proves `~/.codealmanac/auth.json`
   save/load/delete behavior, mode `0600`, malformed-file recovery, identity
   fetch, and logout.

docs/codealmanac-launch/worklog.md

@@ -45,6 +45,15 @@
   `/cli-login` URL, Chrome rendered `CLI login approved`, and the terminal
   completed as `signed_in` for `rohans0509` while installing Codex instructions
   into the temp home.
+- Published `codealmanac` `0.1.9` to PyPI through GitHub Actions run
+  `28672818638`. The run passed full tests, lint, diff hygiene, build, Twine
+  checks, artifact upload, and PyPI upload.
+- Fresh public install smoke passed with
+  `uv tool install --python 3.12 --refresh --no-cache --force
+  codealmanac==0.1.9`. The installed binary returned version `0.1.9`, root
+  uninstall help omitted `--keep-automation`, root uninstall JSON omitted
+  automation fields, and explicit `codealmanac automation uninstall --help`
+  remained available.
 
 ## 2026-07-03 Slice 78: Root cloud status