842be56e80
fix(web): wire GDPR data-export buttons to the real backend API
...
Three user-facing "export my data" entry points (settings/privacy,
settings/data, backup/export) all called endpoints that never existed on
the backend: /v1/settings/data and /v1/compliance/export-data both 404.
Every click silently failed or showed a fake "queued, check your email"
message with nothing ever sent.
A fully working, real GDPR export pipeline already exists at
/api/v1/data-export (request -> async generate -> poll status -> download),
just never wired to any UI. Added a shared requestAndDownloadDataExport
flow (web/utils/dataExportFlow.ts) that requests the export, polls status
until ready, then streams and downloads the file, and pointed all three
pages plus userService's mismatched getExportStatus (was missing the
required exportId path param) at it.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-20 17:20:47 +03:00
50d986473e
feat: round-6 external harvest (19 more features, all products green)
...
- gitgram-web (4): per-image alt-text accessibility, "New posts" load-latest pill
- gitgram-backend (1): per-user muted words/tags moderation (MutedWord model + matcher)
- gitgram-mobile (4): swipe-to-action list rows, soft-reset event bus (tap tab scroll-top)
- aitm-api (7): gitnexus api_impact blast-radius/risk endpoints (reuse vendored gitnexus)
- aitm-mcp (3): MCP handshake instructions, context-efficient beads output projections
Note: gitgram-backend adds MutedWord Prisma model — run prisma migrate at deploy.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 19:04:16 +03:00
46bf9b83bf
feat: round-5 external harvest (22 features ported from external/ into 5 products)
...
Harvest valuable features from external/ reference repos, adapted to each
product's stack and wired in; all products typecheck clean.
- gitgram-web (5): clickable @mention/#hashtag linkify in rendered content
(munia), + feed/notification/accessibility patterns; install @testing-library/dom
- gitgram-backend (3): feed thread dedup + muted-thread removal (bluesky),
GitHub star/follow write-back via OAuth (gh-social)
- gitgram-mobile (4): double-tap-to-like + heart bounce (proximity), haptics layer
(bluesky useHaptics), + gesture/feed UX
- aitm-api (4): beads ready/dependency-DAG endpoints + atomic claim (beads)
- aitm-mcp (6): beads_ready work-queue tool, context-efficient projections,
transport arg aliasing (context7/pal-mcp/beads)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-28 18:48:46 +03:00
49b183818c
Unify gitgram + aitimemachine into the monorepo (de-submodule) and merge vendored engines
...
Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as
opaque submodule gitlinks on GitHub) into fully-tracked first-party content.
AITM now merges its 7 vendored repos as first-party engines:
- memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts
- git: vendored C git (bundled binary) + gitnexus (in-process code intelligence)
- agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess)
Includes the full session's product build: Gitgram web/mobile/backend features,
AITM website/CLI/MCP, the unified memory layer, engine build tooling
(scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md),
and extensive test suites.
Build artifacts, node_modules, external/, and gemini-cli are gitignored.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 14:14:09 +03:00