docs: record cli 0.1.10 release evidence

Author: rohans0509

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

@@ -62,6 +62,12 @@ direction.
   `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`.
+- PyPI `codealmanac` `0.1.10` is published from GitHub Actions run
+  `28690993407`; a fresh public temp-home install with `uv tool install
+  --python 3.12 --refresh --no-cache --force codealmanac==0.1.10` passed for
+  version, root/local help, private local trigger/worker entrypoints, and
+  absence of stale `sync`, root scheduled `automation`, `local update`, and
+  `local jobs` help text.
 - 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`.
@@ -852,6 +858,16 @@ repaired.
   `codealmanac-local-trigger` and `codealmanac-local-worker` entrypoints, and
   absence of stale launch help for `sync`, root scheduled `automation`,
   `local update`, and `local jobs`.
-- Next step: commit the version/release-prep changes, push the release branch,
-  fast-forward `main`, run `publish.yml` with `confirm_version=0.1.10`, then
-  public-smoke PyPI before sending the RelayForge update.
+- Release branch `codex/cli-run-surface-release` and `main` have both been
+  pushed through commit `3c1aeaa`.
+- GitHub Actions publish run `28690993407` passed and published
+  `codealmanac` `0.1.10` to PyPI.
+- Fresh public temp-home install passed with `uv tool install --python 3.12
+  --refresh --no-cache --force codealmanac==0.1.10`.
+- Public smoke proved version `0.1.10`, root/local help, private
+  `codealmanac-local-trigger` and `codealmanac-local-worker` entrypoints, and
+  absence of stale launch help for `sync`, root scheduled `automation`,
+  `local update`, and `local jobs`.
+- RelayForge update was sent through `rohan-codex-019f05b3`.
+- Next step: continue the larger code-quality and hosted/local architecture
+  cleanup.

docs/codealmanac-launch/progress.md

@@ -1,31 +1,32 @@
 # Launch Progress
 
 Status: active.
-Updated: 2026-07-03.
+Updated: 2026-07-04.
 
 This file tracks the rough percentage estimates used in RelayForge updates.
 Percentages are planning estimates, not accounting metrics.
 
 ## Latest RelayForge Update
 
-Sent: 2026-07-03 after Slice 86 CodeAlmanac engine runs/workspaces.
+Sent: 2026-07-04 after Slice 90 CLI 0.1.10 release.
 
 Route:
 
 ```bash
 doppler run --project almanac --config dev -- \
   relayforge reply \
-  --config /Users/rohan/Desktop/Projects/relayforge/relay.config.json \
-  --binding rohan-almanac-main "..."
+  "CLI breaking surface is done. Published codealmanac 0.1.10 ..." \
+  --config /Users/rohan/Desktop/Projects/relayforge/relay.config.json
 ```
 
-Slice 86 moved engine run artifacts into `src/codealmanac/engine/runs/` and
-detached engine workspace management into `src/codealmanac/engine/workspaces/`.
-The composition root now has `app.engine.runs` and `app.engine.workspaces`, and
-local run preparation/execution/delivery are wired through that engine facade.
-Focused verification passed with `96 passed`; full local verification passed
-with `uv run ruff check src tests`, `uv run pytest -q --tb=short`
-(`514 passed`), and `git diff --check`.
+Result: `sent via rohan-codex-019f05b3`.
+
+Slice 90 published `codealmanac` `0.1.10` from `main` through GitHub Actions
+run `28690993407`. Public temp-home install smoke passed with `uv tool install
+--python 3.12 --refresh --no-cache --force codealmanac==0.1.10`; the installed
+CLI returned `0.1.10`, exposed `codealmanac`, `codealmanac-local-trigger`, and
+`codealmanac-local-worker`, and kept stale launch-facing `sync`, root scheduled
+`automation`, `local update`, and `local jobs` help text out of root/local help.
 
 ## Latest Local Notes
 
@@ -62,11 +63,11 @@ with `uv run ruff check src tests`, `uv run pytest -q --tb=short`
 
 | Area | Latest | Previous | Basis |
 | --- | ---: | ---: | --- |
-| CodeAlmanac backend/local | 100% | 99.9% | Slice 86 moved engine run artifacts/workspaces under `src/codealmanac/engine/`, added the `app.engine` facade, and passed focused/full gates. |
-| 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 backend/local | 100% | 100% | Slice 89 removed the old sync/automation implementation path and aligned local execution/history on `local runs`; Slice 90 public smoke verified the packaged private local trigger/worker entrypoints. |
+| CodeAlmanac CLI/public UX | 100% | 100% | Published CLI `0.1.10` passed public install smoke; stale launch-facing `sync`, root scheduled `automation`, `local update`, and `local jobs` help text is gone. |
 | 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 | 100% | 99% | Vercel now targets `thealmanac/codealmanac-hosted`, Render health is live, and Modal `codealmanac-hosted-updates` was redeployed with current `codealmanac` `0.1.9` engine logs. |
+| Infra/deploy rename | 100% | 100% | Vercel targets `thealmanac/codealmanac-hosted`, Render health is live, Modal `codealmanac-hosted-updates` was redeployed, and PyPI `codealmanac` `0.1.10` is live. |
 
 ## Update Rule
 

docs/codealmanac-launch/verification-matrix.md

@@ -1731,3 +1731,13 @@ Known residue:
   `local update`, and `local jobs`; and private
   `codealmanac-local-trigger` / `codealmanac-local-worker` entrypoints exposed
   help successfully.
+- Publish evidence: GitHub Actions run `28690993407` published
+  `codealmanac` `0.1.10` from `main` after passing tests, lint, diff hygiene,
+  build, artifact checks, artifact upload, and PyPI upload.
+- Public install evidence: a fresh temp-home install with
+  `uv tool install --python 3.12 --refresh --no-cache --force
+  codealmanac==0.1.10` succeeded after PyPI propagation. The installed package
+  returned version `0.1.10`, exposed `codealmanac`,
+  `codealmanac-local-trigger`, and `codealmanac-local-worker`, and kept stale
+  `sync`, root scheduled `automation`, `local update`, and `local jobs` help
+  text out of the launch-facing CLI.

docs/codealmanac-launch/worklog.md

@@ -2625,3 +2625,18 @@
   `codealmanac-local-trigger` / `codealmanac-local-worker` entrypoints, and
   rejected stale launch-facing `sync`, `automation`, `local update`, and
   `local jobs` help text.
+- Pushed release branch `codex/cli-run-surface-release` and fast-forwarded
+  `main` from `4f79c161` to `3c1aeaa`.
+- Published `codealmanac` `0.1.10` to PyPI through GitHub Actions run
+  `28690993407`. The workflow passed tests, lint, diff hygiene, build,
+  artifact checks, artifact upload, and PyPI upload.
+- Fresh public install smoke passed from a temp `HOME` with
+  `uv tool install --python 3.12 --refresh --no-cache --force
+  codealmanac==0.1.10`. The first attempt hit PyPI propagation; the second
+  installed `0.1.10`.
+- Public smoke verified `codealmanac --version`, root/local help, private
+  `codealmanac-local-trigger` / `codealmanac-local-worker` entrypoints, and
+  absence of stale launch-facing `sync`, root scheduled `automation`,
+  `local update`, and `local jobs` help text.
+- RelayForge update sent through binding `rohan-codex-019f05b3` with the public
+  install evidence and 100% status for CLI/public UX.