5 commits

Author	SHA1	Message	Date
Ashwin Kumar Sivakumar	1af10420ce	fix(db): convert ai_credits timestamp columns to TIMESTAMPTZ ... 9 columns across ai_plans/user_ai_subscriptions/ai_feature_costs/ ai_usage_logs were TIMESTAMP (no timezone), left over from whatever pre-20260703210000 mechanism originally created these 4 tables, but crates/db/src/models/ai_credits.rs maps all of them to DateTime<Utc>, which sqlx requires TIMESTAMPTZ for. This is a live bug, not just a test-setup gap - discovered via crates/db/tests/ai_credits.rs failing with ColumnDecode errors, but any production code path selecting these columns (e.g. current_period_start/end on every wallet read) would hit the same failure. ALTER COLUMN ... USING col AT TIME ZONE 'UTC' is lossless here since every write path uses NOW()/DEFAULT NOW() with no other timezone handling anywhere in the codebase. Applied to both nxtgauge_test and the live nxtgauge database directly; verified all 9 columns converted and the 3 existing user_ai_subscriptions + 4 ai_plans rows' values are intact and correctly interpreted as UTC afterward. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-13 21:44:30 +05:30
Ashwin Kumar Sivakumar	675a5a12c5	chore: trigger ai-credits CI re-run with seeded test data	2026-08-13 20:24:00 +05:30
Ashwin Kumar Sivakumar	1106b0cb8c	fix: remove invalid trailing line from Dockerfile.test ... My own previous trivial-touch commit appended a bare '-- ...' line without a # prefix, which isn't valid Dockerfile syntax and broke the buildx parse ('unknown instruction: --') - explains why the last CI run died immediately again despite the actual fix (corrected password) being in place.	2026-08-13 20:19:59 +05:30
Ashwin Kumar Sivakumar	f2ee346a37	chore: trivial touch to Dockerfile.test to trigger a real ai-credits CI run	2026-08-13 20:16:26 +05:30
Ashwin Kumar Sivakumar	c307ef1ba4	fix(ci): run ai_credits tests via buildx build, not runtime apt-get/docker run -v ... The bare bookworm runner image has no apt-get/package manager at all (the earlier build-essential install attempt failed with 'apt-get: command not found'), and a plain 'docker run -v $PWD:/workspace' wouldn't work either - DOCKER_HOST points at the sibling dind engine (same nested-container setup build.yaml's own comments describe), so a bind mount would look for the path on the wrong filesystem. Matches build.yaml's actual working pattern instead: docker buildx build with context transfer (not a volume mount), using a Dockerfile (Dockerfile.test) whose RUN step runs the test suite and fails the build on a non-zero exit. TEST_DATABASE_URL passed via buildx --secret (not --build-arg) so it never lands in image layer history. Isolated this by testing each piece of the original workflow independently (env/secrets, id+GITHUB_OUTPUT, if: conditionals all checked out fine one at a time) until apt-get was confirmed as the actual failure point. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-13 18:08:31 +05:30