docs: record owner-requested Gitea Actions disablement
This commit is contained in:
1 parent
d45aac17b5
commit
85294242b2
3 files changed
+17
-2
No files matched your search
@@ -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.
|
||||
|
||||
Reference in new issue
Block a user