Skip to content

Release the Windows-Local AI clerk-minutes-timeout fix bundled in CivicSuite v1.0.2 - #177

Merged
scottconverse merged 4 commits into
mainfrom
work/windows-local-ai-clerk-minutes-timeout
Jul 4, 2026
Merged

scottconverse merged 4 commits into
mainfrom
work/windows-local-ai-clerk-minutes-timeout

Conversation

@scottconverse

Copy link
Copy Markdown
Contributor

Merges commit fa1874e (clerk minutes AI timeout + soft-dependency handling) that ships in the CivicSuite Windows Local v1.0.2 MSI but has lived only on this work branch. Getting it onto main so it can be cut as a proper release (v1.0.5) and close the ahead-of-tag disclosure in the umbrella PROVENANCE. Code is the exact bytes Phase D validated.

@scottconverse
scottconverse force-pushed the work/windows-local-ai-clerk-minutes-timeout branch from 7342223 to 35ab0eb Compare July 4, 2026 02:10
scottconverse and others added 2 commits July 4, 2026 09:47
…ocal-task-queue migration)

The shipped local-AI minutes path (fa1874e) depends on CivicCore's
civiccore_0003_local_task_queue Alembic migration, but the frozen v1.2.0
wheel predates it — so tests/test_milestone_2's real-pgvector upgrade
asserts the civiccore head is 0003 and got 0002. CivicCore v1.2.1 publishes
0003 as the alembic head (0001 -> 0002_llm -> 0003_local_task_queue),
released as a full attested asset set (wheel + sdist + SHA256SUMS +
Sigstore attestation) matching v1.2.0's profile.

Advance every LIVE freeze reference to v1.2.1 and its release-attested wheel
(sha256 8dde2940...): runtime pin (pyproject), the pip-install pin in ci.yml,
cleanroom Dockerfile ARG + runner (FREEZE_TAG/PACKAGE_VERSION/version assert/
provenance), the cleanroom/preflight/release workflows, both fresh-install
rehearsal scripts, check_starter_set, the four freeze-assert test files, and
current-state docs (README/.txt, USER-MANUAL/.txt, index.html, cc-1 harness,
starter-set-integration).

Deliberately KEEP at v1.2.0 (historical records — advancing them would
falsify history): ADR-0006, the cc-1 cleanroom evidence-pack README (records
a past run against v1.2.0), the [1.0.3] CHANGELOG entry, and the test that
asserts the ADR text. A new [Unreleased] CHANGELOG entry records this bump.

Verified locally: v1.2.1 wheel's civiccore alembic head is
civiccore_0003_local_task_queue; the 4 freeze-assert test files pass 31/31;
full suite parity with the pristine branch (643 pass, same 27 infra-only
fails needing postgres/docker/system-civiccore subprocesses).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
verify job: it installed the v1.2.1 freeze wheel but then force-reinstalled
civiccore from an older git commit (90ec5417, head 0002_llm) under a
"suite-session test override" — so the real-pgvector migration test saw
0002, not 0003. That override existed only to overlay the v1.2.0 freeze wheel
with newer civiccore code; the v1.2.1 freeze (aca61910) already contains that
commit, so the override is vestigial. Removed it — civiccore now resolves to
the v1.2.1 wheel (head civiccore_0003_local_task_queue) from the single pin.

browser-QA gate: docs/index.html is a hash-bound v1.0.4 release-evidence
snapshot (docs/browser-qa/release-evidence.json pins its sha256 to captured
desktop/mobile accessibility screenshots at reviewed_at 2026-06-13). My
freeze-advance edited a version string inside it, breaking the hash. Reverted
docs/index.html to the exact evidenced blob — the living current-state docs
(README/USER-MANUAL) already carry the v1.2.1 references, so no version-truth
is lost. verify-browser-qa.py passes locally.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@scottconverse
scottconverse merged commit f1cdaaa into main Jul 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant