docs: record slice 75 release verification

Author: rohans0509

docs/codealmanac-launch/progress.md

@@ -19,18 +19,17 @@ doppler run --project almanac --config dev -- \
   --binding rohan-almanac-main "..."
 ```
 
-Slice 74 verified Chrome/fresh-CLI production auth, fixed
-`codealmanac repo status` through GitHub App installation-token permission
-checks, and recorded that the canonical `codealmanac repo list` command is
-still absent from PyPI `0.1.5`.
+Slice 75 has since been completed locally: published CLI `0.1.6` includes the
+canonical `codealmanac repo list` command, production `/v1/repositories` works,
+and Chrome verified fresh setup from a clean `HOME`.
 
 ## Percentages
 
 | Area | Latest | Previous | Basis |
 | --- | ---: | ---: | --- |
-| CodeAlmanac backend/local | 96% | 96% | Local/backend unchanged in Slice 73. |
-| CodeAlmanac CLI/public UX | 98% | 100% | Published CLI `0.1.5` setup/capture/repo status work; `codealmanac repo list` is not implemented in the published package yet. |
-| CodeAlmanac-hosted backend/auth/API | 100% | 100% | Slice 74 fixed GitHub provider-limit handling and repo authorization hot path; production `repo status` and `repo triggers list` pass. |
+| CodeAlmanac backend/local | 97% | 96% | Full local suite passed with the repo-list service/workflow additions. |
+| CodeAlmanac CLI/public UX | 100% | 98% | Published CLI `0.1.6` setup/whoami/repo list/repo status/capture status passed against production from a clean Chrome-approved HOME. |
+| 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 | 99% | 98% | Production setup and CLI guide copy now match the public CLI; Chrome verified stale setup-capture wording is gone. |
 | Infra/deploy rename | 99% | 99% | Hosted frontend deployed to Vercel production at `af0d7da` and aliased to `https://www.codealmanac.com`. |
 

docs/codealmanac-launch/verification-matrix.md

@@ -1497,3 +1497,31 @@ Known residue:
   `/dashboard/local-agent-access?smoke=slice73` contain
   `codealmanac capture enable` and do not contain stale setup-capture install
   wording.
+
+## Slice 75 Cloud Repo List
+
+- Hosted `GET /v1/repositories` returns repositories mirrored from GitHub App
+  installations visible to the signed-in CLI user.
+- The route intentionally does not fan out to per-repository collaborator
+  permission checks, avoiding the GitHub user-token rate-limit hot path found in
+  Slice 74.
+- `codealmanac repo list [--limit N] [--cursor C] [--json]` is the canonical
+  public command; `repos` remains intentionally absent.
+- Hosted focused tests passed:
+  `uv run pytest tests/test_cli_repositories_api_contract.py
+  tests/test_repositories_api_contract.py tests/test_core_access_contracts.py
+  tests/test_repositories_contract.py`.
+- CodeAlmanac full verification passed: `uv run pytest` (`505 passed`), Ruff
+  on the touched CLI parser, and `git diff --check`.
+- Production API smoke passed:
+  `GET https://api.codealmanac.com/v1/repositories?limit=5` returned
+  `AlmanacCode/codealmanac`, repo id `1212149375`, account id `264516179`.
+- GitHub Actions publish run `28667216307` passed; PyPI accepted
+  `codealmanac-0.1.6`.
+- Fresh temp install with
+  `uv tool install --python 3.12 --upgrade --force --refresh codealmanac`
+  installed `0.1.6` and exposed `codealmanac repo list`.
+- Chrome verified fresh setup from a clean `HOME`; the hosted
+  `/cli-login` page rendered `CLI login approved`, the terminal saved the CLI
+  token, and the same clean `HOME` passed `whoami`, `repo list`, `repo status`,
+  and `capture status` against production.

docs/codealmanac-launch/worklog.md

@@ -2153,3 +2153,26 @@
 - Focused CodeAlmanac verification passed:
   `uv run pytest tests/test_cloud_repositories_service.py
   tests/test_cloud_repo_workflow.py tests/test_cli.py -q`.
+- Full CodeAlmanac verification passed: `uv run pytest` (`505 passed`),
+  `uv run ruff check src/codealmanac/cli/parser/repo.py`, and
+  `git diff --check`.
+- CodeAlmanac commit `a6da193562e74b63387f457a8099e458eba84f79` was pushed
+  to `origin/dev` and `origin/main`.
+- Hosted backend commit `4c986cf` was pushed to hosted `origin/main`; production
+  `GET https://api.codealmanac.com/v1/repositories?limit=5` returned
+  `AlmanacCode/codealmanac`, repo id `1212149375`, account id `264516179`.
+- GitHub Actions publish run `28667216307` passed and PyPI accepted
+  `codealmanac-0.1.6`.
+- Fresh temp install with
+  `uv tool install --python 3.12 --upgrade --force --refresh codealmanac`
+  installed `0.1.6` and exposed `codealmanac repo list`.
+- The real user install was upgraded from `0.1.4` to `0.1.6` with the same
+  `uv tool install --python 3.12 --upgrade --force --refresh codealmanac`
+  command.
+- Chrome verified a fresh setup from a clean `HOME`:
+  `codealmanac setup --no-browser --yes` opened
+  `https://www.codealmanac.com/cli-login`, rendered `CLI login approved`, saved
+  the CLI token, and installed Codex/Claude instruction files.
+- The same clean Chrome setup `HOME` passed production CLI smoke:
+  `codealmanac whoami`, `codealmanac repo list`, `codealmanac repo status`, and
+  `codealmanac capture status`.