docs: record owner-requested Gitea Actions disablement

This commit is contained in:
karl committed 2026-10-12 21:27:00 +02:00
1 parent d45aac17b5
commit 85294242b2
3 files changed
+17 -2

No files matched your search

+3
View File
@@ -27,6 +27,9 @@ readiness without completed release gates and recorded evidence.
download/verify missing Google assets, reuse cached assets, and expose progress/retry in the UI.
- Add meaningful tests for retrieval, persistence, and filesystem lifecycle changes.
- Keep docs/ROADMAP.md current. Unexecuted platform checks remain unchecked.
- Gitea Actions are disabled for this repository at Karl's explicit request
(2026-10-12, repeated failure emails). Do not re-enable without his request.
Keep running appropriate local checks and recording actual platform evidence.
- Agents own assigned paths and must coordinate shared interface changes. Do not commit other agents' unfinished work.
- Prepare indexes and the real Google query session in the background. Retain
warmed readers and keep keyword search usable during setup. Measure startup,
+4 -2
View File
@@ -108,8 +108,10 @@ signing/notarization requires Apple tooling and credentials. See the
## CI and packaging gates
GitHub and Gitea workflows define native OS matrices. Gitea requires registered
runners matching its configured labels. A workflow declaration does not prove
Gitea Actions are disabled for this repository at the owner's request after
repeated failure emails (2026-10-12). Existing workflows remain as references:
GitHub defines native OS matrices; Gitea targets its available Ubuntu runner.
A workflow declaration does not prove
a platform was tested; Linux/macOS gates remain open until actual job evidence
exists. Current workflow checks do not certify the separately built Google
worker or execute downloaded-model tests automatically.
+10
View File
@@ -7,6 +7,16 @@ and `SEARCHI_FORCE_CPU=1`.
## Current integration checkpoint (2026-10-12)
Gitea Actions were disabled for **karl/searchi** at Karl's explicit request;
the API read-back confirmed `has_actions:false`. Fifteen old stuck runs and
the subsequent repair run were cancelled. Diagnosis found unavailable native
Windows/macOS runner labels and a document-pagination test assuming filesystem
traversal order. The test was corrected and its four local document tests plus
strict core Clippy passed. The Linux-only workflow repair was pushed, but its
verification run was cancelled when Karl requested disabling CI. It must not
be reported as a passing remote run. Local checks and remaining release gates
continue to apply; enabling Actions again requires Karl's explicit request.
- Native desktop: **15/15 tests passed**, including structured trace/basic responses
and four optional-answer source/consent/revision tests.
Post-generation cached query warmup is implemented but its interactive first-query gate remains open.