411 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
admin	6b733f7b9c	Merge branch 'main' into feat/vehiq-oltp-watermark-extractor	2026-09-26 21:55:35 +00:00
admin	b89b1e81de	Merge pull request 'fix(ci): check out the siax-templates pin directly instead of comparing main' (#120) from fix/templates-pin-0pt-20260926 into main	2026-09-26 18:47:55 +00:00
Claude CodeandClaude Opus 5	65ee88a01c	fix(ci): check out the siax-templates pin directly instead of comparing main ... 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>	2026-09-26 20:07:29 +02:00
admin	ff7c5cdd66	Merge branch 'main' into feat/vehiq-oltp-watermark-extractor	2026-09-26 14:18:47 +00:00
admin	b982a1a643	Merge pull request 'fix(ci): bump SIAX_TEMPLATES_PINNED_SHA to reviewed siax-templates#138' (#119) from fix/g17-templates-pin-bump-138-20260926 into main	2026-09-26 12:56:13 +00:00
Claude Code	a2d6352e09	merge: bring in main to clear behind-base merge block	2026-09-26 14:51:49 +02:00
admin	125fc0ff66	Merge pull request 'fix(ci): re-pinna siax-templates 9a3a0aa → 09504e3a (granskad bump)' (#115) from fix/red-main-20260925-roda-mains into main	2026-09-26 12:45:09 +00:00
admin	65594902bd	Merge branch 'main' into fix/red-main-20260925-roda-mains	2026-09-26 12:07:11 +00:00
adminandClaude Sonnet 5	f4f660715b	fix(ci): bump SIAX_TEMPLATES_PINNED_SHA to reviewed siax-templates#138 (G17 evidence upload) ... 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>	2026-09-26 11:26:53 +00:00
admin	410339e697	feat(contract): add routing + normalization operationIds (ADR-027) (#118)	2026-09-26 11:19:43 +00:00
Claude CodeandClaude Sonnet 5	07158099ee	feat(ingestion): VehIQ OLTP -> ClickHouse watermark extractor (P070) ... 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>	2026-09-25 19:11:15 +02:00
siax-bot	189d51fb62	Merge branch 'main' into fix/red-main-20260925-roda-mains	2026-09-25 15:54:27 +00:00
admin	ec487746fd	Merge pull request 'fix(readiness): /api/ready svarade 200 med en död motor i produktion' (#116) from fix/readiness-fails-closed-on-broken-engine-20260925 into main	2026-09-25 12:42:43 +00:00
Claude	0062edbec3	fix(readiness): /api/ready svarade 200 med en död motor i produktion ... Mätt live 2026-09-25 mot produktionsdeployen (0pt.app / api.0pt.app, container shxd6lepxuxfsjsp0ath3z1g-172514162615 på server6, uppe 17,9 h, Docker-status "healthy" hela tiden): GET /api/health -> HTTP/1.1 200 OK {"ok":false,"service":"0pt-web","db":"ok","queue":"not_configured", "engine":"error","stripe":"not_configured", "detail":{"engine":"This operation was aborted"}} GET /api/ready -> HTTP/1.1 200 OK {"ready":true,"service":"0pt-web","db":"ok","engine":"error",...} ENGINE_URL pekade på http://0pt-engine:8000. Mätt inifrån containern: `getent hosts 0pt-engine` ger ingen post, och det finns ingen sådan container på någon av server5-11. Ett direktanrop mot motorn misslyckas efter ~5 s (DNS). Datamotorn — 0pt:s hela produkt — var alltså BORTA, och samtliga signaler ovanför den var gröna: Docker healthy, /api/health 200, /api/ready 200. `ok:false` i en 200-kropp är ingen signal. Ingenting i kedjan läser kroppar; allt läser statuskoder och exitkoder. isReady skilde tidigare bara på "db ok". Den skillnad som saknades är inte konfigurerad-vs-ej-konfigurerad utan FRÅNVARANDE-vs-TRASIG: * not_configured / not_integrated -> fortsatt ready. 0pt är byggt för att kunna köra utan motor, Stripe och kö (se .env.example). * error -> INTE ready. Statusen "error" betyder att någon medvetet konfigurerade beroendet och att en riktig round trip mot det just misslyckades. Det är inte längre en valfri integration. Ändrar ingenting i driften i dag: container-HEALTHCHECK pekar på /api/health (liveness) och Dockerfilen säger uttryckligen att en readiness-probe inte ska peka dit. Den här ändringen gör bara att den ärliga ytan faktiskt blir ärlig, så en yttre övervakning kan använda den. Regressionstest tillagt; verifierat att det FALLER mot den gamla isReady (1 failed | 18 passed) och passerar mot den nya (24 passed över health-checks/ready/health). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-25 13:34:42 +02:00
adminandClaude Opus 5	ccbf5878bd	fix(ci): re-pinna siax-templates 9a3a0aa -> 09504e3a (granskad bump) ... "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>	2026-09-25 13:33:20 +02:00
adminandClaude Opus 5	6f9034ff1d	chore: normalize sax3l -> admin CI references (#114) ... Konsolidering 2026-09-25 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: sax3l <simon@siax.io>	2026-09-25 03:29:44 +00:00
admin	480a0a658f	Merge pull request 'fix(ci): bump siax-templates G17-pin till 9a3a0aa (reviewed)' (#113) from fix/g17-templates-pin-bump-9a3a0aa into main	2026-09-24 17:21:58 +00:00
Claude Code	b3efe99ac0	fix(ci): bump siax-templates G17-pin till 9a3a0aa (reviewed) ... 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.)	2026-09-24 18:49:56 +02:00
admin	d29ec4a4b9	feat(des1gn): riktiga consumes härledda ur package.json (4 @siax-paket) ... Estate-derive v0: tomma baslinjer (våg 1) ersatta med FAKTISKA deklarerade @siax/*-beroenden — anpassa fritext-motiveringarna vid behov.	2026-09-24 17:53:59 +02:00
admin	fb69e2876f	Merge pull request 'chore(ci): bump SIAX_TEMPLATES_PINNED_SHA -> 5bda795 (granskad)' (#111) from chore/pin-5bda795 into main	2026-09-24 01:34:18 +00:00
Claude Code	ddc507d99e	chore(ci): bump SIAX_TEMPLATES_PINNED_SHA -> 5bda795 (granskad: renovate lockfiles + CI-natverksdetektion i tpl-workflows — samma monster som act0 ci.yml-fixen)	2026-09-24 03:23:41 +02:00
admin	ddaa62c526	feat(des1gn): repo-kontraktsbaslinjer (GENERATED, siax-standard RC-gaten v3) ... Fyller de fyra DES1GN-kontraktsfilerna (11 st) enligt estate-RC-gaten. Baslinjerna är KANONISKT GILTIGA neutrala former (tomma listor = ärlig baseline) — anpassa per repo eller sätt tidsbegränsad exemption. MEDVETET EJ MED: siax.repo.v3.json (29 required-fält är estates-fakta — genereras via estate-manifestflödet, aldrig stubbat). Merge sker av repoägaren. Bevis: siax-doctor repo-contract.	2026-09-24 00:26:56 +00:00
admin	4642784268	Merge pull request 'fix(decision): gate env OPT_DECISION_ER_SHADOW (Coolify avvisar sifferledande nycklar)' (#110) from fix/decision-gate-env-name into main	2026-09-23 21:19:52 +00:00
Claude Code	c47c4900fa	fix(decision): gate env OPT_DECISION_ER_SHADOW (Coolify avvisar sifferledande nycklar) ... 0PT_DECISION_ER_SHADOW borjar med siffra och avvisas av Coolifys env-validering (422, bevisat 2026-09-23) — gaten nadde aldrig prod-containern. Nytt namn: OPT_DECISION_ER_SHADOW (accepterad, satt i Coolify prod). Det gamla 0PT_- namnet accepteras fortfarande for backcompat.	2026-09-23 23:12:37 +02:00
Claude Code	1838082356	fix(FAS 61/DOD): deployment/environment-poster rensade till siax.deployment/siax.environment-schemanas exakta fält	2026-09-23 18:47:12 +02:00
Claude Code	418d9a9b4c	fix(FAS 61/DOD): deployment-poster i siax.deployment-schema-format (framework/build/start + runtimeState; production-doctorn matchar nu)	2026-09-23 18:41:36 +02:00
admin	e2aa3b9ab3	Merge pull request 'fix(ci): pin till full 40-teckens SHA' (#107) from chore/pin-sha-full-length into main	2026-09-23 16:25:57 +00:00
Claude Code	538d042bac	feat(FAS 61/DOD): siax/deployment + siax/environment — prod-deploy-evidens från Coolify (mätt 2026-09-23: app, server, commit, fqdn)	2026-09-23 18:25:31 +02:00
Claude Code	51dd242054	fix(ci): pin till full 40-teckens SHA (39-teckens variant kan aldrig mata HEAD-jamforelsen)	2026-09-23 18:23:57 +02:00
siax-estate-bot	f2d94db6d4	chore(runtime-evidence): sbom — estate-kampanj issue #76 (app 0pt)	2026-09-23 18:22:50 +02:00
siax-estate-bot	ed289a5390	chore(source-bundle+evidence): registrera FAKTISKT deployad commit f6a29da7e5 (app 0pt, deployed 2026-09-22T18:52:42Z) + deploy-log-evidens — estate-kampanj issue #76	2026-09-23 18:17:15 +02:00
admin	6563a81231	Merge pull request 'chore(ci): bump SIAX_TEMPLATES_PINNED_SHA -> cc81b295 (granskad)' (#106) from chore/bump-siax-templates-pin into main	2026-09-23 15:58:49 +00:00
Claude Code	4e780190a3	chore(ci): bump SIAX_TEMPLATES_PINNED_SHA 89816036 -> cc81b295 (granskad: docs-only ai-worker-pekare + renovate lockfiles)	2026-09-23 17:49:02 +02:00
admin	404e3c5a6a	Merge pull request 'feat(decision): Jev ER auto-match shadow (0PT_DECISION_ER_SHADOW)' (#105) from feat/decision-er-shadow into main	2026-09-23 15:06:40 +00:00
Claude Code	dc5c0eebf1	fix(doctor): point doctor + test at siax.repo.v3.json (legacy manifest raderades i 64e63cd) + operationalState running enligt live-evidens ... Pre-existing main-breakage: FAS 36-drift-konsolideringen (64e63cd) tog bort siax.repo.json men doctor och siax-doctor.test laest den fortfarande -> ENOENT i quality-jobbet. Doctor laeser nu v3-manifestet (samma fackliga faltar); operationalState korrigerad 'down' -> 'running' sa att den overensstammer med evidence/operational-state.json (live-proba 2026-09-22). Doctor 0/55 failures.	2026-09-23 17:01:08 +02:00
Claude Code	dd4731aa3c	feat(decision): Jev ER auto-match shadow (0PT_DECISION_ER_SHADOW) ... Shadow-eval av D0 auto-match: D0-tröskeln förblir auktoritet, kvaliteten mäts fire-and-forget mot siax-decision (:4600, decisionId 0pt.er.auto_match). Gate 0PT_DECISION_ER_SHADOW=1 (OFF by default). Fail-closed: gate-off/fel/ABSTAINED påverkar aldrig det deterministiska svaret; decision-planen loggar inbyggt (AUD0). - packages/decision: erAutoMatchShadow + erAutoMatchShadowEnabled - src/er/comparePair: void erAutoMatchShadow(...).catch(() => null) - tests/p0/decision-er-shadow.test.ts: gate-off/on, POST-body, DECIDED/ABSTAINED, fetch-fel, fire-and-forget-wire (16 nya tester)	2026-09-23 16:53:55 +02:00
Claude Code	63a837ff1e	feat(FAS 44/ADR-027): siax/discovery-policy.json — materialiserar manifestets discovery-block (profil/changeCapture/fail-closed/deletion+lineage; generatorn FAS 44)	2026-09-23 14:52:09 +02:00
admin	64e63cdcb4	fix(FAS 36-drift): DUBBELT v3-manifest konsoliderat — discovery/decision till siax.repo.v3.json, legacy raderad (samma som cl0ud PR#244-precedenten)	2026-09-23 03:55:30 +02:00
admin	8548ec3680	Merge pull request 'feat(FAS 36/ADR-027): siax.repo.json v3-migration + discovery/decision-block' (#102) from feat/fabric-onboarding into main	2026-09-23 01:29:58 +00:00
admin	f3658e2577	fix(FAS 36): ER-decision-importen via workspace-paketet @siax/0pt-decision (relativ path utanför root bröt Turbopack-builden — pre-existerande bugg från fc1a62b, exponerad av färsk pnpm-install i worktree)	2026-09-23 03:07:57 +02:00
admin	1c91bf8a7f	chore: retrigger CI (quality-jobb — lokal körning grön 1108/1108; CI-flake i Postgres-tjänsten misstänkt)	2026-09-23 02:00:01 +02:00
admin	bd84a752bd	feat(FAS 36/ADR-027): siax.repo.json v3-migration + discovery/decision-block (Universal Information & Discovery Fabric, siax-standard 764d526)	2026-09-23 01:32:53 +02:00
admin	3974f1c394	Merge pull request 'feat: decision-plane wiring — ER-pair decision.match tie-break (@siax/0pt-decision)' (#100) from feat/decision-plane into main	2026-09-22 22:29:42 +00:00
Claude Code	fc1a62bb81	feat: decision-plane wiring — ER-pair decision.match tie-break (@siax/0pt-decision) ... - packages/decision: erMatchDecision (0pt.er.pair_match mot siax-decision :4600) - comparePair async + borderline-band (±0.05 av review_threshold) → decision.match (D1 advisory) — deterministisk status GÄLLER om decision abstainar - OPT_DECISION_ER_ENABLED=1-gate (off tills kalibrering) - tests async-anpassade (await generateCandidates/rejects.toThrowError) - typecheck: 13 fel = pre-existing extraction-route (main-paritet), 0 nya fel - tester: 1108 passed | 184 skipped	2026-09-23 00:15:27 +02:00
admin	04e58c5d3c	Merge pull request 'feat(HSP-085): Migration Studio — ratio, session-resume, scoped coverage claim' (#99) from feat/hsp-085-migration-studio into main	2026-09-22 20:23:11 +00:00
admin	655a71ebd7	feat(HSP-085): migration-studio — T01 ej importerbart döljs EJ ur nämnaren (ratio = importable/total), T02 session-resume med tenant-check + checkpoint + resolved conflicts, T03 coverage-claim SCOPED (aldrig komplett M365-ersättning), 8 tester	2026-09-22 22:18:01 +02:00
admin	4320a47909	Merge pull request 'feat(HSP-084): cutover — dual writers, sena ändringar, rollback' (#98) from feat/hsp-084-cutover into main	2026-09-22 19:16:53 +00:00
admin	8f7a064177	fix(doctor-tests): GOV-06-tester uppdaterade till running-truth (0pt#96:s prod-truth-fix; down+402/404 var den föråldrade paret; ok:false-next-to-200 är nu negativa-fallet)	2026-09-22 21:11:33 +02:00
admin	85b0e6cd72	feat(HSP-084): cutover — T01 detectDualWriters (båda aktiva = STOPPAD), T02 handleLateSourceChanges (carry eller stopp, aldrig tyst förlorad), T03 buildRollbackPlan (targetWritesCarriedBack + käll-writer återaktiveras + konsistensverifiering), 8 tester	2026-09-22 21:00:19 +02:00
admin	f6a29da7e5	fix(deploy): corepack-retry-loop 8×15s i båda build-stegen (server6-EGONNRESET-flaken) + GOV-06 live-evidens 2026-09-22 (0pt.app=200)	2026-09-22 20:49:01 +02:00