Replace the accidental from-empty migration (which duplicated all 16 prior
migrations and would break a fresh `migrate deploy`) with a proper incremental
migration adding only the new objects: Post.contentLanguage, the MessageReaction
and MutedWord tables, their indexes, and the MessageReaction foreign keys.
Verified the DDL against the live schema. NOTE: a fresh full `migrate deploy`
still fails on a PRE-EXISTING migration-history drift —
20260514174000_repair_scheduled_posts_schema references "ScheduledPost" which no
earlier migration creates. That predates this work; the running stack baselines
the schema (applied + migrations marked resolved) to sidestep it. Reconciling the
older migration history with schema.prisma is separate follow-up.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The whole stack now comes up healthy under one `docker compose` run (gitgram
backend+web + Postgres/Redis + aitm-api/mcp/website + gitnexus); only the
optional tools-profile context7 remains (pre-existing workspace-build issue).
gitgram/backend/Dockerfile: move to a glibc base (node:20-bookworm-slim). Alpine
musl lacks the glibc loader that @tensorflow/tfjs-node's native libtensorflow
needs (ERR_DLOPEN_FAILED), so NSFW detection now runs for real (no stubbing).
Full install WITH lifecycle scripts in the builder (downloads libtensorflow),
node_modules reused in the runtime stage so devDeps like swagger-ui-express are
present for the NODE_ENV=development compose run; openssl + ffmpeg + libgomp1
runtime libs; create writable /app/logs + /app/uploads for the non-root user.
prisma schema: binaryTargets -> debian/arm64 openssl-3 for the glibc runtime.
nsfwDetectionService: lazy-load tf + nsfwjs so a genuinely-unavailable native
lib degrades gracefully instead of crashing at import (still uses real tfjs).
gitgram/web/Dockerfile: npm ci -> npm install (workspace member's standalone
lockfile drifts after dependency additions).
Verified end-to-end through containers: register/login/post/feed 201/200,
web homepage + GitHub->Gitgram /caelum0x both 200.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
aitm-api, aitm-mcp, and gitnexus now build and run healthy in the same
docker-compose stack as gitgram Postgres+Redis.
- NEW aitimemachine/mcp/Dockerfile — multi-stage; builds gitnexus-shared,
gitnexus (native tree-sitter), the root @gitgram/timemachine lib (rewritten to
file:.. + --install-links so file: engine deps are copied, not symlinked), then
the mcp server; runtime starts HTTP transport (node dist/index.js --transport http).
- NEW aitimemachine/gitnexus/Dockerfile — multi-stage (python3/make/g++ for
tree-sitter); builds gitnexus-shared then gitnexus; serve on 0.0.0.0:3010.
- compose: fix build contexts to the aitimemachine root for aitm-api, aitm-mcp,
gitnexus (so file:../ engine siblings resolve); gitnexus host port 3010->13010
(stray host process owned :3010; internal port unchanged).
- scripts/build-engines.sh: npm install before TS engine build when node_modules absent.
- api-server: regenerate stale package-lock; declare ioredis as optionalDependency
and drop the @ts-ignore in providerHealthService (typed dynamic import, tsc clean).
Verified: aitm-api :3001/health, aitm-mcp :3003/health, gitnexus :13010/api/health
all 200 healthy. aitm-website needs a Clerk key; context7 service def is pre-existing-broken.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Re-skin the AITimeMachine marketing site (93 pages) to GitHub's dark palette so
both products feel like one family: #0a0c10/#161b22 surfaces, #30363d borders,
#c9d1d9/#8b949e text, #58a6ff link blue, #238636/#2ea043 CTA green. Adds CSS
vars + Tailwind tokens mirroring gitgram/web, remaps default gray/blue/green
scales onto the GitHub palette, flattens off-brand gradients/glows, Space Grotesk
font + GitHub-style scrollbars. tsc clean, next build green (93/93 pages).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
End-to-end smoke (real Postgres + Redis via docker-compose) caught a real bug
that mocked unit tests missed: createPost passed the request `type` straight to
prisma.post.create, so a client sending lowercase "text" (instead of the
uppercase PostType enum) threw PrismaClientValidationError 500. Now normalized
to the PostType enum (case-insensitive, falls back to POST).
Verified end-to-end: register→login→create post→comment→like→feed all succeed
against a live DB (3 posts / 1 comment / 1 user persisted).
Also adds prisma/migrations/20260629000000_marathon_additions (full schema incl.
MutedWord, Post.contentLanguage, MessageReaction) — resolves the deploy-time
migration that was infra-blocked from generating against the Neon pooler.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
External reference repos (a2a-js, beads, bluesky, context7, gh-social, gitnexus, munia,
proximity, repo2txt, etc.) were orphaned submodule gitlinks used only as harvest sources.
All valuable features ported into gitgram/* and aitimemachine/*. No product code imports
from external/. Removed to focus the repo on the two shippable products.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>