94de4acef50f4bbc997ad44495414c56337ab16d
39
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
c9af814cbe |
chore(ci): koppla in SonarQube-analys mot självhostad sonar.siax.io
CI (SIAX Cloud) / integration (push) Skipped
CI (SIAX Cloud) / sonar (push) Skipped
masterplan-lock / check (push) Successful in 8s
Security Scan (SIAX Cloud) / security (push) Successful in 19s
CI (SIAX Cloud) / security (push) Successful in 21s
CI (SIAX Cloud) / quality (push) Successful in 42s
CI (SIAX Cloud) / sonar (pull_request) Skipped
masterplan-lock / check (pull_request) Successful in 6s
CI (SIAX Cloud) / security (pull_request) Successful in 20s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 20s
CI (SIAX Cloud) / integration (pull_request) Successful in 51s
CI (SIAX Cloud) / quality (pull_request) Successful in 58s
Lägger till en sonar-job i .gitea/workflows/ci.yml (körs endast vid push till main, Community Build saknar PR-analysläge) samt sonar-project.properties för repot 0pt. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
4c47e151f3 |
chore(ci): add missing timeout-minutes guards to hot-path jobs
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (push) Successful in 6s
masterplan-lock / check (pull_request) Successful in 6s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 24s
Security Scan (SIAX Cloud) / security (push) Successful in 49s
CI (SIAX Cloud) / security (push) Successful in 53s
CI (SIAX Cloud) / quality (push) Successful in 1m20s
CI (SIAX Cloud) / security (pull_request) Successful in 20s
CI (SIAX Cloud) / quality (pull_request) Successful in 53s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m0s
Fleet-wide CI-speed pass: none of 0pt's push/pull_request-triggered workflow jobs capped their own runtime, so a hang (network stall, runaway process, stuck polling loop) burns a runner slot until Gitea's own default kicks in. Added job-level timeout-minutes sized to what each job actually does: cd.yml deploy 20 (bounded ~10min signed-artifact poll + setup) ci.yml quality 30 (typecheck/test/build) ci.yml integration 45 (multi-service: live OpenSearch + ClickHouse) ci.yml security 15 (single trivy fs scan) security.yml security 15 (single trivy fs scan) masterplan-lock.yml check 10 (single dependency-free shell check) release.yml release 45 (docker build/push + full G17 SBOM/scan/attest/verify chain) Deliberately NOT included in this PR: a concurrency: block for ci.yml/security.yml/masterplan-lock.yml's push+pull_request double- trigger. ci.yml's own `integration` job comment already documents, measured live (runs 28904/28906), that "Gitea currently ignores workflow concurrency" on this fleet, and the repo's real fix for the resulting double-run-on-shared-service-containers problem is the self-identifying-container pattern already in that job, not a concurrency group. Adding an inert concurrency: block here would give false confidence that the duplicate-run problem is handled when it measurably is not. Left for a follow-up decision once that fleet-wide finding is resolved. Part of a fleet-wide CI-speed pass (timeout-minutes audit). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
e3930aa633 |
fix(a11y): ta bort alfa-tonad textfärg — 82 kontrastöverträdelser (UI-09)
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (push) Successful in 7s
Security Scan (SIAX Cloud) / security (push) Successful in 20s
CI (SIAX Cloud) / security (push) Successful in 47s
masterplan-lock / check (pull_request) Successful in 10s
CI (SIAX Cloud) / quality (push) Successful in 1m11s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 32s
CI (SIAX Cloud) / security (pull_request) Successful in 42s
CI (SIAX Cloud) / integration (pull_request) Successful in 56s
CI (SIAX Cloud) / quality (pull_request) Successful in 59s
axe-core 4.10.2 mot 0pt.app 2026-09-26: en enda regel, color-contrast, impact=serious, 82 noder. Estatets största enskilda a11y-defekt. Alla 82 har samma form: en Tailwind-alfamodifierare på en textfärg. Uppmätt WCAG 2.2-kontrast mot bägge temabakgrunderna i styles/globals.css: text-muted-foreground 4.73:1 ljust 7.63:1 mörkt GODKÄNT text-muted-foreground/70 2.71:1 4.20:1 faller text-muted-foreground/60 2.29:1 3.37:1 faller text-muted-foreground/50 1.96:1 2.67:1 faller text-muted-foreground/40 1.69:1 2.11:1 faller text-foreground/20 1.57:1 1.74:1 faller Den omodifierade token klarar AA i bägge teman, så åtgärden är helt enkelt att aldrig tona den. Elva textställen bytte till text-muted-foreground. Kopieringsknappen i app/portal går från 1.57:1 till 4.73:1 i viloläge och 19.79:1 vid hover — den föll även 1.4.11 för icke-textkomponenter. Toastens stängknapp klarade redan 1.4.11 (3.71:1) men blir 4.73:1. Kvar med alfa är endast den dekorativa masthead-siffran i app/bestall, som redan bär aria-hidden + select-none + pointer-events-none. Den är undantagen både av WCAG och av axe, och guarden nedan tillåter den på just den grunden. scripts/ci/check-text-contrast.mjs är en blockerande källkodsgrind i quality-jobbet. Den är avsiktligt inte en axe-körning: den fullständiga axe-jobb som UI-09 också begär kräver build + serve i CI och spåras separat. Tills det finns stoppar den här grinden regressionen vid den form som orsakade defekten. Refs: UI-09 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
6b733f7b9c |
Merge branch 'main' into feat/vehiq-oltp-watermark-extractor
masterplan-lock / check (pull_request) Successful in 5s
masterplan-lock / check (push) Successful in 7s
Security Scan (SIAX Cloud) / security (push) Successful in 26s
CI (SIAX Cloud) / security (pull_request) Successful in 42s
CI (SIAX Cloud) / quality (pull_request) Successful in 49s
CI (SIAX Cloud) / integration (pull_request) Successful in 51s
CI (SIAX Cloud) / integration (push) Skipped
CI (SIAX Cloud) / security (push) Successful in 19s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 21s
CI (SIAX Cloud) / quality (push) Successful in 51s
|
||
|
|
65ee88a01c |
fix(ci): check out the siax-templates pin directly instead of comparing main
CI (SIAX Cloud) / integration (push) Skipped
Security Scan (SIAX Cloud) / security (push) Successful in 16s
CI (SIAX Cloud) / security (push) Successful in 22s
masterplan-lock / check (push) Successful in 21s
masterplan-lock / check (pull_request) Successful in 7s
CI (SIAX Cloud) / security (pull_request) Successful in 19s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 1m2s
CI (SIAX Cloud) / quality (push) Successful in 1m56s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m16s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m15s
The G17 gate cloned sax3l/siax-templates on the moving branch `main` and then required that clone's HEAD to equal SIAX_TEMPLATES_PINNED_SHA. Every merge in siax-templates -- including ones that touch nothing under ci/v2/reference-hooks -- therefore turned this repo's release chain red while nothing was actually unsafe (CD-03 / CI-RED-02). It is red right now: siax-templates main is at 6612f6ae, the pin is 09504e3a. The pin is still a real supply-chain control; what was wrong was tying it to someone else's branch tip. The step now fetches the pinned commit by SHA (shallow, no branch consulted) and checks it out detached, falling back to fetching the branches and taking the same commit out of them if the server refuses a by-SHA fetch. It fails closed on the thing that actually matters -- the reviewed commit no longer existing upstream -- and the post-checkout HEAD assertion is kept so the gate still proves what it ran. SIAX_TEMPLATES_REF is removed rather than left unused, so the moving-branch shape cannot quietly come back. The pin value itself is unchanged: commit 09504e3a is confirmed present in siax-templates (Gitea API, two commits behind main). Two comments that described the old "refuses to run if main moved" behaviour are corrected in the same change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
ff7c5cdd66 |
Merge branch 'main' into feat/vehiq-oltp-watermark-extractor
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (push) Successful in 7s
masterplan-lock / check (pull_request) Successful in 8s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 50s
CI (SIAX Cloud) / security (push) Successful in 54s
CI (SIAX Cloud) / security (pull_request) Successful in 53s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m6s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m24s
CI (SIAX Cloud) / quality (push) Successful in 1m32s
Security Scan (SIAX Cloud) / security (push) Successful in 13s
|
||
|
|
a2d6352e09 |
merge: bring in main to clear behind-base merge block
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (pull_request) Successful in 8s
masterplan-lock / check (push) Successful in 8s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 20s
CI (SIAX Cloud) / security (push) Successful in 30s
Security Scan (SIAX Cloud) / security (push) Successful in 30s
CI (SIAX Cloud) / integration (pull_request) Successful in 33s
CI (SIAX Cloud) / security (pull_request) Successful in 39s
CI (SIAX Cloud) / quality (push) Successful in 55s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m2s
|
||
|
|
f4f660715b |
fix(ci): bump SIAX_TEMPLATES_PINNED_SHA to reviewed siax-templates#138 (G17 evidence upload)
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (push) Successful in 7s
masterplan-lock / check (pull_request) Successful in 10s
Security Scan (SIAX Cloud) / security (push) Successful in 21s
CI (SIAX Cloud) / security (push) Successful in 21s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 25s
CI (SIAX Cloud) / security (pull_request) Successful in 30s
CI (SIAX Cloud) / quality (push) Successful in 49s
CI (SIAX Cloud) / quality (pull_request) Successful in 54s
CI (SIAX Cloud) / integration (pull_request) Successful in 56s
siax-templates main advanced main..09504e3a5 (admin/siax-templates#138, merged, tested: 9 offline contract tests, G20 6/6, mutation harness 45/45, explicitly backward compatible / opt-in via G17_REQUIRE_ST0RE). The G17 release-chain gate in this repo was still pinned to the prior commit (9a3a0aa93c, 2026-09-24) and has been failing on every push to main since (refusing to run an unreviewed template version, by design) -- most recently blocking the release/deploy pipeline for #118. Reviewed the drift commit before bumping, per the gate own instructions ("re-review and update deliberately"). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
07158099ee |
feat(ingestion): VehIQ OLTP -> ClickHouse watermark extractor (P070)
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (push) Successful in 7s
CI (SIAX Cloud) / security (push) Successful in 17s
masterplan-lock / check (pull_request) Successful in 9s
Security Scan (SIAX Cloud) / security (push) Successful in 38s
CI (SIAX Cloud) / security (pull_request) Successful in 26s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 26s
CI (SIAX Cloud) / quality (push) Successful in 57s
CI (SIAX Cloud) / integration (pull_request) Successful in 39s
CI (SIAX Cloud) / quality (pull_request) Successful in 59s
Implements Simon's specified pattern (dealer_stock_entry/deal -> watermark/updated_at -> 0pt ingestion -> ClickHouse) as a P061 connector pair (PostgresWatermarkConnector, PostgresKeyedLookupConnector) plugged into the existing P062 IngestionRunner, writing to opt_dataset_projection via SiaxAnalyticsEngine.ingestProjection. Built here, not in admin/vehiq: that repo's own ADR-0035 (decisions 1/2/10, CI-enforced by validate_engine_firewall.py) forbids VehIQ code from ever holding a ClickHouse credential or hammering OLTP directly for analytics. See docs/P070_VEHIQ_OLTP_EXTRACTOR.md for the full rationale. Also corrects a real schema mismatch found while building this: production has no generic `updated_at` on any of the three target tables (verified live, read-only, 2026-09-25). dealer_stock_entry/deal use listed_at/ created_at as insert-time watermarks instead (documented caveat: in-place updates are not caught without a schema change); app.listing has no timestamp column at all and is deliberately not covered yet. Vehicle dimension lookup is narrow by construction: keyed on exactly the vehicle_id set referenced by the batch just read, never a scan of the 98M-row vehiq.vehicle table (connector-level validate() refuses that table by name; runner-level tests assert the query only ever touches referenced IDs). Verified: fixture-backed connector/runner tests (watermark+limit, same-timestamp tie at a page boundary, crash/resume, empty-table case, narrow-lookup query-count assertions) + a real disposable Postgres container (caught two real Date-handling bugs fixtures could not) + a read-only proof against actual production (server10, vehiq-db): the extractor's exact SQL returns zero rows, no error, confirming it is safe to schedule with zero current effect. .gitea/workflows/vehiq-oltp-ingest.yml is present, cron-scheduled, and defaults to VEHIQ_INGEST_MODE=preview (read-only, never writes) with no secrets configured — safe to merge with zero production effect until explicitly activated per the doc's "what activating this requires". Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
ccbf5878bd |
fix(ci): re-pinna siax-templates 9a3a0aa -> 09504e3a (granskad bump)
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (push) Successful in 3s
CI (SIAX Cloud) / security (push) Successful in 14s
Security Scan (SIAX Cloud) / security (push) Successful in 21s
CI (SIAX Cloud) / quality (push) Successful in 1m10s
masterplan-lock / check (pull_request) Successful in 26s
CI (SIAX Cloud) / security (pull_request) Successful in 38s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 38s
CI (SIAX Cloud) / integration (pull_request) Successful in 57s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m15s
"Release chain (G17, ADR-W16-003)" ar rod pa main med: siax-templates main moved (now 09504e3a..., pinned 9a3a0aa...) -- refusing to run an unreviewed version of the gate. Grinden gor precis vad den ska: den vagrar kora en ogranskad version. Det som saknades var granskningen. Deltaet 9a3a0aa..09504e3a ar EN merge — siax-templates #138 "Upload complete release evidence and validate artifact receipt" — och de enda berorda filerna under ci/v2 (det enda detta repo konsumerar) ar reference-hooks/{G17.sh, G17-ADR-W16-003.md, lib/emit-release-evidence.py, lib/test_emit_release_evidence.py}. Andringen ar bakatkompatibel by design: ST0RE-uppladdningen ar opt-in via G17_REQUIRE_ST0RE (default 0). 0pt ar en AUD0-only-konsument och kor darmed exakt samma vag som forut. Notera att grundproblemet ar strukturellt: SIAX_TEMPLATES_REF ar "main", sa varje commit i siax-templates rodfargar varje konsument samtidigt. Denna PR atgardar symptomet; en pinning mot en immutabel tagg hor hemma i en egen andring i siax-templates-konsumentkontraktet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|
|
b3efe99ac0 |
fix(ci): bump siax-templates G17-pin till 9a3a0aa (reviewed)
CI (SIAX Cloud) / integration (push) Skipped
Security Scan (SIAX Cloud) / security (pull_request) Successful in 13s
CI (SIAX Cloud) / security (pull_request) Successful in 25s
Security Scan (SIAX Cloud) / security (push) Successful in 25s
CI (SIAX Cloud) / quality (push) Successful in 39s
masterplan-lock / check (push) Successful in 45s
masterplan-lock / check (pull_request) Successful in 45s
CI (SIAX Cloud) / security (push) Successful in 46s
CI (SIAX Cloud) / quality (pull_request) Successful in 53s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m20s
G17 'Release chain' faller på 6 s: pinned SHA 5bda7950 matchar ej längre siax-templates main (9a3a0aa) — #137 'internal pinned action mirrors' flyttade referensen. Re-review: diff 5bda7950..main rör EJ ci/ (reference-hooks G17.sh/lib byte-identiska) — endast cognition-scaffolds + action-mirrors. Pin-bump är därför mekaniskt säker för gate-koden. (act0 har redan 9a3a0aa.) |
||
|
|
ddc507d99e |
chore(ci): bump SIAX_TEMPLATES_PINNED_SHA -> 5bda795 (granskad: renovate lockfiles + CI-natverksdetektion i tpl-workflows — samma monster som act0 ci.yml-fixen)
CI (SIAX Cloud) / integration (push) Has been skipped
Security Scan (SIAX Cloud) / security (push) Successful in 18s
masterplan-lock / check (push) Successful in 33s
CI (SIAX Cloud) / quality (push) Successful in 43s
CI (SIAX Cloud) / security (push) Successful in 1m13s
masterplan-lock / check (pull_request) Successful in 15s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 26s
CI (SIAX Cloud) / security (pull_request) Successful in 27s
CI (SIAX Cloud) / quality (pull_request) Successful in 47s
CI (SIAX Cloud) / integration (pull_request) Successful in 57s
|
||
|
|
51dd242054 |
fix(ci): pin till full 40-teckens SHA (39-teckens variant kan aldrig mata HEAD-jamforelsen)
CI (SIAX Cloud) / integration (push) Has been skipped
CI (SIAX Cloud) / security (push) Successful in 32s
Security Scan (SIAX Cloud) / security (push) Successful in 43s
masterplan-lock / check (pull_request) Successful in 50s
CI (SIAX Cloud) / quality (push) Successful in 1m8s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 1m8s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m55s
CI (SIAX Cloud) / security (pull_request) Successful in 24s
CI (SIAX Cloud) / quality (pull_request) Successful in 54s
masterplan-lock / check (push) Successful in 10s
|
||
|
|
4e780190a3 |
chore(ci): bump SIAX_TEMPLATES_PINNED_SHA 89816036 -> cc81b295 (granskad: docs-only ai-worker-pekare + renovate lockfiles)
CI (SIAX Cloud) / integration (push) Has been skipped
masterplan-lock / check (push) Successful in 19s
Security Scan (SIAX Cloud) / security (push) Successful in 22s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 18s
masterplan-lock / check (pull_request) Successful in 23s
CI (SIAX Cloud) / security (pull_request) Successful in 39s
CI (SIAX Cloud) / quality (pull_request) Successful in 44s
CI (SIAX Cloud) / quality (push) Successful in 1m3s
CI (SIAX Cloud) / security (push) Successful in 1m7s
CI (SIAX Cloud) / integration (pull_request) Successful in 56s
|
||
|
|
1d5233cee0 |
fix(cd): attestation not-ready regex — cosign 3.x says 'no matching attestations:' (no 'found')
CI (SIAX Cloud) / integration (push) Has been skipped
masterplan-lock / check (pull_request) Successful in 5s
masterplan-lock / check (push) Successful in 9s
CI (SIAX Cloud) / security (pull_request) Successful in 15s
CI (SIAX Cloud) / security (push) Successful in 20s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 23s
CI (SIAX Cloud) / integration (pull_request) Successful in 27s
Security Scan (SIAX Cloud) / security (push) Successful in 33s
CI (SIAX Cloud) / quality (pull_request) Successful in 40s
CI (SIAX Cloud) / quality (push) Successful in 51s
Measured live 2026-09-22: release.yml's G17 attest finished 03:37:18, but cd.yml's poll loop hit the digest at 03:37:02 (image pushed before the attestation upload completed) and cosign 3.1.3 failed with 'Error: no matching attestations: ' — the gate's retry regex required the trailing 'found', so a transient not-ready state was misread as a hard verify failure. Broaden the regex to accept both message forms; the fail-closed behaviour for REAL attest failures is unchanged. |
||
|
|
ab0f5a0c5a |
chore(release): re-pin siax-templates G17 hook pin 7725498 -> a401880
CI (SIAX Cloud) / integration (push) Has been skipped
masterplan-lock / check (push) Successful in 7s
masterplan-lock / check (pull_request) Successful in 4s
Security Scan (SIAX Cloud) / security (push) Successful in 16s
CI (SIAX Cloud) / security (pull_request) Successful in 12s
CI (SIAX Cloud) / quality (push) Successful in 35s
CI (SIAX Cloud) / quality (pull_request) Successful in 35s
CI (SIAX Cloud) / integration (pull_request) Successful in 36s
CI (SIAX Cloud) / security (push) Successful in 1m48s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 1m43s
Templates main moved 12 commits (PAY-35 module, ui-consumer lockfile, recovery wave, X-708 profiles, deps). Verified: diff between pins contains ZERO changes under ci/v2/reference-hooks/ (the G17 contract implementation), so the bump is behaviour-neutral for the gate. release.yml SIAX_TEMPLATES_PINNED_SHA and .siax/hook-pins.json templateRef bumped together per the pin file's own reSyncInstructions. |
||
|
|
1ed035327d |
chore(release): pin siax-templates to 7725498 (deliberate re-review)
CI (SIAX Cloud) / integration (push) Has been skipped
masterplan-lock / check (pull_request) Successful in 4s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 15s
Security Scan (SIAX Cloud) / security (push) Successful in 18s
CI (SIAX Cloud) / security (pull_request) Successful in 18s
CI (SIAX Cloud) / security (push) Successful in 21s
CI (SIAX Cloud) / quality (pull_request) Successful in 38s
CI (SIAX Cloud) / quality (push) Successful in 38s
masterplan-lock / check (push) Successful in 41s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m16s
Gate files (lib/pinned-tools.sh, G17.sh) unchanged between 384e350 and 7725498 — diff is template/dep updates only (web-app, worker deps, otel bootstrap, HSP docs). Verified before bumping the pin. |
||
|
|
2e75b54717 |
Merge pull request #65
masterplan-lock / check (push) Successful in 5s
CI (SIAX Cloud) / security (push) Successful in 17s
Security Scan (SIAX Cloud) / security (push) Successful in 29s
CI (SIAX Cloud) / quality (push) Successful in 34s
CI (SIAX Cloud) / integration (push) Successful in 56s
Deploy to Coolify / deploy (push) Failing after 9m57s
Release chain (G17, ADR-W16-003) / Build, push, G17 (SBOM/scan/attest/verify/evidence) (push) Failing after 5s
|
||
|
|
f976f36530 |
fix(ci): avoid duplicate live integration jobs on branch push
CI (SIAX Cloud) / integration (push) Has been skipped
masterplan-lock / check (push) Successful in 4s
CI (SIAX Cloud) / security (pull_request) Successful in 14s
Security Scan (SIAX Cloud) / security (push) Successful in 16s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 16s
CI (SIAX Cloud) / integration (pull_request) Successful in 27s
CI (SIAX Cloud) / quality (pull_request) Successful in 37s
masterplan-lock / check (pull_request) Successful in 46s
CI (SIAX Cloud) / security (push) Successful in 48s
CI (SIAX Cloud) / quality (push) Successful in 1m16s
|
||
|
|
a3df134caf |
feat(ci): migrate signed-deploy gate to siax-templates G17 reference (ADR-W16-003)
masterplan-lock / check (push) Successful in 3s
Security Scan (SIAX Cloud) / security (push) Successful in 16s
CI (SIAX Cloud) / integration (push) Successful in 28s
CI (SIAX Cloud) / quality (push) Successful in 35s
masterplan-lock / check (pull_request) Successful in 5s
CI (SIAX Cloud) / security (pull_request) Successful in 13s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 14s
CI (SIAX Cloud) / integration (pull_request) Successful in 28s
CI (SIAX Cloud) / security (push) Successful in 1m24s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m9s
0pt's own "P007 pattern" release chain (added 2026-09-14) genuinely failed the ADR-W16-003 promotion bar an audit (2026-09-15) checked it against: syft/cosign installed via curl + a freshly-refetched checksums file (not a pinned, out-of-band-verified digest), no vulnerability scan of the built digest at all, cosign signed only the bare digest (no in-toto/SLSA statement, no source-SHA/build-identity/environment/SBOM-hash binding, no scoped key identity), and evidence committed straight back into this same mutable repo (siax/production-evidence/*.json, siax/source-bundles/*.json -- nine such commits already existed in this repo's history, deleted in this change). Delegates every bar item (1-7: pinned-tool install, SBOM, blocking vuln scan, in-toto attestation, scoped-key signing, pubkey verification, AUD0/ST0RE evidence storage) to sax3l/siax-templates' real, reviewed G17 reference implementation (PR #51, merged, pinned at 384e35060b91ea78ec045e14af114abf5d5eb23b), checked out at CI runtime via the SIAX_CI_TOKEN org secret this repo already had wired for a different cross-repo write -- picked over a vendored copy (the mechanism st0re/cl0ud/ api0 used) because 0pt has no prior vendoring convention anywhere in this repo. Matches aud0/h0st's own migrations for the same reason. See .siax/hooks/README.md for the full composition-mechanism rationale. .siax/hooks/G17.sh is the adapter: owns only 0pt-specific values (image repo, key identity, and a license-allowlist policy measured against 0pt's own real SBOM -- 280 components, one genuine new finding this pass caught that the old gate never checked at all: gcompat's NCSA license, triaged and allowed as the real OS-substrate license it is). cd.yml's own real signed-artifact wait/verify gate (predates this migration, genuinely 0pt-specific -- polls the registry for release.yml's artifact, verifies before triggering Coolify) is KEPT, updated from `cosign verify` (bare digest) to `cosign verify-attestation --type ...` to match the new attestation format `cosign attest` produces. A fresh cosign keypair was generated for this migration -- the previously committed cosign.pub had no corresponding private-key secret ever provisioned on this repo (the old release.yml's own comment confirms: "NOT YET SET on sax3l/0pt as of this writing"), so there was no real existing key material to carry forward. G20 (live-digest-equality) deliberately NOT wired in this pass: 0pt has no Coolify application provisioned and no /version endpoint for it to poll against -- see .siax/hooks/README.md "G20 -- deliberately not wired yet" for what would need to exist first. Verified for real during this migration (see PR description for the full evidence): a real image built from this repo's own Dockerfile, pushed to a local registry, SBOM'd (syft), scanned (trivy, 0 CRITICAL/HIGH findings), DSSE-attested (cosign attest) and verified (cosign verify-attestation) against the new cosign.pub, submitted to a mock AUD0 server enforcing the real eventInputSchema contract, plus three real tamper-rejection negative controls (wrong key, wrong predicate type, never-attested digest) against this exact artifact, plus the reference implementation's own 29/29-assertion selftest (including a real live check against production api.aud0.siax.io). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
5669a0e9e7 |
fix(cd): gate får retry på 'no signatures found' — 8-sekunders-racet mellan release.yml:s push och cosign-sign mät live 2026-09-15 (pull 02:36:45, verify-fail 02:37:03, sign fast 02:37:11); hård fail kvar för äkta verify-fel
masterplan-lock / check (push) Successful in 5s
Security Scan (SIAX Cloud) / security (push) Successful in 14s
CI (SIAX Cloud) / security (push) Successful in 15s
CI (SIAX Cloud) / integration (push) Successful in 25s
CI (SIAX Cloud) / quality (push) Successful in 34s
masterplan-lock / check (pull_request) Successful in 7s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 15s
CI (SIAX Cloud) / security (pull_request) Successful in 24s
CI (SIAX Cloud) / integration (pull_request) Successful in 25s
CI (SIAX Cloud) / quality (pull_request) Successful in 35s
|
||
|
|
5a0429d46b |
fix(ci): add SBOM+sign release chain and gate Coolify redeploy on it
masterplan-lock / check (push) Successful in 4s
CI (SIAX Cloud) / security (push) Successful in 13s
CI (SIAX Cloud) / quality (push) Successful in 32s
Security Scan (SIAX Cloud) / security (push) Successful in 52s
CI (SIAX Cloud) / integration (push) Successful in 1m35s
0pt had no SBOM/sign/digest chain at all (re-confirmed live before this change: no cosign/syft/sbom hit anywhere under .gitea/workflows/, only doc mentions in CHANGELOG.md/docs/architecture/ARCHITECTURE.md). Applies the same two-part pattern already proven on sax3l/cl0ud and sax3l/st0re (fix/wire-signed-digest-to-deploy, 2026-09-14): 1. .gitea/workflows/release.yml (new): builds the image, pushes it to git.cloud.siax.io/sax3l/0pt:sha-<12>, SBOMs it (syft), signs it (cosign, key-based), verifies the signature in the same run, and commits source-bundle/production-evidence records back to the repo. 2. .gitea/workflows/cd.yml: the `deploy` job now polls the registry for this exact commit's release-chain image and cosign-verifies it (against the committed cosign.pub) before calling Coolify's deploy endpoint -- fails closed (10 min timeout) if release.yml never produced a verifiable artifact for this sha. Added AFTER the existing guard step, which still fails closed first on 0pt's real, pre-existing blocker: no Coolify Application is provisioned for 0pt yet (COOLIFY_APP_ID is a literal placeholder). This gate is wired ahead of that so it's already in place the day the app is provisioned, instead of a second follow-up change. Honest limitation carried over from cl0ud/st0re/h0st: once provisioned, 0pt's Coolify Application is expected to use the `dockerfile` build pack (per siax.config.json), so Coolify would still perform its own independent docker build rather than pulling the signed image, and /api/v1/deploy has no digest parameter to pin against -- true digest-pinning needs a production Coolify resource-type decision, out of CI-YAML scope. This gate proves a signed, verified build of the exact commit exists before authorizing any deploy call; it does not prove byte-identical output from Coolify's own rebuild. cosign.pub is a fresh, 0pt-specific keypair generated offline for this change. NOT YET SET on sax3l/0pt (release.yml/cd.yml's gate will fail closed until present): REGISTRY_USER, REGISTRY_TOKEN, COSIGN_PRIVATE_KEY, COSIGN_PASSWORD, SIAX_CI_TOKEN repo secrets. Validated without live Coolify/registry access: YAML-parsed all 2 files, bash -n syntax-checked all 19 embedded run: blocks, and dry-ran the actual verification logic -- the RepoDigests filter and bounded poll-retry loop against mocked scenarios, plus a real cosign sign+verify round-trip (offline signing-config, local throwaway registry container) proving the gate's cosign verify command genuinely passes on the correct key/digest and fails closed on a wrong key and on an unsigned image. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
bb4cc78145 |
chore(conformance): add masterplan-lock guard + PLAN/MASTERPLAN_INDEX.md
masterplan-lock / check (pull_request) Successful in 5s
masterplan-lock / check (push) Successful in 6s
CI (SIAX Cloud) / security (pull_request) Successful in 13s
CI (SIAX Cloud) / security (push) Successful in 17s
Security Scan (SIAX Cloud) / security (push) Successful in 13s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 13s
CI (SIAX Cloud) / quality (push) Successful in 35s
CI (SIAX Cloud) / integration (push) Successful in 41s
CI (SIAX Cloud) / quality (pull_request) Successful in 46s
CI (SIAX Cloud) / integration (pull_request) Successful in 48s
Per siax-standard conformance sweep: repo lacked the masterplan-lock CI guard (.gitea/workflows/masterplan-lock.yml + scripts/check-masterplan-lock.sh) and a repo-local PLAN/MASTERPLAN_INDEX.md. Copied from sax3l/st0re template (generic POSIX sh check), stub PLAN index with locked architecture principles and pointer to sax3l/siax-masterplan. Refs: sax3l/siax-standard (conformance sweep 2026-09-10) |
||
|
|
6b1723dbd0 |
Merge pull request 'chore(deps): update clickhouse/clickhouse-server docker tag to v24.12' (#27) from renovate/clickhouse-clickhouse-server-24.x into main
Deploy to Coolify / deploy (push) Failing after 2s
Security Scan (SIAX Cloud) / security (push) Successful in 13s
CI (SIAX Cloud) / security (push) Successful in 14s
CI (SIAX Cloud) / quality (push) Successful in 33s
CI (SIAX Cloud) / integration (push) Successful in 44s
|
||
|
|
be5e598646 |
fix(ci): replace the integration anti-skip guard that could not pass
CI (SIAX Cloud) / security (push) Successful in 15s
Security Scan (SIAX Cloud) / security (push) Successful in 18s
CI (SIAX Cloud) / integration (push) Successful in 29s
CI (SIAX Cloud) / quality (push) Successful in 47s
CI (SIAX Cloud) / security (pull_request) Successful in 15s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 15s
CI (SIAX Cloud) / integration (pull_request) Successful in 31s
CI (SIAX Cloud) / quality (pull_request) Successful in 38s
The guard grepped vitest's HUMAN output:
grep -qE "skipped" && ! grep -qE "Tests [0-9]+ passed"
vitest colours that summary. The real line emitted on these runners is
ESC[2m Tests ESC[22m ESC[1mESC[32m97 passedESC[39m | ...
so ANSI escapes sit between "Tests " and the digits and the
two-spaces-then-digits pattern can never match. The first grep still
matched "skipped", so the condition was true whenever a single test
skipped -- no matter how many passed.
Measured on run 13911 job 31183 (this branch, 2026-09-08): 13 files /
97 tests PASSED, 1 file / 2 tests skipped, and the step still printed
"FATAL: integration suites skipped instead of running" and exited 1.
That message was false; the suites ran.
It survived review because it is correct locally -- redirecting vitest
to a file disables its colour, so the pattern matches on a developer
machine and misfires only under CI.
Replaced with vitest's JSON reporter: structured, colourless, and
fail-closed if the report is missing. A/B measured on real reports in
BOTH directions, so the replacement is not merely green:
all skipped (0 passed / 99 pending) -> exit 1 (protection kept)
945 passed + 184 skipped -> exit 0 (false red gone)
report file absent -> exit 1 (fail closed)
The anti-skip guarantee the original guard was written for is preserved:
a run where every suite skips still fails.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|
|
1322d26fac |
fix(ci): make the required security gate capable of failing
Branch protection on `main` requires exactly two status contexts:
CI (SIAX Cloud) / security (push)
CI (SIAX Cloud) / quality (push)
The `security` half could not fail. All three Trivy invocations in this
repo ran with `--exit-code 0`, so the scanner reported findings to stdout
and then exited 0 regardless.
Measured on main @4514d97, 2026-09-08, same scanner (Trivy 0.73.0), same
target, only the flag differing:
A --exit-code 0, clean tree -> exit 0
B --exit-code 0, planted AWS secret access key -> exit 0 (DETECTED
as CRITICAL in the report, gate still green)
C --exit-code 1, same planted secret -> exit 1
D --exit-code 1, probe removed -> exit 0
B is the defect: the required context reported success while the scanner
had a CRITICAL secret in hand. D is why this is safe to land now -- the
tree is clean today, so flipping the flag does not open the gate red.
(PR #19 measured 19 HIGH findings on 2026-08-11; those dependencies have
since been updated on main, 142 commits later.)
The other required context, `quality`, was verified real and left alone:
a planted type error fails `pnpm run typecheck` (exit 2) and a planted
failing assertion fails `pnpm run test` (exit 1, 945 passed baseline).
nightly.yml carried the same flag. A nightly scan exists to catch CVEs
published against code that did not change; with `--exit-code 0` it could
never raise that alarm.
Not fixed here, needs an owner decision: services/scrapers/requirements.txt
uses `>=` ranges only. Trivy's pip scanner cannot resolve unpinned
specifiers, so it omits the file from the scan entirely -- it never appears
as a target. Pinning those same floors with `==` surfaces 3 HIGH findings
(aiohttp CVE-2025-69223, aiohttp CVE-2026-69244, lxml CVE-2026-41066).
Deliberately NOT suppressed with `--skip-dirs`, which would turn a
measurable blind spot into declared policy.
Job names are unchanged, so both required context strings are preserved.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|
|
15ebce07ed |
chore(deps): update clickhouse/clickhouse-server docker tag to v24.12
CI (SIAX Cloud) / quality (push) Successful in 47s
Security Scan (SIAX Cloud) / security (push) Successful in 34s
CI (SIAX Cloud) / security (push) Successful in 35s
CI (SIAX Cloud) / integration (push) Successful in 46s
CI (SIAX Cloud) / security (pull_request) Successful in 24s
CI (SIAX Cloud) / integration (pull_request) Successful in 27s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 21s
CI (SIAX Cloud) / quality (pull_request) Successful in 48s
|
||
|
|
f8bb0d5ab9 |
Merge pull request 'feat: SIAX Platforms P0 wave 2 — real-contract platform clients + Data-OS capability layer' (#25) from feat/siax-platforms-p0-data-os into main
Deploy to Coolify / deploy (push) Successful in 3s
CI (SIAX Cloud) / integration (push) Successful in 25s
CI (SIAX Cloud) / security (push) Successful in 18s
CI (SIAX Cloud) / quality (push) Successful in 48s
Security Scan (SIAX Cloud) / security (push) Successful in 19s
|
||
|
|
62f7b0049f |
fix(ci): pin OpenSearch service container workdir — act_runner clobbers WORKDIR-relative ENTRYPOINT
CI (SIAX Cloud) / integration (push) Successful in 22s
CI (SIAX Cloud) / security (push) Successful in 20s
Security Scan (SIAX Cloud) / security (push) Successful in 17s
CI (SIAX Cloud) / quality (push) Successful in 47s
CI (SIAX Cloud) / security (pull_request) Successful in 20s
CI (SIAX Cloud) / integration (pull_request) Successful in 31s
CI (SIAX Cloud) / quality (pull_request) Successful in 45s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 22s
PR #25 CI run 7745 job 'integration' failed before any test ran: 'exec: "./opensearch-docker-entrypoint.sh": stat ...: no such file or directory'. Root cause (confirmed against the job log's merged container.Config, and reproduced locally with plain docker run -w): this runner's act_runner merges the JOB's WorkingDir (/workspace/sax3l/0pt) into every SERVICE container, clobbering the OpenSearch image's own WORKDIR (/usr/share/opensearch) that its ENTRYPOINT ./opensearch-docker-entrypoint.sh is relative to. ClickHouse's entrypoint is an absolute path so it started fine under the same defect -- a green ClickHouse service is not evidence this class of bug is absent elsewhere. Fix: --workdir /usr/share/opensearch in the opt-ci-opensearch service's options, restoring the image's own working directory. Verified locally: 'docker run -w /workspace/sax3l/0pt opensearchproject/opensearch:2.11.1' reproduces the exact failure; '-w /usr/share/opensearch' fixes it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|
|
c47e3b468e |
test(integration)+ci+docs: live OpenSearch/ClickHouse suites, CI service containers, STATUS.md (§56)
CI (SIAX Cloud) / integration (push) Failing after 22s
CI (SIAX Cloud) / security (push) Successful in 22s
Security Scan (SIAX Cloud) / security (push) Successful in 21s
CI (SIAX Cloud) / quality (push) Successful in 43s
CI (SIAX Cloud) / integration (pull_request) Failing after 3s
CI (SIAX Cloud) / security (pull_request) Successful in 17s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 16s
CI (SIAX Cloud) / quality (pull_request) Successful in 43s
- tests/integration/: 10 tests against REAL OpenSearch 2.11 (tenant isolation, purpose/rights filters, generation rebuild/rollback, projection-disaster rebuild §68) + REAL ClickHouse 24.8 (tenant-isolated metric DSL, TTL schema, injection-surface refusals). Honest skip without env - and CI fails hard if the suites skip instead of running. - .gitea/workflows/ci.yml: new blocking 'integration' job with self-identifying service containers (st0re ci.yml's measured alias-collision discipline: run-unique cluster.name / credentials, getent-enumerated IP selection, no-match = hard fail). - STATUS.md: full 8-level Master-DoD classification per capability incl. the honest gaps blocking PRODUCTION_READY. - dependency-mode: NEXT_PHASE=phase-production-build is not a serving runtime (next build page-data collection must compile; guard re-arms at boot) - pinned by contract test. - docs/02-architecture.md: superseded the accurate-but-now-fixed 'every client runs against its mock' paragraph; .env.example: client URLs now actually read from env + new P0 backend vars. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|
|
18ea0ecc41 |
fix: wire COOLIFY_APP_ID from repo variable (0pt app provisioned via API 2026-08-31)
CI (SIAX Cloud) / security (push) Successful in 46s
CI (SIAX Cloud) / security (pull_request) Successful in 49s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 48s
Security Scan (SIAX Cloud) / security (push) Successful in 21s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m15s
CI (SIAX Cloud) / quality (push) Successful in 1m13s
|
||
|
|
2393f52768 |
docs(compliance): finish attributing the evasion-stack keep decision
CI (SIAX Cloud) / security (push) Successful in 20s
Security Scan (SIAX Cloud) / security (push) Successful in 20s
CI (SIAX Cloud) / quality (push) Successful in 41s
CI (SIAX Cloud) / security (pull_request) Successful in 20s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 20s
CI (SIAX Cloud) / quality (pull_request) Successful in 41s
PR #15 already fixed AGENTS.md/SECURITY.md with a dated, attributed statement of the account owner's 2026-08-11 decision (Simon Axelsson, via an interactive decision prompt, responding to this repo's own removal proposal PR #7 which was verified clean/128 tests and closed unmerged -- no rationale beyond "keep it" was given or is invented). This PR finds and fixes every other place in the repo that still carried the earlier unattributed "medvetet anvandarbeslut" / "deliberate user decision" claim a compliance audit flagged as unverifiable: - docs/compliance/GOLDEN-STANDARD-REPORT.md: control C6 row + the "Bypass-undantag" formal section (the two places this doc was explicitly named to need checking) -- header gains a dated update note, C6 row and the section body get the same attributed statement as AGENTS.md/SECURITY.md. - docs/compliance/SLUTRAPPORT.md, docs/compliance/INVENTORY.md: historical session doc keeps its original text and gains a dated correction addendum; the INVENTORY.md evidence bullet is corrected in place. - docs/slo.md, CONTRIBUTING.md, prompts/002-compliance-audit.md, renovate.json, .gitea/workflows/security.yml: direct/living references to the exemption get the same attributed, dated pointer instead of the unattributed phrase. CLAUDE.md's general §1 anti-evasion policy text is untouched, per instruction -- this is a scoped exception note, not a change to the normative rule. No code changes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
6612ab1233 |
ci: keep advisory security job in ci.yml so protected-branch status contexts stay reported
CI (SIAX Cloud) / security (push) Successful in 21s
Security Scan (SIAX Cloud) / security (push) Successful in 22s
CI (SIAX Cloud) / security (pull_request) Successful in 18s
CI (SIAX Cloud) / quality (push) Successful in 40s
CI (SIAX Cloud) / quality (pull_request) Successful in 39s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 16s
|
||
|
|
48d31d0081 | ci(workflows): split CD/security/nightly under .gitea/workflows + gitignore hygiene (protected-path PR) | ||
|
|
ad042d825f |
fix(deploy): declare Coolify as the deploy target, not Vercel
siax.config.json declared deploy.target: "vercel", which conflicts with the SIAX Cloud platform pattern every sibling OS repo (n0d, st0re, aud0) follows: a Dockerfile "for Coolify" (already present in this repo) plus a .gitea/workflows/deploy.yml that POSTs a restart to a Coolify app UUID. Investigated before changing anything: - 0pt.app is confirmed live on Vercel (Server: Vercel, 200 OK) but its own /api/health reports db/queue "not_configured", and POSTing to /api/orders creates an order that is not durably persisted (in-memory store only, per this repo's own docs/08-infrastructure.md and docs/architecture/ ARCHITECTURE.md, both independently verified live 2026-07-19 / 2026-08-07, and reconfirmed live again today). It's a fully-built marketing/demo surface with no real backend behind it -- not a live product serving real customer data. Safe to change deploy config without a cutover plan. - Dockerfile already exists and is already written "for Coolify" (node:24- alpine multistage, non-root, /api/health healthcheck) -- no changes needed there. - No .gitea/workflows/deploy.yml existed. Added one following the exact pattern used by n0d and st0re (POST /api/v1/deploy?uuid=...&force=false with COOLIFY_TOKEN). No Coolify app has been provisioned for 0pt yet, so the app UUID is a literal placeholder and the workflow fails loudly by design until a real app + token are in place -- this does not silently ship a broken deploy config. This changes only this repo's declared *intent*. It does NOT touch the live Vercel deployment, delete the Vercel project, or move any traffic -- that cutover (provision Coolify app -> verify -> DNS -> decommission Vercel) is a separate, larger decision. README and ARCHITECTURE.md updated to state this plainly rather than let them contradict the new config. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
5166d85ecd | chore: add missing standard files (LICENSE/CLAUDE/health-check) | ||
|
|
1d76d50f3d |
feat(auth,foundation): Wave 2 flag-gated Zitadel JWT verify + validation + eslint + tests
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|
|
bd5e309851 | chore(foundation): Wave 1 scaffolding — CI gate / Dockerfile / .env.example | ||
|
|
afd301facb |
feat: production scraper engine v2 for DK/NO/DE data
Scraper CI / lint (push) Successful in 5s
|