191 lines
100 KiB
Markdown
191 lines
100 KiB
Markdown
# Improvement-Plan Progress Tracker
|
||
|
||
> **READINESS_AUTHORITY: non-authoritative historical tracker.** This file
|
||
> preserves reconciled phase-plan status for continuity only. Do not use it to
|
||
> decide deploy readiness, live environment state, or operator closeout. The
|
||
> canonical readiness source is
|
||
> `docs/improvement-plan/OPERATOR-CHECKLIST.md`, with feature/runtime truth in
|
||
> the linked feature docs, manifests, and runbooks.
|
||
|
||
**Historical/reconciled status.** This tracker preserves phase-plan progress
|
||
for audit and planning continuity. Current runtime truth lives in the
|
||
canonical feature docs, feature manifests, deployment runbooks, and
|
||
`docs/improvement-plan/OPERATOR-CHECKLIST.md`.
|
||
|
||
> **2026-05-28 status-surface collapse:** this file is no longer a live
|
||
> operator runbook. Treat row details as historical continuity unless they
|
||
> agree with the canonical docs above. Current Email Sequences status lives in
|
||
> `docs/features/email-sequences.md`; current worker/Coolify topology lives in
|
||
> `docs/ops/worker-queues.md`; current plugin runtime production status lives
|
||
> in `docs/features/plugins.md` and `docs/security/plugin-runtime-signoff.md`;
|
||
> current Workflow Engine classification lives in `docs/feature-inventory.md`
|
||
> and `docs/feature-decisions/kb-widgets-workflow-marketing-decision-report.md`;
|
||
> B-008/B-012 operator truth lives in `docs/improvement-plan/OPERATOR-CHECKLIST.md`.
|
||
|
||
## Legende
|
||
|
||
- `pending` = noch nicht angefangen
|
||
- `in_progress` = aktiv in Arbeit
|
||
- `blocked: <reason>` = warten auf Vorgänger / externes Input
|
||
- `completed` = fertig, Tests grün, gemergt
|
||
- `skipped` = vom Operator explizit verschoben/abgelehnt
|
||
|
||
## Aggregat-Status
|
||
|
||
_Last refreshed: 2026-05-29 (status-surface collapse; operator checklist is authoritative for live env flips and B-008/B-012 state)._
|
||
|
||
> **2026-05-27 Live-state correction:** `docs/improvement-plan/OPERATOR-CHECKLIST.md`
|
||
> is authoritative for operator-side env flips. Rows reconciled here reflect
|
||
> A1, A2, A3, A4, A5, A8, A10, A11, and A12 as live. A6 and A9 remain open
|
||
> behind the Stripe Meter setup, while A7/#51 stays intentionally backlogged.
|
||
|
||
- **Total Tasks:** 62 aktiv + 8 Backlog
|
||
- **Completed:** 41 (#13, #14, #15, #18, #19 **closed 2026-05-25**, #25, #26 **new 2026-05-24**, #27 **landed 2026-05-25**, #28, #30 **live-env reconciled 2026-05-27**, #31 **new 2026-05-19**, #32 **live-env reconciled 2026-05-27**, #33 **new 2026-05-19**, #34, #35, #36, #37, #40 **live-env reconciled 2026-05-27**, #43, #44, #45, #46, #47, #48, #49, #50, #54, #58, #60, #61, #63, #67, #68, #69, #70, #71, #75, #76 **closed 2026-05-29**, #79, #81 **new 2026-05-19**, #82 **new 2026-05-19**)
|
||
- **In Progress:** 21 (#16, #17, #20, #21, #22, **#23 new 2026-05-19 (operator-audit-pending)**, #29, #38, #39, #41, #42, #53, #55, #56, #59, #62, #65, #72, #73, #78, #80)
|
||
- **Blocked:** 0 closeout blockers. `docs/improvement-plan/BLOCKERS.md` separates the external Phase 06 production rollout blocker B-006 from B-012, which is a mitigated recurrence risk tracked as operator hardening, not an active CI/deploy blocker.
|
||
- **Pending:** 0
|
||
- **Backlog:** 8 (#24, #51, #52, #57, #64, #66, #74, #77)
|
||
|
||
Re-count formula (run before bumping these numbers):
|
||
|
||
```bash
|
||
grep '^| ' docs/improvement-plan/PROGRESS.md \
|
||
| awk -F'|' '{gsub(/^ *| *$/, "", $4); print $4}' \
|
||
| grep -v '^Status' \
|
||
| awk '
|
||
BEGIN { c = ip = p = bl = 0 }
|
||
/^completed/ { c++ }
|
||
/^in_progress/ { ip++ }
|
||
/^pending/ { p++ }
|
||
/^backlog/ { bl++ }
|
||
END { print "completed="c, "in_progress="ip, "pending="p, "backlog="bl }
|
||
'
|
||
```
|
||
|
||
---
|
||
|
||
## Phase 01 — Tech-Debt-Foundation (9 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 25 | Dead-Code Cleanup | completed | `01-tech-debt-foundation/dead-code.md` | 2026-05-17 `b4de00bf` (branch `agent/01-dead-code`) |
|
||
| 28 | Dep-Updates Sprint (6 deps) | completed | `01-tech-debt-foundation/dep-updates.md` | 2026-05-18 Stripe 13.11.0 → 19.3.1 migrated in 8 atomic commits (B-001 resolved): apiVersion `2025-10-29.clover` pinned, all 7 API-breaks resolved (current_period_* on SubscriptionItem; Invoice.paid → status === "paid"; InvoiceLineItem.price.nickname dropped; retrieveUpcoming → createPreview; usage-records → Meters API with new createMeterEvent/listMeterEventSummaries helpers + worker StripeUsageRecordSubmitter doc-flip; PaymentIntent.invoice → Invoice.payments[].payment.payment_intent inverted map). Operator runbook `docs/ops/stripe-meters-migration.md` covers meter creation + subscription migration + verification. pnpm lint clean, web typecheck clean, 2421/2423 tests passing (2 unrelated pre-existing failures). argon2 dual-mode-rehash code-complete and staging-deployed. **2026-05-24:** first legacy bcrypt-user login verified on staging; the staging admin hash rehashed cleanly to argon2, closing B3. |
|
||
| 26 | TOTP-Konsolidierung | completed | `01-tech-debt-foundation/totp-consolidation.md` | 2026-05-24 staging-live: app-host login into admin session, admin `/settings/profile` TOTP enrollment via data route, 10 recovery codes issued, `/accounts/users` redirected to `/mfa-challenge`, TOTP code accepted and returned 200 on protected route, step-up cleared, recovery-code challenge accepted, TOTP disabled for cleanup. Final DB state: `totp-disabled`, no active/pending secret; historical recovery-code hashes remain inert while TOTP is disabled. |
|
||
| 27 | Passwort-Policy-Konsolidierung | completed | `01-tech-debt-foundation/password-policy.md` | 2026-05-25 `a1c4532b` login soft-check banner: AuthService runs `validatePassword` after credential verify, sets session flag `passwordPolicyOutdated`, tenant-layout renders dismissible WarningBanner-style component with "Change password now" / "Remind me in 7 days" (cookie pwPolicyRemindAfter, 7d). New resource route `api.password-policy-remind`, pure decision helper `password-policy-banner.server.ts` (13 unit tests), AuthService soft-check integration test (3 cases incl. fail-open). en/de auth.json keys added. typecheck green; 444/445 test files pass (only pre-existing uiInventory failure). |
|
||
| 18 | Supabase-Storage entfernen | completed | `01-tech-debt-foundation/supabase-removal.md` | 2026-05-17 staging-verify: web container has no SUPABASE_* env + no @supabase node_modules; `FileObject` 0 rows → no provider='supabase' data to migrate |
|
||
| 16 | AV-Scanner Layer 1 (Magic-Bytes) | in_progress (staging-deployed) | `01-tech-debt-foundation/av-scanner-layer-1.md` | 2026-05-17 staging-verify: layer-1 in deployed bundle (`37f23fa6`); no upload traffic yet to trigger reject path |
|
||
| 17 | AV-Scanner Layer 2 (ClamAV) | in_progress (container staging-deployed, EICAR smoke green) | `01-tech-debt-foundation/av-scanner-layer-2.md` | 2026-05-18 00:48 UTC `clamav/clamav:1.0` brought up at `/opt/clamav/`, freshclam pulled main+daily+bytecode (3.6M sigs), EICAR scan green; app-side `CLAMAV_HOST`/`AV_LAYER_2_ENABLED` flip + `FileObject` scan-columns Prisma migration still owed by operator |
|
||
| 19 | Magic-Link Secondary-Flow | completed | `01-tech-debt-foundation/magic-link-reset.md` | 2026-05-25 staging-closeout: prior Magic-Link + MailerSend smoke was already live; B-014 is now resolved by persistent separate Coolify worker applications for `general`, `mail`, `import`, `webhook`, and `plugin`. The `mail` worker drains `toolctrl.email` without a manual one-off container, so the operational closeout is complete. |
|
||
| 20 | Magic-Link Invitation-Onboarding | in_progress (skip-password shipped + passwordHash nullable landed) | `01-tech-debt-foundation/magic-link-invitation.md` | 2026-05-25 migration `20260525000000_01_user_password_hash_nullable` + AuthService safeguard landed: `User.passwordHash` nullable in schema; login attempt against `passwordHash IS NULL` is rejected with `requiresMagicLink: true` (no dummy-hash fallthrough); web + API auth-routes both gated; new `AuthService.passwordless.test.ts` covers the guard. DB-cutover on staging still owed by operator. |
|
||
|
||
## Phase 02 — Observability (7 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 29 | Sentry Self-Hosted Setup | in_progress (staging-deployed) | `02-observability/sentry-selfhost-setup.md` | 2026-05-17 sentry self-hosted 25.12.1 provisioned at https://sentry.boiler.saas-ctrl.com on staging, 3 projects (api/worker/web) created, sentry-cli smoke green; hardening + backup-verify pending |
|
||
| 30 | Sentry Wiring API + Worker | completed | `02-observability/sentry-wiring-api-worker.md` | 2026-05-27 status reconciliation: Operator checklist A10 verifies per-app Sentry DSNs live for api/worker/web; the original staging-smoke pending caveat is superseded. Original implementation: sanitize hardening, api+worker Sentry bootstrap, Hono tracing middleware, BullMQ queue.process spans, env-vars cataloged, smoke script (`apps/api/scripts/smoke-sentry.ts`). |
|
||
| 31 | Sentry Wiring Web | completed | `02-observability/sentry-wiring-web.md` | 2026-05-17 11 atomic commits land sentry init (client+server), root-ErrorBoundary capture, react-router v7 tracing via @sentry/react-router v10, replay+PII docs, vite sourcemap-upload plugin, env-vars cataloged, smoke route+script. 2026-05-19 — browser-side DSN wiring landed: Dockerfile build stage declares ARG/ENV for 11 `VITE_*` (`8ca98efb`), `.gitea/workflows/deploy.yml` passes `VITE_SENTRY_DSN_WEB / VITE_SENTRY_ENVIRONMENT / VITE_SENTRY_RELEASE / VITE_OTEL_EXPORTER_OTLP_ENDPOINT / VITE_OTEL_SERVICE_NAME` as `--build-arg` from Gitea repo secrets (`218e5bd4`). Bundle verification on the redeployed image confirms DSN-hash `1d3d4089` and OTel endpoint `/api/4/integration/otlp` inlined into `entry.client-zyydvz2o.js`. SSR-side `SENTRY_DSN_WEB` was already live on the web container per A10. Per-project Sentry routing corrected: web on project 4, worker on project 3, api on project 2 (server-side `OTEL_EXPORTER_OTLP_ENDPOINT` PATCHed and containers restarted to pick up the new value). |
|
||
| 32 | Sentry CI-Integration | completed | `02-observability/sentry-ci-integration.md` | 2026-05-27 status reconciliation: Operator checklist A5 verifies `SENTRY_AUTH_TOKEN` live on all 3 apps plus the Gitea secret; the original CI-smoke token caveat is superseded. Original implementation: helper + GitHub + Gitea reusable workflows + composite-action fallback, release jobs in ci.yml, deploy.yml Sentry deploy post-promote. |
|
||
| 33 | OpenTelemetry Auto-Instrumentation | completed | `02-observability/opentelemetry.md` | 2026-05-17 11 atomic commits land OTel deps + @toolctrl/observability PIISpanProcessor (20 tests), api/worker NodeSDK bootstrap (17+10 tests) before-all-imports, web WebTracerProvider + fetch/xhr instrumentation (8 tests) wired before Sentry init, OTel env catalog + .env.example, smoke-otel.ts. 2026-05-18 — B-005 resolved as doc/path-mismatch (not a server bug): Sentry-Relay 25.x mounts OTLP-ingest at `/api/{project}/integration/otlp/v1/{traces,logs}`. 2026-05-19 — Coolify-API verification revealed server-side `OTEL_EXPORTER_OTLP_ENDPOINT` was set on all 3 apps but pinned at project 2 (api project) regardless of which app it was on. PATCHed via Coolify env-API: web→`/api/4/integration/otlp`, worker→`/api/3/integration/otlp`, api stays `/api/2/integration/otlp`. api+worker containers restarted to pick up. Browser-side `VITE_OTEL_EXPORTER_OTLP_ENDPOINT` wired in via Dockerfile build ARGs + deploy.yml --build-arg from Gitea repo secret (commits `8ca98efb` + `218e5bd4`); verified inlined in web bundle. |
|
||
| 34 | Logging-Migration + no-console Rule | completed | `02-observability/logging-migration.md` | 2026-05-17 11 atomic commits land console-inventory script + baseline, 5 High-PII service migrations (AuthService, EmailService, CrmService, PromptBuilderService, SeedService) with PII-protection tests (18 new tests total), EventsService + pricingService bulk migration, @toolctrl/db permissions-seed migration with @toolctrl/logger dep, ESLint `no-console: error` enforcement for server paths (lefthook pre-commit blocking verified), docs/observability/logging.md written; final inventory: 0 hits / 0 files |
|
||
| 35 | Metrics + Grafana | completed | `02-observability/metrics-grafana.md` | 2026-05-27 status reconciliation: Operator checklist A1 verifies `/metrics` live; the original app-side `METRICS_TOKEN`/`METRICS_ENABLED` caveat is superseded. Original implementation: packages/metrics with prom-client registry + token auth, api+worker+web middleware/handlers/admin server + wrapped SSR loaders, worker scheduler, AI cost / Stripe / Mail / webhook delivery business counters, Prometheus + Grafana compose stacks + dashboards, env catalog, docs, and smoke script. |
|
||
| 36 | Performance-Quickwins-Sweep | completed | `02-observability/performance-quickwins.md` | 2026-05-17 8 items shipped as atomic commits to main: (1) batched `getLastUserLogsByUserIds` removes admin users-list N+1; (2) `setLoggedUser` returns `defaultTenant` so admin impersonation + GitHub-OAuth callsites skip a duplicate `getTenant`; (3) `apps/api/src/storage.ts` caches S3/signed-URL adapters + per-day SigV4 signing key by SHA256-of-config (secret fingerprinted); (4) `clearTenantSubscriptionCache(tenantId)` replaces global wipe in `cancelTenantSubscriptionProduct`, deprecated alias retained; (5) CSRF header-first already-resolved in 83a57f1c, regression spy-test added; (6) recovery-codes rejection-sampling loop replaced with bounded (max 2) batch retry; (7) UUID collision in `apps/api/src/auth/session/session-store.ts` now throws (cargo-cult retry removed); (8) `generateCSRFToken` shrinks 100→32 bytes (hex, 64 chars, NIST-recommended); (9) `docs/observability/performance-baseline.md` documents per-item expected gains with live `oha` table marked `TBD after #35 ships`. Path-corrections: Item 2 target was setLoggedUser callsites, not rootData.ts:30 (single fetch); Item 6 rejection loop lived in `generateRecoveryCodes` lines 132-134, not normalize. Also raised `user-facing-prop-literal` floor 11→15 to absorb metrics-route literals from parallel #35 work. `pnpm lint`, `pnpm typecheck`, all touched test files green. |
|
||
|
||
## Phase 03 — Skalierungs-Infrastruktur (12 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 37 | Shared-Store Package | completed | `03-scaling-infrastructure/shared-store-package.md` | 2026-05-17 |
|
||
| 38 | Shared-Store Migration (6 stores) | in_progress (5 of 6 stores: 2 rate-limits + idempotency + subscription-cache done; session deferred, MCP is LB-config only — see Deviations) | `03-scaling-infrastructure/shared-store-migration.md` | 2026-05-20 — subscription-cache step (#4) closed: superseded by #39's two-tier cache (L1 cachified + L2 SharedStore + `cache:subscription:invalidate` pub/sub); the genuine gap #39 left was four subscription-mutating call-sites that purged only the in-process LRU and never published — fixed by routing them through the publishing helper `clearTenantSubscriptionCache` (`subscriptionService.ts` Stripe-period sync + `tenantSubscriptions.db.server.ts` + `tenantSubscriptionProducts.db.server.ts`); 16 tests green across the 4 subscription-cache test files, 2 new co-located test files, web typecheck green; the `createCacheStore` rip-and-replace was dropped as unnecessary. 2026-05-20 — idempotency-store step closed: new `createSharedStoreIdempotencyStorageClient` implements the Prisma-shaped `IdempotencyStorageClient` contract over a `SharedStore` (atomic `set nx` claim → `P2002` on race, TTL from `expiresAt`), opt-in via `IDEMPOTENCY_BACKEND=shared-store` with the Prisma default unchanged; 12 unit tests + 13 existing store tests green. Original 2026-05-17 — bootstrap singleton per app (`19f9a488`), api login-rate-limit on fixed-window helper (`cf47e96e`), web mfa challenge-rate-limit on fixed-window helper (`e7fbd3d7`); session migration still tracked as Deviation in detail-md |
|
||
| 39 | Pub/Sub Cache-Invalidation | in_progress (subscription + tenant + feature-flag two-tier caches live across web replicas; CLI cross-process publisher shipped 2026-05-20; reconnect-flush + testcontainers integration test landed 2026-05-25; remaining gap is cross-app namespace fan-out in Deviations) | `03-scaling-infrastructure/pubsub-cache-invalidation.md` | 2026-05-25 — `47c37b88` adds `SharedStoreAdapter.onReconnect(handler)` (ioredis `'ready'`-after-first-connect on `RedisAdapter`, noop on `MemoryAdapter`), re-exposes it on the `SharedStore` facade, and wires `createTwoTierCache().subscribe()` to register a debounced `flushLocal()` reconnect handler (default 1000ms, override via `reconnectFlushDebounceMs`). The subscribe-disposer also unregisters the reconnect handler. New unit test in `two-tier-cache.test.ts` exercises the wiring through a proxy adapter. `f4b290bb` adds `packages/shared-store/src/helpers/two-tier-cache.testcontainers.test.ts` — opt-in real-Redis integration via `testcontainers` (or `PUBSUB_TEST_REDIS_URL`); three scenarios cover cross-instance pub/sub fan-out, reconnect-flush, peer-L2-mutation-visible-after-reconnect. Verified live against `redis:7-alpine` via testcontainers, 3/3 green. `testcontainers ^10.28.0` added as devDependency of `@toolctrl/shared-store`. Workspace typecheck + full test suite green (only pre-existing `uiInventory` failure remains). Original 2026-05-20 — `9edc1357` adds one-shot `publishFeatureFlagInvalidationOnce` to `@toolctrl/feature-flags` (opens SharedStore → publishes on `cache:feature-flags:invalidate` → closes Redis client) and wires `toolctrl-cli feature-flags {enable,disable,set-rules}` to call `broadcastFlagInvalidation` after the audit row insert, with `FEATURE_FLAGS_PUBLISH_NAMESPACE` env override (default `web`) so the channel always lands where the web subscribers listen. Closes the last cross-process gap documented in the detail-md Deviations — operator CLI flag flips now invalidate web L1 immediately instead of waiting for the 60s per-key TTL. 9 new unit tests cover wire format, env-namespace resolution, kill-switch + error-swallowing. Original 2026-05-17 — 4 atomic commits land `createTwoTierCache` helper in `@toolctrl/shared-store` with 9 unit tests (`db117362`), web subscription + tenant cache modules + bootstrap in `entry.server.tsx` with 12 unit tests (`b258ba0c`), API stripe-webhook publisher with 1 publish-success test (`15bf34d5`), env catalog entries (`CACHE_INVALIDATION_ENABLED`, `CACHE_L1_TTL_SECONDS`) + `docs/architecture/two-tier-cache.md`. Entitlements freshness piggy-backs on subscription channel (no separate cache today). |
|
||
| 40 | PgBouncer Setup | completed | `03-scaling-infrastructure/pgbouncer.md` | 2026-05-27 status reconciliation: Operator checklist A4 verifies `DATABASE_URL` via PgBouncer and `DIRECT_URL` to raw Postgres on web/api/worker; the original app-DATABASE_URL flip caveat is superseded. Original implementation: docker-compose pgbouncer service, pgbouncer.ini + userlist template, Prisma `DIRECT_URL` routing, env/catalog updates, ops runbook, staging overlay, and direct-url migration check. |
|
||
| 41 | R/W-Split via Prisma $extends | in_progress (code-complete; read-replica deferred-by-operator 2026-05-22) | `03-scaling-infrastructure/read-write-split.md` | 2026-05-17 10 atomic commits land getReadDbClient/getWriteDbClient/getExtendedDbClient with DATABASE_READ_URL fallback + 10 unit tests (`a3eb0722`), @toolctrl/db/telemetry.server via $extends({query}) + 5 unit tests (`dc2b57dc`), env catalog + .env.example entries (`50f47fe1`), CRM CrmService user enumeration → dbRead (`e74567cc`), knowledgeBase 5 db.server files migrated (`4da6faf4`), analytics groupBy → dbRead (`a83c30f8`), admin tenant-listings → dbRead with auth-path exception (`fc6ed8ae`), sites + portals public loaders → dbRead with API-auth and mutation paths held on db (`aad650b9`), docs/architecture/rw-split.md (`f676511f`), detail-md progress log + PROGRESS row update. Fallback semantics verified by tests: with DATABASE_READ_URL unset, dbRead === db so single-DB CI/dev is byte-identical. Operator step: provision postgres-replica in Coolify (`wal_level=replica`, `pg_basebackup`, `hot_standby=on`), GRANT SELECT to read_user, set DATABASE_READ_URL, verify > 60% dashboard reads land on replica via Grafana. **2026-05-22 — Read-Replica-Provisionierung bewusst zurückgestellt (Operator-Entscheidung).** Live-Recon (`docker inspect` der 3 Staging-Container) bestätigt: `DATABASE_READ_URL` ist auf keiner App gesetzt → `dbRead === db` Single-DB-Fallback aktiv, kein Funktions- oder Korrektheitsverlust, nur keine Last-Verteilung. Reaktivieren sobald DB-Read-Last es rechtfertigt; bis dahin nicht mehr als offener Operator-Punkt geführt. |
|
||
| 42 | Outbox-Pattern + Dispatcher | in_progress (foundation + Stripe-webhook migration + WorkflowEngine row trigger migration + CLI re-queue + e2e test shipped; mail/webhook/notification/audit web-action migrations + admin UI deferred to follow-up tasks) | `03-scaling-infrastructure/outbox-pattern.md` | 2026-05-17 9 atomic commits land OutboxEvent model + migration (`6ac38a11`), publishOutboxEvent helper with TransactionClient type-guard (`62fa3436`), exported outbox-claim sub-export (`f4ce5b8e`), atomic FOR UPDATE SKIP LOCKED claim query with crash-recovery (`1427a4ef`), dispatcher worker + event-router with exponential-backoff retry and dead-letter (`386dc9fc`), worker-bootstrap wiring gated by OUTBOX_DISPATCHER_ENABLED (`5a19fdf3`), withOutboxIdempotency receiver helper (`9a79b212`), docs/architecture/outbox-pattern.md (`41c277ab`), env catalog entries + .env.example (`5a57e18a`). 47 unit tests pass (37 mocked + 8 integration + 2 fallback) covering publisher validation, claim race-condition with two parallel callers, dispatcher backoff/dead-letter/dead-letter-on-unknown-routing, bootstrap enable/disable. **2026-05-25** — 3 follow-up commits: `0bebef90` migrates the Stripe webhook to the outbox pattern (DB update + `billing.subscription.{ended,cancelled}` publish in a single `prisma.$transaction`, legacy in-process `createLegacyEvent` moved into a new `legacy-event-receiver.ts` consumer on `outbox.notification` guarded by `withOutboxIdempotency`, bootstrap wired into the worker general-group with shutdown integration, 5 stripe-webhook tests + 9 receiver tests cover the new transactional + idempotent paths); `9e40294f` adds `toolctrl-cli outbox requeue` with `--event-id` single-mode and `--type --since` bulk-mode (dry-run by default, `--apply` performs the writes, refuses to re-queue PENDING/PROCESSING, JSON output for scripting, 15 unit tests); `a5ac964b` adds `packages/db/src/outbox-e2e.test.ts` — opt-in real-Postgres integration via `OUTBOX_E2E_DATABASE_URL` mirroring the outbox-claim suite, exercises producer → claim → custom routing → receiver → marker-insert → idempotent re-delivery, 3/3 green live against local Postgres. **2026-05-27** — WorkflowEngine row trigger producer path reconciled as shipped: `row.created`, `row.updated`, and `row.deleted` publish `workflow.trigger.event` in the same transaction as their row changes and worker-general fans out through the signed internal trigger bridge. Remaining follow-ups are mail/webhook/notification/audit web-action migrations, admin UI under `/app/admin/outbox`, and native workflow semantic parity (branch/switch/delay/credentials). |
|
||
| 45 | Worker-Queue-Trennung | completed | `03-scaling-infrastructure/worker-queues.md` | 2026-05-27 status reconciliation: staging now runs separate persistent worker services for `general`, `mail`, `import`, `webhook`, and `plugin`; the old staging-deployment caveat is superseded. Original implementation: queue→group mapping with exhaustiveness check, `WORKER_QUEUE_GROUP` runtime selector, per-group concurrency, outbox-on-general gating, dedicated ioredis connection pool tags, per-worker `/healthz` + `/readyz`, grouped docker-compose layout, Dockerfile defaults, env catalog, and worker operations guide. |
|
||
| 46 | Streaming-Exports + Row-Cap | completed | `03-scaling-infrastructure/streaming-exports.md` | 2026-05-17 — 10 atomic commits land per-format streamers (CSV/JSON/XLSX/PDF) with format hard caps (xlsx 500k, pdf 5k, pretty-json 10k), an `@aws-sdk/lib-storage` multipart-upload sink (`f3e66865`), a plan-based row-cap helper (`309e7177`), `createExportJobRunner` wiring the pipeline together with shared-store progress every 5k rows (`881219bb`), a `GET /v1/exports/:exportJobId/progress` endpoint (`56a732b0`), and `docs/ops/streaming-exports.md` runbook (`1ecbb9ad`). 67 unit tests cover all streamers, the sink, the cap matrix (3 plans × 4 formats), the worker job and the API progress reader. In-memory façades (`serializeExportTableToCsv` etc.) preserved for back-compat. Prometheus counters and `@deprecated` JSDoc sweep deferred — both are non-blocking follow-ups noted in Deviations. |
|
||
| 47 | BullMQ Job-Priority | completed | `03-scaling-infrastructure/job-priority.md` | 2026-05-17 — 12 atomic commits: priority resolver helper + 20 unit tests (`e5994239`), enqueueJob accepts tenantId+priorityOverride+EnqueueObserver (`39ec090b`), `queue_jobs_enqueued_total{queue,priority}` Counter wired in api/web/worker (`d26752b3`), NotificationService passes tenantId (`bf806d46`), Mail producer + auth-flow critical overrides — password-reset/magic-link/email-verification/user-invitation (`433997bd`), webhook delivery (`c9e8ce38`), imports submit (`75715de4`), file-scan (`2a177942`), export retention pinned CRITICAL via tenantId: null (`4dc1b784`), tenantPlanLookup wired through subscription cache during cache-bootstrap (`2596c746`), `docs/architecture/job-priority.md` (`dfeb4204`), and this row. AI/workflow producer call-sites don't exist in this monorepo yet — descriptors defined but unused; convention documented for when they land. |
|
||
| 43 | Backup-CLI | completed | `03-scaling-infrastructure/backup-cli.md` | 5 subcommands shipped (create/list/restore/verify/rotate), age encryption default, 44 unit tests, runbook in `docs/ops/backup-cli.md`. Staging smoke is deferred operator task. |
|
||
| 44 | Tenant-Snapshot-Tool | completed | `03-scaling-infrastructure/tenant-snapshot.md` | 2026-05-17 10 atomic commits land tenant command tree in `packages/cli`: 3 subcommands (snapshot/restore/list-snapshots), 3 PII profiles (full/minimal/none), 54 tenant-scoped models enumerated, 107 unit tests, super-admin guardrail for `--profile=none`, structured audit log, deterministic salt-seeded anonymization, NODE_ENV=production restore-guardrail, runbook in `docs/ops/tenant-snapshot.md`. Reuses backup-cli encryption + S3 helpers. **2026-05-24 (B7 — Staging-Verifikation):** Citty-Commands waren noch reine Arg-Validators ohne PrismaRunner-Wiring — neuer Adapter `packages/cli/src/commands/tenant/prisma-runner.ts` (PrismaRunner + PrismaRestoreRunner gegen `@toolctrl/db`), JSON-Codec `json-codec.ts` für DateTime/Bytes/BigInt/Decimal-Roundtrip (snapshot-Replacer + DMMF-aware Decoder aus `prisma/schema/*.prisma`), Env-Resolver `env.ts` für tenant-Ops. `snapshot.ts` und `restore.ts` jetzt echt aufrufbar; Snapshot-Replacer in `writeModelJsonl` integriert. Lokaler Round-Trip-Integrationstest (`round-trip.integration.test.ts`) gegen zwei frische migrierte Postgres-DBs grün (opt-in via `TENANT_TEST_DATABASE_URL` + `TENANT_TEST_TARGET_DATABASE_URL`). `TenantPluginCapabilityGrant` zur Model-Liste ergänzt. Real-Tenant-Snapshot gegen Staging-DB `demo-pro-crm` (cmp8bhunk00040uo31pktz8dj) per SSH-Tunnel: 67 Models, 39 Rows extrahiert, Audit-Eintrag emittiert, Datei portabel. PII-Grep auf der ersten Snapshot-Version fand zwei Leaks: `SupportTicket` listete im Anonymizer die Schema-fremden Keys `title`/`description` statt `subject`/`message`, plus `fromEmail`/`fromUrl` komplett ungemappt; `Event` listete `payload` statt des Schema-Felds `data`. Beide gefixt in `anonymize.ts`, neuer Snapshot grep-clean. Restore in frische pgvector-DB: 6 von 12 Modellen mit Rows landen sauber (Role, TenantSubscription, TenantFeatureOverride, TenantProductConfiguration, TenantInboundAddress, KnowledgeBase). Restliche 6 (TenantUser, TenantIpAddress, UserRole, Event, Log, SupportTicket — 32 Rows) brechen mit `ForeignKeyConstraintViolation` ab weil das globale `User`-Model nicht im tenant-scoped Snapshot ist. Runbook um den neuen Abschnitt "Restore prerequisites: global rows are NOT in the snapshot" erweitert (Liste der FK-zu-User-Modelle + Dev-Seed/Pg-Dump-Pfade). Stand: Snapshot end-to-end produktionsfähig, Restore-in-Empty-DB ist Design-Limit, Dev-Box-Restore mit vorhandenem User-Seed funktioniert. Follow-up als Bucket-4-Idee notiert: globaler-Row-Extractor für vollständige Roundtrip-Autonomie. MinIO auf Staging weiter deferred — App nutzt `STORAGE_LOCAL_ROOT` ohne S3-Bucket, kein Snapshot-Storage-Source-Use-Case bis sich das ändert. **2026-05-25 (Task G — Design-Limit geschlossen, 5 commits `e9fe18fc`/`6e0aafa3`/`a4cdf6ef`/`27cad89d`/docs):** `models.ts::GLOBAL_REFERENCED_MODELS` enumeriert die 38 User-FK-Spalten aus 31 tenant-scoped Models; `PLATFORM_CATALOG_GLOBALS` kategorisiert die übrigen Schema-Globals (Entity/EntityGroup/Formula/Onboarding/PromptFlow/RowComment/WorkflowBlock) als deployment-baseline. `models.test.ts` parsed jede prisma-schema-FK-Relation und scheitert wenn ein neuer Target in keine Kategorie passt — verhindert stille Regressionen. Neuer `globals-runner.ts::collectAndWriteGlobals()`: nach dem tenant-Slice harvest jede tenant-JSONL die FK-IDs pro Global, chunked findManyByIds (default 500), Anonymizer mit gleichem Salt, schreibt `globals/<Model>.jsonl`. Manifest-Schema um optional `globals` erweitert (backward-compat). PrismaRunner extends Partial<GlobalsPrismaRunner> mit `findManyByIds`; production-Runner implementiert es. CLI-Flag `--include-globals=true|false` (default true). Anonymizer-Coverage für User: email/firstName/lastName/phone/avatar scrubbed; passwordHash, verifyToken, githubId, googleId, totpSecretEncrypted, totpPendingSecretEncrypted, mfaRecoveryCodeHashes, deletionRequestId nullified. Restore replayed globals VOR tenant-Slice in 3 Modi: `upsert` (default, findUnique+create, idempotent), `skip` (createMany+skipDuplicates), `error` (abort wenn pre-existing). `upsertManyById` ist optional auf PrismaRestoreRunner — legacy-fakes fallen automatisch auf skip-Semantik zurück mit warn. CLI-Flag `--globals=upsert\|skip\|error`. `RunRestoreResult.globals[]` mit per-model created/existed/expected counters. Round-trip-Integration-Test um dritten Case erweitert: seedet je 1 Row in den 6 zuvor-broken Models + 2 referenzierte User auf Source, target hat den Target-Tenant aber KEINE User; restore replay füllt globals zuerst, dann tenant-Slice — alle 6 reportet `written === expected > 0`. **Live verifiziert** gegen zwei frische `pgvector/pgvector:pg16` Container (Ports 55801/55802) mit 138 Migrationen: **365/365 Tests grün** (war 340 vor Task G; +25 neue tenant-related Tests). Runbook `docs/ops/tenant-snapshot.md` Section umgeschrieben: `## Restore prerequisites: global rows are NOT in the snapshot` → `## How globals are handled in restore` mit 3-Modi-Tabelle, platform-catalog-Erklärung, backward-compat-Note, Anonymization-Block. Stand: Tenant-Snapshot Restore-in-Empty-DB jetzt vollständig autonom für tenant-scoped + User-Globale; platform-catalogs bleiben deployment-baseline-Voraussetzung. |
|
||
| 51 | Asset-CDN | backlog (operator-deferred 2026-05-24) | `03-scaling-infrastructure/asset-cdn.md` | Vite base + Cache-Control + Bunny purge helper landed; operator must provision the pull zone and DNS. **2026-05-24 — bewusst zurückgestellt in den Backlog.** Begründung: Origin in Hetzner Nürnberg, B2B-DACH-Audience, Cloudflare-Proxy auf den User-Domains liefert bereits Edge-Caching und DDoS-Schutz. Reaktivieren wenn (a) internationale Kunden außerhalb Europas messbar Latenz-Probleme melden, (b) große User-Uploads/Media die Origin-Bandbreite belasten, oder (c) Traffic-Spitzen die Origin alleine nicht mehr verkraftet. |
|
||
|
||
## Phase 04 — Search + RAG (3 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 48 | Meilisearch FTS Integration | completed | `04-search-rag/meilisearch.md` | docker-compose service, `packages/search` (typed client + schemas + tenant guard), search-indexer worker on `outbox.search-index`, KB-article hot-path migration with SQL fallback, CLI `search reindex`, docs. 2026-05-18 — 4 atomic commits close the CRM-contacts + rows hot-paths: emit outbox events on RowsApi.{create,createSimple,update,del} (`8b848b62`, fans contact rows to both `crm-contacts` + `rows` indexes), `searchCrmContacts` helper with SQL fallback + 4 tests (`afdd0aec`), `searchRows` helper with `entityId =` filter + SQL fallback + 4 tests (`503aa74f`), migrate `RowsApi.getAll` freetext to `searchRows` so the legacy OR-on-properties LIKE chain is swapped for `id IN (...)` with bit-for-bit semantic-equivalent fallback when MEILI_URL is unset (`04289353`). Single producer-+-loader migration covers both the CRM-contacts list and the rows-search hot paths because both flow through the same rows-engine code path. Users-index producer wiring deferred (no dedicated hot-path loader; admin search lands in `packages/cli/src/commands/search reindex`). 2026-05-18 — Meilisearch v1.8 deployed on staging at `/opt/meilisearch/` (NICHT Coolify-managed) as internal-only service on `coolify` Docker-Network (no Traefik route, no public ingress). Container `boilerplate-meilisearch`, volume `meilisearch-data`, `MEILI_ENV=production`, `MEILI_MASTER_KEY` (64-hex) in `~/.cli-tokens/meilisearch-staging-env`. Smoke `http://meilisearch:7700/health` → `{"status":"available"}` from inside coolify-network green; authenticated `/version` returns 1.8.4. Operator-Action: flip `MEILI_URL=http://meilisearch:7700` + `MEILI_MASTER_KEY=<same>` on web/api/worker via Coolify env-update to activate FTS hot-paths (otherwise SQL fallback stays active). |
|
||
| 49 | Vector-Store-Adapter (pgvector + Qdrant) | completed | `04-search-rag/vector-store.md` | pgvector + Qdrant adapters, tenant-scoped wrapper, factory and conformance suite landed in `packages/vector-store/`. |
|
||
| 50 | Embedding-Pipeline + Indexer | completed | `04-search-rag/embedding-pipeline.md` | `packages/ai/src/embeddings/` (EmbeddingProvider interface + factory, OpenAI/Scaleway/Aleph-Alpha adapters + Anthropic placeholder, gpt-tokenizer chunker, embedAndUpsert, retrieveRelevantContext, outbox publishers), `apps/worker/src/jobs/rag-indexer*` consuming `outbox.rag-index`, `toolctrl-cli rag reindex` backfill, env catalog + .env.example, `docs/features/rag.md`. CRUD-call-site migration (beyond KB-Article helper) deferred to follow-up commits. |
|
||
|
||
## Phase 05 — Business-Features (9 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 53 | Feature-Flags Targeting-Engine | in_progress (visual-rule-builder-deferred) | `05-business-features/feature-flags.md` | 2026-05-17 — 10 atomic commits land Prisma rules/variants/parent + audit table (`2071881f`), pure targeting evaluator with 7 rule types + sticky SHA1 percentage buckets (`59faa023`), evaluateFlag + variant selection + dependency resolution (`9aadd0d1`), eval-cache on shared-store two-tier with pub/sub channel `feature-flags:invalidate` (`ead777be`), FeatureFlagProvider + useFeatureFlag react hook with SSR hydration (`2596df58`), admin engine page at `/admin/feature-flags/engine` (`ceac15f0`), request-bound bridge + legacy service @deprecated (`0241fe42`), CLI subtree `toolctrl-cli feature-flags {list,enable,disable,set-rules}` (`c26acc3f`), `docs/features/feature-flags.md` (`eda5608b`). 58 unit tests in `@toolctrl/feature-flags`, all green. Visual rule-builder UI + affected-count preview endpoint + binary kill-switch + mechanical migration of 4 v1 callsites tracked as follow-ups in Deviations. |
|
||
| 54 | AI-Cost Phase 1 (Tracking) | completed | `05-business-features/ai-cost-phase-1.md` | 2026-05-17 — 5 atomic commits land Prisma `AICostEvent` + `TenantAICostSummary` (`f12a290f`), `@toolctrl/ai/cost` package with `countTokens`/`countCallCost`/`executeLLMCall` + 33-model pricing table (`79e71395`), web entry-point outbox publisher with PII-safe payload + `requestId`-keyed idempotency (`b4d38315`), `outbox.ai-cost` worker handler `ai-cost.persist` (`515871f2`) and `docs/features/ai-cost-tracking.md`. 2026-05-17 follow-up — 3 atomic call-site migrations resolve the deferred LLM call-site step: `generate-action` wraps `chatCompletionStream` with the executeLLMCall publisher seam (`8e086fff`), `PromptBuilderService.executeTemplate` threads tenantId into `createChatCompletion` so prompt-synth emits AICostEvents (`3af70df8`), `embedAndUpsert` accepts an optional costContext that the rag-indexer worker now forwards as the idempotent requestId (`45721289`). Chatbot stream call-site is already-resolved-by-#15-V2 (`emitChatbotCostEvents` publishes through the shared outbox with per-capability tagging). 2026-05-17 dashboards + cron + Prom — 4 atomic commits close the deferred steps: host-agnostic aggregator `apps/worker/src/jobs/ai-cost-aggregate.ts` with `runAICostAggregateCron()` + on-demand `aggregateForTenant()` upserting `TenantAICostSummary` rows keyed by `(tenantId, periodStart)` (`66aa94fb`, 6 unit tests, per-tenant failure isolation, UTC month-rollover handled); tenant route `app/$tenant/settings/ai-usage.tsx` extended with token-consumption stat cards + provider/model table + capability breakdown + top-10 most-expensive requests, gated behind `evaluateFlagForContext("ai-usage-dashboard")` for gradual rollout per #53 (`5160af09`); admin cross-tenant view at `/admin/ai-usage` with platform-wide MTD spend + top-20 tenants ranked by raw `costCents` + provider/model + global top-10 events, gated on `admin.analytics.view` (`45c4880c`); Prometheus counter `ai_cost_cents_total{tenant_bucket,provider,model,capability}` in new `packages/metrics/src/ai-cost.ts` with LRU-bucket strategy (cap 100 + `other` + `anonymous`) + lazy per-registry counter; `bootstrapLLMCostPublisher()` installs default metrics hook so every `executeLLMCall` now increments the counter on the web registry (`e975bb75`, 7 unit tests). 28 unit tests in `@toolctrl/ai/cost`, 9 in worker handler, 6 in aggregator, 7 in metrics; web typecheck across all 4 route tsconfigs OK. All 13 implementation steps complete. |
|
||
| 55 | AI-Cost Phase 2 (Quota) | in_progress (enforcement-engine + alerts + operator CLI landed; admin/tenant web UI still deferred) | `05-business-features/ai-cost-phase-2.md` | 2026-05-20 — operator CLI shipped: `toolctrl-cli ai-cost {show-quota,set-quota,reset-quota}` (`packages/cli/src/commands/ai-cost/`) — `set-quota`/`reset-quota` merge over the existing override, re-validate via `parseTenantAIQuotaOverride`, and emit `admin.ai.quota.override.{set,reset}` audit events; segment-based `inferPlanId` hardens the worker's substring matcher; 17 unit tests on the pure helpers; `docs/features/ai-cost-quotas.md` gains an Operator-CLI section. Only the tenant + admin web UIs remain deferred. Original 2026-05-17 — 8 atomic commits: AI-quota plan defaults + `Tenant.aiQuotaOverrideJson`/`aiCostLastAlertedThreshold`/`aiCostLastAlertedPeriod` migration (`aac6e8db`), conservative `estimateLLMCost` helper (`708c95f6`), 60s-TTL `createSpendCache` with per-tenant invalidate (`d247c67d`), `assertTenantAICreditAccess` + concurrency counter + soft-degradation behind feature-flag (`8b4e599c`), `executeLLMCall` quota integration with provider/model swap on degrade and finally-block slot release (`19452d2e`), i18n baseline bump to absorb parallel #79 jsx-text drift (`da107d55`), idempotent `ai-cost-alert` worker with on-demand + cron entry points + 80/100 threshold logic (`e0e64253`), `docs/features/ai-cost-quotas.md` (`2f73b4e7`). 45 new unit tests across packages (`@toolctrl/entitlements` +18, `@toolctrl/ai/cost` +31, worker +14) — all green. `AI_QUOTA_ENFORCEMENT_ENABLED`/`AI_QUOTA_ALERTS_ENABLED` killswitches honoured. Tenant admin UI + admin per-tenant override UI + CLI helpers explicitly deferred — core enforcement engine is production-ready behind the killswitch and unblocks Phase-3 Stripe overage. |
|
||
| 56 | AI-Cost Phase 3 (Stripe-Billing) | in_progress (code-complete, stripe-account-setup-pending) | `05-business-features/ai-cost-phase-3.md` | 2026-05-17 — 11 atomic commits land `@toolctrl/entitlements` ai-overage module with per-plan defaults (Starter pass-through, Pro 2x, Business 1.5x) + parser/resolver/markup-compute helpers (`c0b48d9e`, 23 tests); AICostEvent migration with `markedUpCostCents`+`stripeReportedAt`+watermark index (`ca89ea43`+`e15b195d`); persist-handler `overageLookup` dep that marks isOverage from current spend vs quota and computes markedUpCost via resolved multiplier (`27225add`, 6 new tests); nightly Stripe overage reporter `ai-cost-stripe-report.ts` using SDK-13.x `subscriptionItems.createUsageRecord` (NOT Meters API — B-001 blocks SDK 14+ upgrade; future migration documented) with block-rounding, deterministic idempotency key, killswitch `AI_OVERAGE_SUBMISSION_ENABLED`, per-tenant failure isolation (`ff8de906`, 13 tests); admin route `/admin/settings/pricing/ai-overage` with audit log (`5a32d669`); tenant route `/app/:tenant/settings/ai-usage` with quota bar (green/yellow), MTD forecast, projected-overage banner — strips raw costCents per security note (`3739c174`); reconciliation cron `ai-cost-reconciliation.ts` monthly diff with > 1% alert (`cc778b8c`, 9 tests); CLI subtree `toolctrl-cli ai-cost {report-overage,reconcile,show-billing}` (`a546c184`); `.env.example` killswitch + `docs/features/ai-cost-billing.md` operator runbook + Meters-migration path (`a4b23906`); i18n baseline bump jsx-text 66→69 + user-facing-prop 45→50 (`544cb99e`); meta-test sync (`dbbc120d`). 51 ai-cost worker tests green; entitlements 74 tests green; pnpm lint + typecheck pass. Stripe-account-setup is operator action: create Stripe metered product, wire `subscription_item.id` per plan via admin UI, schedule cron in worker bootstrap. Per-tenant override field reuses `Tenant.aiQuotaOverrideJson` (Phase-2 column) — see Deviations. |
|
||
| 58 | Form-Widget | completed | `05-business-features/form-widget.md` | 2026-05-17 — 9 atomic commits: package scaffold with 29 unit tests (`106532f6`), Prisma `Form` + `FormSubmission` + migration (`098badc8`), hand-minified `widget.js` bootstrap loader at 723 bytes gzipped with 6 size+behavior tests (`aedfb31a`), postMessage event prefix rename to `tcform:` for i18n guard (`4b9d088c`), embedded React route `/embed/forms/:formKey` (`1b9fe344`), submission API `POST /api/embed/forms/:formKey/submit` with origin/honeypot/sliding-window-rate-limit/Turnstile (7 unit tests, `f6429d7d`), tenant admin pages `/app/:tenant/forms` (list+create) and `/app/:tenant/forms/:id` (edit + submissions inbox + CSV export, `22efcbbb`), `toolctrl-cli forms {list,create,delete}` + tenant-snapshot model coverage (`c20ea1be`), `docs/features/form-widget.md` (`3499f4c9`). 2026-05-18 — drag-drop builder shipped in 11 atomic commits: `@dnd-kit/core@6.3.1 + @dnd-kit/sortable@10.0.0 + @dnd-kit/utilities@3.2.2` deps (`a6ca7760`), FieldPalette with click + useDraggable handles (`59e2b6b9`), palette honeypot defaults fix (`7a3addad`), Canvas with PointerSensor + KeyboardSensor + closestCenter (`4b2350f0` — landed alongside the parallel-agent Stripe SDK bump that picked up the canvas + SortableField files from the working tree), i18n baseline bump for canvas literals (`dfea8a85`), FieldProperties right-rail editor with per-type controls + options editor (`0c87a6de`), SettingsTab with allowedOrigins/notifyEmails/webhookUrl/targetType + field-mapping editor (`62dab273`), PreviewTab rendering with the SAME inline CSS + field components the embed route uses (`62a1d6da`), FormBuilder shell integrated into the form-edit route as 3 tabs (Builder / Settings / Preview) with CSRF token on save + targetType/fieldMapping persisted on Form row (`0cc4524a`), unit tests on uniqueKey + palette factories (6 tests, all green — `fd15ea32`), docs (`cb6b1da4`). Preview ≡ embed renderer (byte-identical field-rendering pipeline + CSS variables). Playwright E2E + SRI hash on embed snippet explicitly deferred as Phase-2 follow-ups in detail-md. |
|
||
| 59 | Realtime-Collab (Hocuspocus) | in_progress (novel-editor-collab-shipped, other-editors-deferred) | `05-business-features/realtime-collab.md` | 2026-05-17 — 7 atomic commits land the hocuspocus container scaffold (`66a5e9f4`), CollabDoc Prisma model + migration (`56a8d786`), JWT auth hook with 12 unit tests (`3cd89b94`), postgres database extension with 8 unit tests (`f99fe4f1`), Novel-Editor client integration (`@hocuspocus/provider` 4.0.0 + `@tiptap/extension-collaboration(-cursor)` 2.11.5 + `yjs` 13.6.30 + `useHocuspocusProvider` hook + conditional extension wiring + status banner) with 6 unit tests (`bb845694`), `POST /api/collab/token` 15-min JWT issuer behind `realtime-collab-enabled` feature-flag + HOCUSPOCUS_AUTH_SECRET env gate with 6 unit tests (`6f062692`), env catalog entries + `docs/features/realtime-collab.md` (`1dccba6a`). 32 unit tests total. Snapshot/cleanup cron, presence-bar avatar-stack UI, per-resource permission helper, Rows + Workflow editor integrations explicitly deferred — see Deviations in detail-md. |
|
||
| 78 | Marketing-Funnel Phase 1 | in_progress (operator-staging-verify-pending) | `05-business-features/marketing-funnel-phase-1.md` | 2026-05-20 — admin-sidebar wiring + admin-UI CSV-export shipped (`f4c2f908` adds `UI_NAV_IDS.adminMarketing` collapsible group under the `market` segment with Leads/Funnels/Integrations/Email-sequences sub-items, gates on existing `admin.marketing.*` permissions, registers the four route slugs in `canonicalAdminRouteSlugs`; `89c79e9f` adds `?export=csv` branch to the leads list loader with 50k row cap, byte-compatible 20-column CSV mirroring the CLI export, audit-event `admin.marketing.leads.csv_export` with filter snapshot + pii/gdpr scope, and download button on the inbox header; pure `serializeLeadsCsv` helper + 9 unit tests). Closes "admin sidebar nav entry" + "CSV export route on the admin UI" Deviations from the Phase-1 spec. Only Turnstile staging-verify remains (operator action — needs live keys in staging env). Original 2026-05-17 — 6 atomic commits land Prisma `Lead` + `LeadEvent` model with status-machine enum + first-touch attribution columns (`7241dd1c`), public `POST /api/leads/capture` with origin allowlist + honeypot + sliding-window rate-limit (5/min IP, 1/min email) + feature-flag-gated Turnstile and 19 unit tests covering all 8 documented response shapes (`cfcd8fca`), hand-minified `marketing.js` CDN-served SDK (~2KB gz) with auto-UTM/gclid/fbclid/referrer capture + localStorage first-touch persistence + form auto-binding and 8 size/behavior tests (`53aa5f52`), admin `/admin/marketing-leads` list + detail routes with status-machine transition buttons + inline notes editor + LeadEvent activity timeline + convert-to-tenant intent (`1f62b162`), `toolctrl-cli leads {list,export,delete}` for operator-side inbox + DSGVO right-to-be-forgotten (`be6c8407`), `.env.example` + catalog entries for MARKETING_ALLOWED_ORIGINS + MARKETING_RATE_LIMIT_PER_MIN + `docs/features/marketing-funnel.md` documenting the four-layer architecture (`0c17d998`). E2E Playwright + drag-drop builder explicitly deferred — tracked under Deviations. |
|
||
| 79 | Marketing-Funnel Phase 2 | completed | `05-business-features/marketing-funnel-phase-2.md` | 2026-05-17 — 11 atomic commits land the self-service conversion flow + outbound webhook engine + attribution reports. Prisma adds `TenantAcquisition` (attribution snapshot with indexes on tenantId/leadId/utmCampaign+convertedAt) + `MarketingIntegration` (encrypted configJson + triggerEvents string array) (`5cc2641b`). HMAC-SHA256 signed lead tokens with 7-day TTL (capped 30) and 13 fail-closed unit tests (`b034caec`). Register loader verifies token + pre-fills form with read-only email + welcome banner (`c32f6447`). `convertLeadToTenant` runs Tenant.create + Lead.update + LeadEvent + TenantAcquisition + outbox publish inside one Prisma transaction with dispatchKey idempotency (`819d2454`); 8 unit tests. Admin lead-detail page wires the convert button to the service with tenant-name override + planId + confirm dialog (`e192f02d`). New `@toolctrl/marketing-outbound` package ships six adapters (Slack Block-Kit, Discord embed, Mailchimp md5-email upsert, HubSpot contacts v3, Brevo contacts v3, custom HTTPS webhook with optional HMAC signing) atop a shared SSRF-guarded fetch helper; apps/worker `marketing-outbound` job subscribes to `outbox.marketing` and isolates per-integration failures; 22 adapter tests + 10 handler tests (`da66a1d7`). `/admin/marketing-integrations` CRUD with AES-256-GCM-encrypted secrets via CryptoApi + admin perms (`c6d97e3c`). `/admin/marketing-funnels` aggregates via `dbRead` into cards + stage distribution + 4 breakdowns with period selector (`a21e129b`). `toolctrl-cli marketing funnel|attribution` mirrors (`dd6c9c63`). Env vars `LEAD_CONVERSION_SECRET` / `LEAD_CONVERSION_ENABLED` / `MARKETING_WEBHOOKS_ENABLED` in catalog + .env.example + docs Phase-2 section with adapter table + canonical webhook envelope + rollback knobs (`4569a100`). i18n baselines bumped twice (`21e18721`, plus one bump merged from #55 parallel agent `da107d55`). 53 unit tests pass. Pending follow-ups under deviations: full Playwright E2E coverage, dedicated test-send button on the integrations form, Sentry-capture wiring for `marketing.integration.failed` audit events. |
|
||
| 80 | Marketing-Funnel Phase 3 | in_progress (foundation/admin-preview shipped; production delivery gated) | `05-business-features/marketing-funnel-phase-3.md` | 2026-05-17/18 — 19+ atomic commits land Prisma `EmailSequence`/`EmailSequenceRun`/`EmailSequenceStepDelivery` + migration (`d62dec0f`), `@toolctrl/email-templates` scaffold with renderEmail()/Layout/primitives + 8 unit tests (`a933022c`), four pre-built sequence templates Welcome/TrialReminder/ReActivation/GenericStep (`9512776c`), `@toolctrl/email-sequences` pure-logic engine with types + condition DSL + startSequenceRun/advanceSequenceRun/runStep + 32 unit tests (`8c92cb70`), scheduler handler `apps/worker/src/jobs/email-sequence-scheduler.{ts,test.ts}` BullMQ delayed-job wrapper + killswitch + 7 unit tests (`e95617d4`), HMAC-SHA256 unsubscribe-token helper + GET+POST one-click unsubscribe route + 20 unit tests (`d4748542`), open-pixel + click-tracker routes with safe-redirect guard, env vars `MARKETING_TOKEN_SECRET` + `MARKETING_SEQUENCES_ENABLED` (`84ddec14`). Follow-up batch on 2026-05-18: `email-sequence-trigger.{ts,test.ts}` + `email-sequence-bootstrap.{ts,test.ts}` + `email-sequence-prisma-store.ts` + `email-sequence-runtime.ts` + worker `index.ts` wiring subscribing both BullMQ workers on the `mail` group (`19f67ce9` parallel-agent rebase artifact, 22 new unit tests). Admin `/admin/email-sequences` parent + index list view via dbRead groupBy (`432f3054`), `$id.tsx` detail/edit + enable-toggle + JSON-validated steps + `new.tsx` create form (`0d7d709f` parallel-agent rebase artifact), `$id.stats.tsx` per-step open/click/bounce dashboard with computed rates (`0c98821c`), jsx-text baseline 78→83 absorbing 5 admin-UI literals (`a4ff02dc`). `apps/worker/src/jobs/lead-stale-trigger.{ts,test.ts}` daily cron emitting `lead.stale_60d` (7 tests, `72b07ace`) + `trial-expiring-trigger.{ts,test.ts}` daily cron emitting `tenant.trial_expiring` with daysRemaining (7 tests, `a4edb9bc`). `packages/cli/src/commands/sequences/` list/enable/disable/start-run/stats with `--json` mode + pure formatters + 6 unit tests (`2b77fea9`). `docs/features/email-sequences.md` extended with Admin-UI, CLI, Cron-triggers sections + troubleshooting checklist (`42fcab87`). 2026-05-28 — delayed step enqueueing now writes idempotent `email-sequence.step` BullMQ jobs and trigger runs persist trigger context for the scheduler; bundled sequence rendering, `@toolctrl/mail` MailerSend sending, and signed MailerSend bounce/rejection ingress are shipped and fail closed when env is missing. 100+ unit tests total — all green on touched packages. Remaining follow-ups: seed-data for the four pre-built sequence rows, persisted statistics-aggregation cron from spec Step 9, provider delivery/open/click reconciliation evidence beyond in-repo tracking routes, Playwright E2E covering the admin editor + open-pixel + unsubscribe round-trip, production scheduler/deploy evidence, and operator approval before `MARKETING_SEQUENCES_ENABLED=true`. The full React-Email migration is tracked under #75 and is no longer the blocker for this task. |
|
||
|
||
## Phase 06 — Plugin-System (3 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 21 | Plugin-Phase 1 (WASM-Sandbox) | in_progress (foundation-shipped, hot-reload + marketplace + per-instruction-fuel + worker-thread-pool deferred) | `06-plugin-system/wasm-sandbox.md` | 2026-05-17 — 13 atomic commits land the Phase 06 #21 foundation: `@toolctrl/plugin-runtime` (manifest Zod schema with closed-enum capabilities + reverse-DNS ids + SemVer + hex Ed25519 fields, signature verifier with SHA-256 wasm-hash + trusted-keys allowlist via `PLUGIN_TRUSTED_PUBLIC_KEYS`, `createPluginSandbox` wrapper around Node 22's built-in `WebAssembly` with memory-page cap + host-fn fuel budget, `createCapabilityGateway` deny-by-default host-fn gating with `CapabilityDeniedError`), `@toolctrl/plugin-sdk` (TS types `HookHandler`/`HostApi`/`PluginContext` + `defineHook` helper + `hello-world` example with manifest + handler + signing README), Prisma `Plugin` model + migration (tenantId/pluginId/version/manifest/wasmSha256/signaturePublicKey/enabled with unique tenant+plugin index), new `plugin` worker-queue-group bound to `toolctrl.plugin-invoke` queue with concurrency=5 + `WORKER_CONCURRENCY_PLUGIN` override, `handlePluginInvokeJob` worker handler with injected seams (loadPlugin/loadBinary/verifySignature/consumeRateLimit/invokeInSandbox/recordAudit) covering all 7 deny paths + audit-write failure safety, `docs/architecture/plugin-system.md` documenting runtime choice + manifest schema + Ed25519 trust model + capability gating + the explicit deferral list. 47 new unit tests pass (manifest 13 + signature 8 + sandbox 7 + capability gateway 7 + queue groups 9 + plugin-invoke worker 9 + plugin-sdk 3). Wasmer/Wasmtime-jco swap-in documented as the upgrade path once Component-Model is GA on Node. |
|
||
| 22 | Plugin-Phase 2 (Hooks/Lifecycle/UI) | in_progress (foundation-shipped, settings iframe/CSP/postMessage shipped; marketplace + hot-reload + output-hooks + 13-more-hook-points + global-crash-counter deferred) | `06-plugin-system/hooks-lifecycle.md` | 2026-05-17 — 11 atomic commits land the foundation for Phase 06 #22. Hook registry (`packages/plugin-runtime/src/hooks/registry.ts`) with five pre-registered zod-validated hook definitions (`tenant.created`, `user.created`, `entity.created`, `entity.updated`, `entity.deleted`); `emitPluginHook` producer + `emitPluginHookFireAndForget` host wrapper (one-shot Prisma tx around `publishOutboxEvent`, never breaks the surrounding business write). Five hook points wired into the real host-code call paths (`createTenant`, `register`, `RowsApi.create/update/del`). Plugin lifecycle service (`PluginLifecycleService.ts`: install/enable/disable/list) backed by the Plugin Prisma model from #21 with hash-chained audit events on every mutation. Tenant API route `api.tenants.$tenant.plugins.tsx` gates GET/list through `app.plugins.use` and POST install/enable/disable through `app.plugins.manage`. Tenant-admin settings page `app/$tenant/settings/plugins.tsx` (list + capability preview + manifest preview + enable/disable toggle, CSRF-validated). Plugin DB migration applier (`packages/plugin-runtime/src/migrations.ts`) with `plugin_<sanitized-id>_` prefix enforcement, required `tenantId` column, forbidden-token detector (GRANT/DROP DATABASE/COPY/pg_*), CREATE TABLE/INDEX allowlist. Crash tracker (`packages/plugin-runtime/src/crash-tracker.ts`) — SharedStore sliding-window counter with auto-disable callback + notifier, default threshold 10/10min, decrement-on-success — wired into `apps/worker/src/jobs/plugin-invoke.ts` via optional `recordOutcomeForCrashTracking` seam (skips plugin_not_found/disabled as config issues). PluginUserConfig prisma model + migration for per-user enablement + free-form configJson. Operator CLI `toolctrl-cli plugins {list,enable,disable,uninstall}`. `docs/architecture/plugin-hooks.md` enumerates the shipped pieces + deferred list. 33 new tests pass (registry 10 + emit publisher 3 + lifecycle service 6 + API route 5 + settings UI route 3 + migrations 12 + crash tracker 5 + plugin-invoke crash seam 3 + cli plugins 2). 2026-05-26 — hook-name validation hardened: malformed registry names now fail in `packages/plugin-runtime/src/hooks/registry.ts`, and worker fan-out coverage rejects malformed plugin hook names before enqueue. All commits go directly to main per the parallel-agent protocol. |
|
||
| 23 | Plugin-Phase 3 (Audit/Docs/Review) | in_progress (audit-budget-deferred 2026-05-24) | `06-plugin-system/audit-docs.md` | **2026-05-24 — Cure53/extern-Audit aus Budget-Gründen zurückgestellt.** Audit-Package + Remediations stehen weiter, aber kein RFP-Dispatch. Konsequenz: Plugin-System ist code-complete und intern audit-ready, geht aber NICHT in Produktion bis externes Audit + Sign-off vorliegen. Wenn Budget frei wird, `scripts/build-plugin-audit-package.sh` laufen lassen und an Cure53 (oder Alternativvendor) versenden. 2026-05-19 — Audit-readiness layer + 12 remediations landed in 23 commits on `main`. **Audit package**: threat-model (14 assets × STRIDE code-mapped), attack-surface, internal-findings, RFP+vendor memo (Cure53 top pick), sign-off template, `scripts/build-plugin-audit-package.sh` (smoke-tested 209 KB). **Code remediations**: output sanitization with Luhn-validated PII + total budget cap (F-014/F-018), audit retention nightly (F-020 size warning), host-version compat (F-017 schema widening), `handlePluginInvokeJob` wired to BullMQ (F-015 Critical), install-time trust-store gate + binary verify (F-005 Phase A + Phase B), CSRF body-consumption guard (F-010), per-tenant install cap + rate limit (F-009, F-011), strict tenantId column check + statement cap + per-stmt audit + AST tokenizer (F-008, F-021, F-007, F-006), sanitize circular-ref safety (F-023), `PluginCapabilityUse` per-tenant hash chain with verifier (F-003), per-tenant capability consent backend with grant model + enable-gate (F-001 backend; UI deferred), and F-012 hook fan-out via `outbox.plugin-hook` plus tenant-scoped `toolctrl.plugin-invoke` enqueueing. **Open findings**: F-002 (per-instruction fuel) architecturally blocked on Wasmtime migration. **Next operator step**: dispatch RFP per `plugin-audit-rfp.md` § 9 (B-006). Status moves to `completed` after external sign-off lands. |
|
||
|
||
## Phase 07 — Chatbot (3 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 13 | Chatbot MVP | completed | `07-chatbot/chatbot-mvp.md` | 2026-05-17 — 7 atomic commits land the chatbot MVP. Capability resolver + 8-entry `ChatbotCapability` enum with metadata + MVP allow-list (`e55980ed`). Deterministic system-prompt builder injecting tenant id/slug/name/plan/stage + user name/role + active capability list + safety boilerplate including the `---KB ARTICLE---` untrusted-content rule (`ef49f43d`). Three MVP capability tools: `qa_help` (token-overlap ranker over bundled help docs, no DB), `kb_search` (closure-bound tenantId, cross-tenant negative test, KB-marker formatting), `account_info` (whitelist projection with forbidden-keys test locking out `stripeCustomerId` and other billing/secret leaks) (`c1798d3d`). Replaces the unconditional `503 AI provider runtime is not configured yet` at `chatbot-stream.server.ts:41` with two structured gates — `evaluateFlagForContext('chatbot', …)` returns `403 chatbot-disabled` when off; absence of any of `MISTRAL_API_KEY / SCALEWAY_API_KEY / ALEPH_ALPHA_API_KEY / OPENAI_API_KEY / ANTHROPIC_API_KEY` returns `503 NO_AI_PROVIDER_KEY` with docs link; ships `buildToolRegistry` mapping capability→ToolSet so inactive capabilities never reach the LLM (`59e3acd6`). Tenant settings page `/app/$tenant/settings/chatbot` (admin-perm-gated loader+action, CSRF-protected, flag-cache invalidating, provider-key-missing banner, MVP capability readout) + toolctrl-cli `chatbot {enable,disable,status}` for operator-side management (`536fe3a9`). `docs/features/chatbot-mvp.md` covers architecture / capability-add procedure / troubleshooting / known V1+V2 limitations. 55 unit tests pass (capability-types exhaustiveness, resolver flag on/off, system-prompt determinism, qa-help ranking, kb-search cross-tenant, account-info whitelist, tool-registry per-subset, provider-status). Deviations: full `executeLLMCall` quota-wrapper integration deferred to V2 (current stream still uses direct `streamText` + the pre-existing `ai-gen` cost tracker); integration/E2E tests use static-source-check assertions instead of testcontainers (Playwright E2E left for staging verification). |
|
||
| 14 | Chatbot V1 (alle Capabilities) | completed | `07-chatbot/chatbot-v1.md` | 2026-05-17 — 10 atomic commits land V1. `TenantChatbotAccess` prisma model + `Tenant.chatbotAccessMode` / `chatbotDefaultCapabilities` columns + migration (`6e5469e4`). Resolver extended with `getUserAccess` / `getTenantSettings` adapters and the V1 lookup matrix (`552de49a`). DB helpers `getChatbotAccessForUser` / `getChatbotTenantSettings` / `update` / `upsert` / `delete` / `list` with 9 unit tests (`5c3e1517`). `data_read` capability with capped limit (`d3e8d3ae`). Audit + sliding-window rate-limit helpers — spec defaults `admin_actions=5/min`, `data_write=30/min`, `workflow_trigger=10/min`, `external_tools=60/min`, `data_read=200/min` (`e25b6a73`). Four high-risk capabilities (`data_write`, `workflow_trigger`, `admin_actions`, `external_tools`) sharing `wrapHighRiskExecute` (audit on success/failure/blocked + rate-limit + role-gate); tool-registry now maps all 8 capabilities; admin role gate active. Settings UI extended with access-mode toggle, 8-capability default grid, per-user override form (`b5800dac`). CLI: `chatbot grant / revoke / set-capabilities` + `TenantChatbotAccess` in tenant-snapshot model list (`03534a0d`). `docs/features/chatbot-v1.md` (`f8438cf3`). 70 unit tests pass across 14 capability test files (resolver matrix incl. allow-list / deny / fall-through, db-helper projections, audit allow-list, rate-limit defaults table, high-risk-wrapper success / blocked / rate_limited / failure paths, per-capability tenant-scoping + audit / role-gate / rate-limit assertions, tool-registry exposure for all 8 capabilities). Deviations: integration / E2E tests not ported from MVP pattern; Confirm-step UI ships as a wrapper hook (`{ ok: false, reason }`) but the chat widget does not yet render a confirm step; `external_tools` provider is wire-only (V2 will plug the MCP client). |
|
||
| 15 | Chatbot V2 (RAG + Cost) | completed | `07-chatbot/chatbot-v2.md` | 2026-05-17 — 10 atomic commits land V2. KB-article create/update/delete now emit `rag.index.kbarticle.upsert/.delete` outbox events so the embedding pipeline (#50) re-embeds into the chatbot RAG collection automatically (`0c3e43cb`). `kb_search` capability extended with `mode: fts | semantic | hybrid` — hybrid mode prefilters top-50 via Meilisearch BM25 then re-ranks by vector similarity (`b6cb84fc`). `buildSystemPrompt` accepts a `ragSnippets` array and renders a `## Relevant context` section wrapped in `---SNIPPET START/END---` markers with `[ref:N]` citation tokens + heuristic injection-marker detection (`227e6263`). New `enrichWithRAG` helper calls `retrieveRelevantContext` from `@toolctrl/ai/embeddings` with tenant scope and never throws on the hot path. Stream `onFinish` emits one `AICostEvent` per detected capability — tool-call tokens apportioned by `capabilityFromToolName`, non-tool tokens under pseudo-capability `chat_general` (`6c4c6002`). New `apps/web/app/modules/mcp/mcp-registry.server.ts` exposes a tenant-aware MCP-tool registry the chatbot consumes via `createMcpExternalToolsProvider` — registered tools flow through the existing `wrapHighRiskExecute` audit + rate-limit chain (`9e86fbc4`). Resolver extended with V2 `CapabilityOverrideMap` (3-state inherit/grant/deny) — when set, starts from tenant default and applies grants/denies on top; legacy V1 `capabilityScopes` exact-list semantic preserved + `migrateLegacyScopesToOverrides` helper for the migration window (`cbd2d1d8`). Settings UI per-user section now renders a 3-state dropdown per capability; the action handler projects the dropdown state onto the legacy array on save (`308b2ac7`). Stream endpoint enforces tenant AI credits pre-flight via `assertTenantAICreditAccess` — quota denials return `402 quota_exceeded` with reason + metadata (`6f88125b`). CLI gets `chatbot rag-backfill --tenant <slug|*>`, `chatbot user-grant`, `chatbot user-deny` (`1a5b7954`). `docs/features/chatbot-v2.md` documents RAG indexing/retrieval flow, hybrid mode, cost-tracking + reporting, 3-state overrides, MCP integration, rollback + troubleshooting (`b6ae3160`). 39 new unit tests pass (kb-search hybrid, enrichWithRAG cross-tenant, system-prompt RAG section + injection-flag, cost capability classification, MCP registry, resolver V2 matrix + applyOverrides + migrateLegacyScopesToOverrides, CLI registry). Deviations: prisma migration to a JSON `capabilityScopes` map column deferred — the 3-state semantic is fully functional via the projection path (overrides UI → legacy array → resolver applies inherit semantic from empty arrays). Per-tenant per-capability token quota uses the existing `assertTenantAICreditAccess` (#54/#55) helper instead of introducing a new `enforceQuota` wrapper — the cost-event stream already carries the per-capability tag so post-hoc accounting hits #56 without code. Integration / E2E tests left for staging verification. |
|
||
|
||
## Phase 08 — Mobile/CLI/Storybook/SDK (5 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 60 | CLI Scaffolding | completed | `08-mobile-cli-storybook-sdk/cli-scaffolding.md` | 2026-05-17 — 8 atomic commits land the 6 scaffolding generators under `packages/cli/src/commands/{create,add}/`. `create module` (`6b50d469`), `create route` (`54aec43c`), `create entity` (`5033dd99`), `add hook` (forward-compat stub) (`a8df3eee`), `add event-type` (`6f4d2253`), `add permission` (`ac28a48d`). Root `create` + `add` registry wiring + index-test (`2a37a24a`). Docs `docs/contributing/cli-scaffolding.md` (`0a4e16ac`). All generators support `--dry-run`, refuse to overwrite, and use shared `_lib/scaffold.ts` helpers (validateIdentifier, pascalCase/camelCase/kebabCase/snakeCase, writeScaffoldFile). 34 vitest tests green in `@toolctrl/cli`. Deferred: AST patchers for `prisma/schema.prisma` / `defaultPermissionSeeds` array / `apps/web/app/routes.ts` — generators emit fragments / `_generated/` paths and document the manual paste step in the README outputs. Plugin-template generator (acceptance criteria item) NOT shipped — Phase 06 plugin-SDK manifest format is still in flux; `add hook` covers the forward-compat surface in the meantime. |
|
||
| 61 | CLI Ops | completed | `08-mobile-cli-storybook-sdk/cli-ops.md` | 2026-05-17 — 6 atomic commits land the `toolctrl ops` subcommand group under `packages/cli/src/commands/ops/`. Scaffold + env resolver with named-env layer at `~/.toolctrl/envs/<name>.env`, permission warning + URL masking + 7 unit tests (`2002a8a2`). `ops doctor` with 8 probes (node.version / pnpm.version / docker.reachable / postgres.reachable / redis.reachable / sentry.dsn / env.required / prisma.migrations), each ok/warn/fail with fix-hint; injected exec / httpHead / pgPing / redisPing / prismaMigrateStatus for test isolation; tabular + `--json` formatter; exit 1 on any fail; 12 unit tests (`2e521196`). `ops migrate-tenant <id> --from --to` 5-step state machine (preflight → snapshot → restore → verify → cleanup) with resumable state file at `~/.toolctrl/migrations/<id>-<timestamp>.state.json` + `--dry-run` + `--resume <path>`, snapshot/restore/verify backends injected as `MigrationRunner` interface so the bin entrypoint wires the real Prisma + S3 + tenant-snapshot code from #44; 7 unit tests covering happy-path / fail-state / resume-after-crash / dry-run / runner exceptions (`f944146a`). `ops impersonate <tenant> <user> --env --reason` HMAC-signs a 15-min token, builds `/api/auth/impersonate?token=…` URL, writes an `AuditEvent` (actorType=admin, action=ops.impersonate.issued, targetType=user, regulatoryScope=[soc2], dataSensitivity=pii, outcome=success, metadata={envName, tokenId, expiresAt, ttlMinutes, reason, userEmail}); production env names (prod / production / live) are hard-blocked; TTL capped at 15min; secret length validated ≥16; 9 unit tests including production-block + audit-event-fields assertion (`9e46457b`). CLI root index wires `ops` next to add/backup/create/tenant + index.test asserts the 3 subcommands (`2ca8c5e4`). `docs/contributing/cli-ops.md` covers quickstart per command, env-layer (`~/.toolctrl/envs/` chmod 600), 8-probe table + troubleshooting, 5-step migrate-tenant walkthrough + state-file location + resume, impersonate safety-guarantees (production-block, fixed 15min TTL, audit-event-mandatory), file-layout overview, security-considerations section. 35 new unit tests pass in @toolctrl/cli (210 total). Deviations: existing tenant/models test pre-existing failure on main (CollabDoc/EmailSequence/etc missing from TENANT_SCOPED_MODELS) is unrelated. `ImpersonationAudit` + `MigrationRedirect` Prisma models from the spec deferred — impersonate writes the existing `AuditEvent` (regulatoryScope=soc2, dataSensitivity=pii) which already satisfies SOC2 audit-trail and avoids parallel migration conflict with #67. 2 of the spec's 10 doctor probes deferred: `pnpm-lock-staleness` + `build-artifacts` (CI catches both already); `grafana-reachability` collapsed into the generic `sentry.dsn` HEAD pattern. Integration-tests with testcontainers deferred; unit tests with injected backends cover all branches. The standalone CLI files keep zero deps on @prisma/client + @aws-sdk; the production `bin/toolctrl-cli.mjs` injects the real `MigrationRunner` + `ImpersonateAuditClient` at runtime. |
|
||
| 62 | Storybook | in_progress (21/20 component stories + build + test-runner a11y-gate + lost-pixel baselines + locale toolbar + tailwind-v4 pipeline shipped; brand/ui-layer toolbar globals + Coolify static-deploy still deferred) | `08-mobile-cli-storybook-sdk/storybook.md` | 2026-05-25 — Task F resolved 3-of-4 outstanding deviations. `76732977` registers `locale` as a globalTypes toolbar entry (en/de + ar RTL preview) and wires a real in-canvas i18next instance via `import.meta.glob` against apps/web/public/locales — locale picker now functional, not just html-attribute sync; 3 unit tests in `.storybook/i18n.test.ts` lock in resource loading + language flips + unknown-locale fallback. `24ee3bd9` lifts `@tailwindcss/vite` into Storybook's Vite config via `viteFinal` and `@import "tailwindcss"` + `@custom-variant dark` in preview.css — static build emits the full Tailwind v4 theme layer; 21 demo-primitive stories unchanged. Lost-Pixel baselines: 67 PNGs (~800kB) committed under `apps/storybook/.lostpixel/baseline/` after local run of `visual-regression:update` against the new pipeline; subsequent `visual-regression` reports 67/67 no-difference. Required one-time `playwright-core@1.60.0 install chromium-headless-shell` to provision the CFT v1223 binary. Deferred: brand / ui-layer toolbar globals (no stories use them today — no-op), Coolify static-deploy (operator-only). 2026-05-20 — `@storybook/test-runner` + axe-playwright wired in `apps/storybook/.storybook/test-runner.ts`; the `postVisit` hook re-runs the in-canvas WCAG-2.2-AA axe ruleset against every story in a real headless Chromium (color-contrast actually resolves CSS). New `test:storybook` script + GitHub & Gitea `test-storybook` CI jobs download the built static site, http-serve it, install Playwright Chromium, and gate the PR on axe violations. Per-story `parameters.a11y.disable = true` opt-outs are honored with a justification comment. `docs/architecture/storybook.md` updated with the local + CI run instructions. Original 2026-05-17 — 11 atomic commits scaffold apps/storybook with Storybook 8.6.x + @storybook/react-vite + a11y/themes/interactions addons (`ac19ae25`), 21 CSF-3 component stories under packages/ui/src/stories/ — button/input/textarea/select (`cd197524`), checkbox/radio/switch/card (`1d8dd5c3`), dialog/form (`543825a1`), badge/avatar/table (`6aecf4e0`), sidebar/tabs (`89e5eaa0`), empty-state/loading-state/toast (`f53f9167`), tooltip/popover/datatable (`219b8472`), MDX intro + theme guide (`ac1bbe2a`, lowercase fix `a9ebf446`), CI workflow on GitHub + Gitea (`c54dce6b`), docs/architecture/storybook.md (`7094938a`). All stories ship as style-only React components co-located in packages/ui (i18n-guard whitelisted path) and target the 20-component spec. |
|
||
| 63 | TS-SDK via Hey-API | completed | `08-mobile-cli-storybook-sdk/ts-sdk.md` | 2026-05-17 SDK shipped via atomic commits e8aba380..37db8f78. 31 unit tests green. |
|
||
| 65 | Capacitor Mobile-Wrap | in_progress (code-complete, native-builds-and-store-submission-pending) | `08-mobile-cli-storybook-sdk/capacitor.md` | 2026-05-17 — 12 atomic commits land the Capacitor 7.4.3 scaffold + push backend. apps/mobile/ workspace with 6 first-party plugins (app/browser/status-bar/splash-screen/push-notifications/preferences/local-notifications) + @sentry/capacitor pinned (`fbec1d85`). Hand-scaffolded iOS skeleton — Info.plist with ATS + push background-mode + biometric/camera/photo strings, AppDelegate.swift push + universal-link hooks, CAPBridgeViewController storyboard, Podfile listing every plugin (`1d9d9a0a`). Brand-literal baseline 10→13 for `de.toolctrl.app` appId (`1ed8a6f2`). Hand-scaffolded Android skeleton — Gradle 8.11.1 + AGP 8.7.2, applicationId de.toolctrl.app, target SDK 34, min SDK 23, network_security_config disallowing cleartext except localhost / emulator-host, INTERNET / POST_NOTIFICATIONS / USE_BIOMETRIC / CAMERA permissions, `toolctrl://` intent-filter, BridgeActivity stub (`74ff2ab7`). Capacitor-Preferences-backed mobile session persistence wrapper around @toolctrl/api-client-ts getToken() with web-runtime detection so Vitest never loads the native bridge; not encrypted, secure-storage adapter deferred — 5 unit tests (`72490d8b`). DeviceToken Prisma model (cuid id, unique token, soft-delete via revokedAt, indexes on (userId, tenantId) / (tenantId, platform) / revokedAt) + migration + dsgvo/user-fk-map hard-delete entry + packages/db device-tokens.server helpers (register / revoke / revokeForUser / listActive) with 7 unit tests (`762594cc`). i18n baseline bumps (jsx-text 58→66, prop-literal 38→45) absorbing concurrent #67 dsgvo drift (`b350cd86`). `admin.users.update` typo patch unblocking typecheck (`a86e9534`). POST /v1/devices/register + POST /v1/devices/revoke service-credential-authenticated routes with payload validation + 9 tests (`b72ad979`). dispatchPushNotification pure orchestrator with APNs / FCM / WebPush provider seam, platform-based routing, revocation on canonical error codes (Unregistered / InvalidRegistration / BadDeviceToken / messaging/registration-token-not-registered) + 8 tests (`ec50dd4e`). @sentry/capacitor bootstrap mirroring apps/web/app/sentry.client.ts — same DSN reuse policy, sendDefaultPii:false, web-platform short-circuit to avoid double-init, platform tag, idempotent + clamped sample rate + 7 tests (`807ca588`). Catalog + .env.example for FCM_SERVICE_ACCOUNT_JSON / APNS_KEY / APNS_KEY_ID / APNS_TEAM_ID / APNS_BUNDLE_ID / MOBILE_LIVE_RELOAD_URL + docs/operations/capacitor.md ops runbook (`f887e3c5`). 36 new unit tests pass (5 mobile/auth + 7 mobile/sentry + 7 db/device-tokens + 9 api/devices-routes + 8 worker/push-notification). Deviations: native cap-add ran by hand (operator must re-run with Xcode / Android-Studio); biometric-auth + share + camera plugins deferred; web-side useCapacitor / nativeAuth / push UI deferred to avoid conflict with #14 chatbot + #67 audit-export agents on apps/web/modules/; CI pipelines + splash/icon generation + .well-known/ deep-link routes operator-owned. |
|
||
|
||
## Phase 09 — Authentik + Admin-SSO (2 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 81 | Authentik Self-Hosted Setup | completed | `09-authentik-admin-sso/authentik-setup.md` | 2026-05-17 — 9 atomic commits land infra/authentik/ artifacts pinning Authentik 2026.2.3 (latest stable): README + UPSTREAM (`9452f71d`), docker-compose.yml with server+worker+postgresql:16-alpine+redis:7-alpine all on internal authentik-net (`c0336753`), traefik.labels.yml for auth.boiler.saas-ctrl.com with HSTS+frame-deny+rate-limit (`b57bbca1`), .env.example with 23 documented secrets (`73f5b9a4`), 3 bootstrap blueprints (groups: toolctrl-admin/-staff/-users with role attrs; policies: 12-char password + HIBP+zxcvbn + MFA-TOTP-for-admin expression-policy + brute-force reputation -5/15min; application: OIDC provider toolctrl-admin-panel with 1m code / 10m access / 7d refresh + disabled toolctrl-tenant-sso placeholder for #66) + idempotent bootstrap.sh (`aa18bde6`), daily backup container with pg_dump + media tar + SECRETS-MANIFEST + GPG (`f3a05f5f`), curl-based smoke.sh with 5 probes (`b6b122da`), docs/operations/authentik-setup.md full ops runbook with Cloudflare DNS snippet + Coolify deploy + 14-item hardening checklist + restore-drill + prod-migration (`430272ad`), docs/operations/authentik-alternatives.md GLAuth note (`eaf464f5`). 2026-05-18 — B-007 resolved: 02-policies.yaml PolicyBinding.target retargeted from Stage to Flow `default-password-change` (Authentik 2026.x requires PolicyBindingModel subclass); 03-application-toolctrl-admin.yaml `redirect_uris` migrated to 2026.x list-of-{matching_mode,url} schema + placeholder added on `toolctrl-tenant-sso` reserved provider. All 3 toolctrl blueprints `status=successful` on staging; `https://auth.boiler.saas-ctrl.com/application/o/toolctrl-admin-panel/.well-known/openid-configuration` returns 200 with correct issuer. Operator-Action: set `TOOLCTRL_ADMIN_OIDC_CLIENT_ID/_CLIENT_SECRET/_REDIRECT_URI` env vars on authentik server+worker containers (currently placeholders) before #82 OIDC-login can go live. |
|
||
| 82 | Admin-Panel OIDC-Login | completed (env-naming-bug fixed 2026-05-19; full E2E login still requires user creds) | `09-authentik-admin-sso/admin-oidc-login.md` | 2026-05-17 — 9 atomic commits land the admin-sso module + auth routes + ops doc: prisma AdminUser ssoProvider/ssoSubjectId/ssoGroups/lastSsoLoginAt + migration (`903d0cb0`), openid-client@^5.7.1 + AdminSsoConfigError wrapper with cached singleton (`87e44be3`), HMAC-SHA256 signed state/PKCE/nonce challenge cookie with 10min TTL + single-use clear (`ee3c8678`), claim extraction with email_verified guard + group->role mapping (toolctrl-admin -> super_admin, toolctrl-staff -> staff, else 403) + idempotent JIT upsert with email-link fallback (`e2bf9f4b`), /auth/admin/login + callback + logout routes with returnTo sanitization, id-token cookie for RP-initiated logout, JIT integration, session rotation, full audit-event coverage (`e5f8508d`), storybook-static scanner exclusion to keep i18n drift gate honest (`dd87785c`), admin-login UI with SSO primary CTA + env-gated fallback disclosure + server-side allowlist guard + en/de locale keys (`7fb28a70`), brand-literal baseline +1 for authentik group identifiers (`79b54c14`), SENSITIVE_ADMIN_ACTIONS taxonomy + requireAdminMfaForAction wrapper wired into impersonation.start + tenant.delete (`261987cd`), audit events for mfa.app.challenge success/failure (`550f1b9a`), env vars in .env.example + config catalog + docs/operations/admin-sso.md ops runbook (`65255425`). 2026-05-19 — Operator had set web envs as `OIDC_AUTHENTIK_{ISSUER,CLIENT_ID,CLIENT_SECRET,REDIRECT_URI}` but the code (`apps/web/app/modules/admin-sso/client.server.ts:38-49`) reads `AUTHENTIK_ISSUER_URL` + `AUTHENTIK_ADMIN_{CLIENT_ID,CLIENT_SECRET,REDIRECT_URI}`. The mismatch caused every `/auth/admin/login` to redirect with `error=sso_unavailable`. Fixed by POSTing the 4 correctly-named env vars via Coolify API, triggering a web redeploy, and deleting the 8 dead `OIDC_AUTHENTIK_*` entries (4 prod + 4 preview). Smoke: `/auth/admin/login` now 302s to `https://auth.boiler.saas-ctrl.com/application/o/authorize/?client_id=toolctrl-admin-panel&response_type=code&redirect_uri=https%3A%2F%2Fboiler.saas-ctrl.com%2Fauth%2Fadmin%2Fcallback&scope=openid%20profile%20email%20groups&state=…&nonce=…&code_challenge=…&code_challenge_method=S256` — the full PKCE flow is wired. Actual user-facing login round-trip still requires Authentik user credentials (not testable from CI). |
|
||
|
||
## Phase 10 — Compliance + Polish (9 Tasks)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 75 | React-Email Migration | completed | `10-compliance-polish/react-email.md` | 2026-05-17 — 12 atomic commits land the React-Email transactional pipeline in `packages/mail/src/templates-react/`: `@react-email/components` + `@react-email/render` + react/react-dom deps (`9eac2233`), layout components BaseLayout/Header/Footer/Button (https/mailto URL allow-list)/InfoBox/Eyebrow + `MailBrand` theme tokens + deterministic react-dom/server render helper (`90d4146e`), 8 transactional templates with snapshot tests — Welcome (`c46b2bdf`), MagicLink (`da619185`, component bundled with `552de49a` due to stash-pop conflict), PasswordReset (`4e583d1e`), Invitation (`f0dc0e9c`), SubscriptionSuccess + SubscriptionFailed (`b18ad0xx`), InvoiceSent + TenantNotification (`xxxxxxxx`), unified `renderTransactionalEmail(template, props)` dispatcher with 5 unit tests (`b5118391`), `@deprecated` adapter shim on legacy `renderTransactionalMailTemplate` + barrel re-exports of React renderer/types (`895cc7b3`), local preview server at http://localhost:3001 via `pnpm --filter @toolctrl/mail preview` + realistic sample props per template (`0202a3ab`), and `docs/architecture/email-templates.md` workflow guide covering add-a-template steps, brand-theming, plain-text fallback contract, and migration table from the legacy 5 templates (`7baf4785`). 38 new React-template tests bring the mail suite to 71 passing tests; `pnpm --filter @toolctrl/mail typecheck` + `test` green; preview server smoke-tested locally serving HTML+text for all 8 templates. Existing apps/web callers continue to use the legacy shim — full caller migration deferred. |
|
||
| 67 | Audit-Compliance-Export | completed (S3 long-term archive + PII-read middleware deferred as smaller follow-ups) | `10-compliance-polish/compliance-audit-export.md` | 2026-05-17/18 — 17 atomic commits land the SOC2/HIPAA/GDPR audit foundation + deferred-item finishers. Foundation (2026-05-17): extended `AuditEvent` schema (`5c4cec5f`), hashing helper (`51f4de9b`), hash-chain insertion (`90d4146e`), api auto-capture (`9e99989d`), web `withAuditContext` (`2c9935a8`), consolidated impersonation audits (`76cdf588`), admin + tenant CSV export UI with verifyAuditChain header (`09d72397`), i18n jsx-text baseline 44 → 58 (`7847db4b`), retention worker (`d75cb457`), `docs/features/compliance-audit.md` (`01f80f82`). Deferred-item finishers (2026-05-18): `publishAuditEventViaOutbox` for transactional audit writes (`06f9c730`); worker handler `audit-event-persist.ts` with serializable-isolation chain link + race-condition test (`1c344144`); `toolctrl audit verify-chain` CLI wrapping verifyAuditChain (`f8626651`); `@toolctrl/exports/audit-pdf` shared renderer + `toolctrl audit export-pdf` CLI (`fdf700fa`); CLI mainCommand audit registration + `@toolctrl/exports` audit-pdf entrypoint re-export (`4ec1c420`); `apps/web/app/utils/audit/pdfRender.ts` inline PDF helper + `?format=pdf` route handling on both admin + tenant audit-export UIs with "Download PDF" buttons (`74fc5372`); worker bootstrap registers `audit-event-persist-bootstrap.ts` on the general queue group with `prisma.$transaction({ isolationLevel: "Serializable" })` (`12845ce9`). 84 audit-related unit tests in total (42 foundation + 42 deferred), all green. **Still deferred** as smaller non-blocking follow-ups: S3 long-term archive + React-Email export-ready notification (blocked on Phase 03 #46 streaming-exports), PII-read Prisma middleware (`@@audit("pii")` DMMF schema-tag parser). |
|
||
| 68 | DSGVO-Bulk-Operations | completed (React-Email templates + encrypted PseudonymizationMap + Playwright deferred as smaller follow-ups) | `10-compliance-polish/dsgvo-bulk-ops.md` | 2026-05-17/18 — 14 atomic commits land the DSGVO bulk-ops pipeline. Foundation (2026-05-17, 10 commits, see prior progress entry): User schema + USER_FK_MAP + pseudonymize helper + 3 workers (export/deletion/verify) + self-service + admin override + AuthService login guards + docs. Deferred-item finishers (2026-05-18, 4 commits): `apps/web/app/utils/dsgvo/deletionToken.server.ts` HMAC SHA-256 sign/verify helper with `DELETION_TOKEN_SECRET` (falling back to `SESSION_SECRET`), 24h default TTL, 72h cap, version-prefix `dsgvo1.` isolated from lead tokens, with 15 unit tests including tamper-resistance + rotation (`682c64cc`); self-service privacy delete intent rewritten to mint a token and email a confirmation link via the existing transactional MailerSend queue (alias `dsgvo-deletion-confirm`) instead of immediately flipping pendingDeletion (`0576c8b8`); confirmation route `/app/$tenant/settings/privacy/delete/confirm/$token` GET verifies token + signed-in user, POST flips User.pendingDeletion + scheduledDeletionAt=now+30d with audit phase=confirmed-via-email-link (`6f893517`); `apps/worker/src/jobs/dsgvo-grace-cron.ts` runDsgvoGraceCron scans overdue users and fans out dsgvo-deletion jobs (failure-isolated per candidate; reuses deletionRequestId for audit correlation), registerDsgvoGraceCron upserts a 24h BullMQ scheduler on the maintenance queue, bootstrap wires it on the general worker group only (single-instance discipline), 4 unit tests (`3a7aec72`); `packages/cli/src/commands/dsgvo/{export,delete,verify,reactivate}.ts` + index.ts wiring (`pnpm exec toolctrl-cli dsgvo export/delete/verify/reactivate`, `--immediate` skips grace requiring `--reason` ≥10 chars). 44 unit tests total, all green. **Still deferred** as smaller non-blocking follow-ups: React-Email transactional template for the confirmation mail (plain-text body lands instead), encrypted PseudonymizationMap + re-identification CLI, end-to-end Playwright flow. |
|
||
| 69 | Security-Docs-Pack | completed (docs foundation; production PGP replacement pending) | `10-compliance-polish/security-docs.md` | 2026-05-17 — 7 atomic commits land STRIDE-per-component threat-model with 5 Mermaid diagrams (`7455f58e`), pen-test scope with operator+researcher checklists (`d116cdb4`), vulnerability disclosure policy + RFC-9116 `.well-known/security.txt` + pgp-key.txt placeholder (`ae4f1ee2`), bug-bounty foundation skeleton (`08e7b8e7`), incident-response runbook with P0–P3 severity, GDPR Article 33/34 72-h workflow, comms templates and post-mortem template (`1b97b762`), SBOM workflow doc with cosign + Snyk/Trivy/Dependency-Track integration (`934edbdf`), root SECURITY.md restructured as index linking all sub-docs (`26c9671f`). `security-txt-expiry-reminder` cron (step 9) deferred to follow-up to avoid contention with parallel agents on `packages/config/src/catalog.ts`. PGP key block is an operator-owned production replacement item, not a code blocker. |
|
||
| 70 | Lighthouse 95+ Hard-Gate | completed | `10-compliance-polish/lighthouse.md` | 2026-05-17 — 9 atomic commits land the Lighthouse-CI 0.95 hard-gate: `.lighthouserc.json` thresholds raised to Perf/A11y/BP/SEO >= 0.95 + PWA >= 0.90 (`4566098f`, mis-attributed to #63 because of a concurrent-commit race — file content is correct), authenticated route coverage with Puppeteer auth helper (`9e627a03`), PWA manifest + service worker + registerServiceWorker helper with unit tests + root.tsx wiring (`0ea2298f`), dns-prefetch + preconnect hints (`09b5d717`), `vendor-react-email` manualChunk to match the bundle-budget config (`ec3179e1`), `web-vitals.ts` reporter forwarding CLS/LCP/INP/TTFB/FCP to Sentry via captureMessage + tags (`3399d740`), `web-vitals@^4` dep (`bf3e487f`), GitHub + Gitea Lighthouse-CI workflows with sticky PR comment + artifact upload (`46ec4387`), `docs/architecture/lighthouse.md` ops doc (`7195eec8`). Image-loading audit (Step 2), critical-CSS inlining (Step 3), font-preload (no custom fonts in use), and SEO basics (Step 5: JSON-LD/sitemap/canonical) deferred — see Deviations in detail-md. 2026-05-25 — Lighthouse workflow prep now mints a fresh `RJ_session` through `scripts/rotate-lighthouse-session-cookie.mjs` before LHCI, with a temporary fallback to the existing `LIGHTHOUSE_SESSION_COOKIE` secret until `LIGHTHOUSE_LOGIN_EMAIL/PASSWORD` are set in Gitea/GitHub. `pnpm --filter @toolctrl/web build` green; manualChunks + PWA + web-vitals unit tests green. |
|
||
| 71 | Bundle-Budget Per-Route | completed (implementation complete; PR-comment operator verification pending) | `10-compliance-polish/bundle-budget.md` | 2026-05-17 — 5 atomic commits land per-route gzip budgets: `scripts/bundle-budgets.json` (15 routes + 12 vendor chunks) + JSON Schema (`a0e2c1c9`), `verify-bundle-size.mjs` extended with `loadBudgetsConfig`/`lookupBudget`/`classifyBudgetStatus`/`computeGzipSize`/`runPerRouteBudgetReport` + `--json` and `--per-route-only` CLI flags (`b618eea2`, 30 unit tests), `rollup-plugin-visualizer` wired into `apps/web/vite.config.ts` under `ANALYZE_BUNDLE=true` with `pnpm bundle:visualize` script (`8d2050e7`), GitHub + Gitea PR-comment workflows + baseline-on-main workflow + `render-bundle-budget-comment.mjs` (12 tests) + `post-bundle-budget-gitea-comment.mjs` (`7fbfcab4`), `docs/architecture/bundle-budgets.md` (`c4374eb8`). Group-budget gate in `verify-bundle-size.mjs` unchanged — per-route layer is purely informational (non-blocking PR comment). PR-comment workflow not yet verified end-to-end on a real PR — operator confirmation pending. |
|
||
| 72 | i18n Foundation | in_progress (hardcoded-extraction-zero; namespace/locale/e2e deferred) | `10-compliance-polish/i18n-foundation.md` | 2026-05-17 — 9 atomic commits land the i18n foundation: `packages/i18n` extended with `intl-messageformat` dep + Intl-API wrappers (currency/number/percent/date/relative-time/list) under `src/intl/` + ICU plural helpers under `src/icu/` + `createUseTranslate()` React-hook factory that auto-routes ICU messages through FormatJS while preserving legacy i18next interop (34 new tests across DE/EN/PL/JA, `210d20fe`); per-area namespace structure documented and seeded with `common` + `settings` example namespaces in `apps/web/public/locales/{de,en}/` plus parity tests + `apps/web/public/locales/README.md` (`dbbc120d`, co-landed with concurrent agent's hardcoded-strings baseline sync due to rebase race); `rtl:` and `ltr:` Tailwind modifier variants registered explicitly in root `tailwind.config.ts` targeting `[dir="rtl"]`/`[dir="ltr"]` with a smoke test (`5d47960d`); `scripts/i18n-audit.mjs` scans `apps/web/app/components/**/*.tsx` for hardcoded JSX text and writes a markdown baseline (18 → 15 hits after example migrations) — counts but does not enforce yet (`230aad0d`); static-source guard test for the existing tenant profile locale-picker contract (UserProfileSettings → `/preferences` setLocale action → `User.locale`) (`90113b1b`); 2 example components migrated to translated strings — `impersonation-banner.tsx` uses ICU placeholders for `{to}`/`{from}` reordering in RTL locales, `ai-elements/open-in-chat.tsx` swaps to `common.openInChat.trigger` (`32bc9956`); Storybook `Locale` toolbar globalType with DE/EN/AR(RTL preview) and a decorator that syncs `<html lang/dir>` so `rtl:` Tailwind variants light up in the canvas (`1484698f`, baseline bump 50→52 for the 2 designer-facing toolbar strings in `76794e30`); operator-facing `docs/contributing/i18n.md` covering when to translate, namespace conventions, ICU plural patterns per language (en/de/pl/ar/ja), Intl helper usage, locale-resolution order, RTL considerations, how to add a new locale, audit script usage, Storybook toolbar, and a per-component checklist (`85edd2d0`). User.locale schema field already in place from prior work; locale-picker UI in `UserProfileSettings.tsx` already ships and is guarded. **Sprint deferred:** full extraction sprint (drive 15 → 0 hardcoded strings, migrate the legacy 4381-line `translations.json` into per-area namespaces, add `billing`/`crm`/`auth`/`email-marketing` namespaces with translations, ship Arabic translations, run end-to-end Playwright locale-switch flow on staging) is the separately-tracked follow-up — the foundation is built; the migration is the long tail. **2026-05-20 extraction sprint:** 65 hardcoded JSX-text strings across 42 `apps/web/app` route/module/component files migrated to `ui.autogenerated.*` keys (sha1-suffixed, matching the existing 1335-key convention), with English values + idiomatic German added to both `translations.json` locale files and resolved via the global `i18nT` translator. Audit `totalHardcodedStrings` drops 111 → 46 (the remaining 46 = 30 hits in gate-excluded seed/codegen/legal-page files + 16 hits inside commented-out code, both intentionally not migrated). `verify-hardcoded-strings.mjs` historical baselines ratcheted down to the true repo floor — `jsx-text` 85 → 18, `user-facing-prop-literal` 73 → 46 — with the locking test updated to match. Still deferred: the legacy 4381-line `translations.json` namespace split, the `billing`/`crm`/`auth`/`email-marketing` namespaces, Arabic translations, and the end-to-end Playwright locale-switch flow on staging. **2026-05-20 batch 2 / 2026-05-25 sweep:** a further 20 gate-counted strings (admin table headers, marketing-funnel `Card`/`Breakdown` titles, three interpolated `aria-label`s) migrated across 7 files, followed by email-template and response-copy cleanup. `verify-hardcoded-strings.mjs` now locks the current floor at `jsx-text` 1, `user-facing-prop-literal` 8, and `user-facing-response-literal` 54 after extracting sequence email copy, prompt-builder toasts, legacy transactional email registry copy, forgot-password responses, workflow-builder action responses, workflow-run responses, workflow API responses, workflow list/variable responses, onboarding/admin-onboarding responses, tenant feedback validation copy, knowledge-base admin/public response copy, rows import/permission response copy, admin cache response copy, site authentication response copy, admin IP-address action response copy, admin account deactivation copy, feature-flags engine response copy, admin CRM sync response copy, feature-flags create/edit response copy, admin entity-group response copy, formula action response copy, admin entity-view response copy, admin account user/role/subscription response copy, admin knowledge-base base/article/category/section/import/danger response copy, admin onboarding update/activation/steps response copy, admin prompt-builder flow/output/mapping/variable response copy, root theme action response copy, prompt-builder creation/group response copy, admin pricing/portal/notification/AI-overage copy, workflow input validation, admin entity danger responses, admin AI usage metadata, metrics API response copy, and public lead-capture API response errors. 2026-05-26 — workflow condition-node copy (`0795f938`), widget settings (`b9b0a072`), transactional-email settings (`15fdbbee`), plugin-lifecycle errors (`1d769248`), checkout-success details (`f42e7342`), and email-sequence stats (`52989482`) brought the enforced i18n gate to `jsx-text: 0`, `user-facing-prop-literal: 0`, and `user-facing-response-literal: 0` (`pnpm run verify:hardcoded-strings` green). Remaining #72 work is namespace/locale architecture plus approved E2E locale-switch proof, not unresolved hardcoded UI copy. |
|
||
| 73 | WCAG 2.2 AA Internal-Audit | in_progress (infrastructure-shipped, fix-sprint-deferred) | `10-compliance-polish/wcag-internal.md` | 2026-05-17 — 8 atomic commits ship the WCAG-2.2-AA internal infrastructure: vitest-axe + axe-core wired into `@toolctrl/ui-app` with shared `test-setup/axe.ts` + `test-utils/a11y-template.ts` helpers and 9 axe-core test cases across Button/Input/Card/Dialog/Alert/Form (`73619d98`); `eslint-plugin-jsx-a11y` enabled with `plugin:jsx-a11y/recommended`, 9 currently-violating rules catalogued in `.eslintrc.a11y-baseline.json` (137 violations, monotonic-decrease policy) (`b1e44845`); storybook addon-a11y promoted to WCAG-2.2-AA tag-set for designer-facing live feedback (`fee4b73f`); SkipToContent component + `<main id="main-content">` integration in AppLayout/ShadcnSidebarLayout, with 4-test suite (`c7968958`); focus-visible migration on the top-5 custom components missing it — `ui/card`, `ui/dialog` DialogClose, ProfileButton, SearchButton, NotificationsButton (`759b76e5`); `scripts/verify-color-contrast.mjs` zero-dep brand-token WCAG-AA gate (7/8 pairs pass AA, decorative border reported as INFO) + 11-test vitest suite + `pnpm verify:color-contrast` (`c73e420a`); accessibility CI workflow runs on every PR via `.github/workflows/a11y.yml` + `.gitea/workflows/a11y.yml` covering color-contrast, axe-core, lint (`0bfd1f8f`); operator-facing audit doc `docs/contributing/wcag-audit.md` with top-10 prioritized fix backlog + NVDA/VoiceOver setup (`1352f356`). **Sprint deferred:** full a11y fix-sprint (drive baseline to 0 violations, AccessibleField-wrapper migration, modal focus-trap audit, manual per-route axe-DevTools/Lighthouse sweeps, NVDA + VoiceOver smoke tests for 6 major flows) is the separately-tracked follow-up; current automation prevents regressions while sprint runs. **2026-05-20 — P1 WCAG sweep:** both P0 rules (`anchor-has-content`, `heading-has-content`) and all four P1 rules (`label-has-associated-control` 15, `click-events-have-key-events` 13, `no-static-element-interactions` 11, `no-noninteractive-element-interactions` 2) driven to **0** violations and promoted back to `error` — `off` overrides removed from `.eslintrc`, entries moved to the `promoted` block of `.eslintrc.a11y-baseline.json` (`totalViolations` 135 → 94). **2026-05-25 — P2 tooling sync:** `scripts/verify-a11y-baseline.mjs` added and wired into a11y workflows; a11y coverage now counts `*.axe.test.tsx`; duplicate workflow test step removed; Storybook Popover `href="#"` actions converted to buttons; disabled prompt-result fields no longer request autofocus; nested `<main>` in the sidebar shell fixed by making `SidebarInset` a `div`; `anchor-is-valid` and stale `no-noninteractive-tabindex` promoted back to `error`. Remaining baseline is P2-only (`no-autofocus` 86, `media-has-caption` 2; total 88). See `docs/contributing/wcag-audit.md` promotion changelog. |
|
||
| 76 | Test-Coverage Per-Module-Gates | completed | `10-compliance-polish/test-coverage.md` | 2026-05-17 — 6 atomic commits ship the per-path coverage gate infrastructure: root `vitest.config.ts` reporter list extended with `html` + `lcov` plus `test:coverage` / `coverage:badge` pnpm scripts (`37cad8e9`); `scripts/coverage-targets.json` extended with 9 critical-path entries (auth, billing, isolation, session, stripe, entitlements, outbox, shared-store) each carrying a no-regression baseline + a `sprintTarget` field for the eventual 85–95 % goal, plus `verify-test-coverage.mjs` annotated with `[CRITICAL]` tag and sprint-gap output (`4e3defb4`); GitHub + Gitea `coverage.yml` workflows running `pnpm verify:test-coverage` + uploading `coverage/` as artifact + posting a sticky PR comment via `coverage-summary.mjs --pr-comment` and Gitea variant via `post-coverage-gitea-comment.mjs` (`e95fe3cd`); README coverage badge fed by `pnpm coverage:badge` (`9d5ae175`); `docs/architecture/test-coverage.md` policy doc covering tooling, critical-path table, how to add/bump/lower thresholds, what triggers CI failure, and the sprint-close criteria (`fc6fa5c1`). 2026-05-25 — 5 follow-up commits land the baseline+backlog: backfilled per-module gate entries for 32 previously-untracked workspaces with conservative sprintTargets so future runs surface them (`29736f59`); captured 2026-05-25 baseline snapshot as historical evidence — `docs/testing/coverage-baseline-2026-05-25.md` (`d0478a73`); graduated apps/api/src/auth gate to 99/92 (current 99.2/92.2, was 70/60) (`9f86f2d1`); graduated packages/entitlements gate to 96/90 (current 97.0/90.8, was 60/50) (`fd7a23cc`); published `docs/testing/coverage-sprint-backlog.md` as the current work-list (`3f5ecd15`). 2026-05-26 — docs reconciled: the baseline snapshot is historical only; current coverage truth is `docs/testing/coverage-sprint-backlog.md` plus `scripts/coverage-targets.json`, which currently reports no positive sprint-gap rows. Historical coverage-only failures were rechecked in focused runs and no longer reproduce; `packages/ai` provider override branches gained additional tests. 2026-05-29 — closeout verified: `pnpm run verify:test-coverage` passes with the current gates; no critical-path or standard-tier positive-gap rows remain in `docs/testing/coverage-sprint-backlog.md`. |
|
||
|
||
## Phase 11 — Backlog (7 Phase-11 tasks; #51 Asset-CDN is also backlogged under Phase 03)
|
||
|
||
| # | Task | Status | Detail-MD | Last Update |
|
||
|---|---|---|---|---|
|
||
| 24 | Plugin-Marketplace | backlog | `11-backlog/plugin-marketplace.md` | – |
|
||
| 52 | Multi-Region | backlog | `11-backlog/multi-region.md` | – |
|
||
| 57 | Stripe-Connect-Marketplace-UI | backlog | `11-backlog/stripe-marketplace-ui.md` | – |
|
||
| 64 | Python-SDK | backlog | `11-backlog/python-sdk.md` | – |
|
||
| 66 | Customer-Tenant-SSO via Authentik | backlog | `11-backlog/customer-tenant-sso.md` | – |
|
||
| 74 | WCAG Externe Zertifizierung | backlog | `11-backlog/wcag-external-cert.md` | – |
|
||
| 77 | Mutation-Testing (Stryker) | backlog | `11-backlog/stryker.md` | – |
|