What we shipped

• Control: MOB-01
• Instances: 1
• Category: viewport_meta
• File: N/A

• <!-- db-audit:kind=fk_on_delete_mismatch -->
• • child is ephemeral state (logs, acks, in-flight handshakes, derived counters) → CASCADE is safe
• • child is value-carrying (refs the parent but should outlive it) → SET NULL is safer than CASCADE
• If the code's declared `no action` is wrong, fix the code first, then ship the aligning migration.

• <!-- db-audit:kind=missing_foreign_key -->

• <!-- db-audit:kind=default_mismatch -->
• The database audit found 6 column default mismatches that need to be reconciled between the code and the database.
• Column `organization_databases.status` has a different default value in the database than in your code.
• Column `permission_profiles.type` has a different default value in the database than in your code.

• <!-- db-audit:kind=default_mismatch -->
• The database audit found 6 column default mismatches that need to be reconciled between the code and the database.
• Column `organization_databases.status` has a different default value in the database than in your code.
• Column `permission_profiles.type` has a different default value in the database than in your code.

• <!-- db-audit:kind=default_mismatch -->
• The database audit found 6 column default mismatches that need to be reconciled between the code and the database.
• Column `organization_databases.status` has a different default value in the database than in your code.
• Column `permission_profiles.type` has a different default value in the database than in your code.

• <!-- db-audit:kind=default_mismatch -->
• The database audit found 6 column default mismatches that need to be reconciled between the code and the database.
• Column `organization_databases.status` has a different default value in the database than in your code.
• Column `permission_profiles.type` has a different default value in the database than in your code.

v1.6.0 — a5519520

• When you drop down the left-hand ladder, you get an option to create organisation when selected it gives a 404 error

v1.4.0 — 2d9cc0ab

v1.3.0 — 2d9cc0ab

v1.2.0 — 2d9cc0ab

• when adding feedback getting this error -

• The release is live! Here's a full summary of what was done:
• *PR #185** — *feat: Real-Time Agent Workspace Console with Human-in-the-Loop Controls*
• **Tag:** `v1.0.168`
• **Release URL:** https://github.com/SaaS-Factory-Live/SaaSFactory.SaaSFactory/releases/tag/v1.0.168

• Everything is done. Here's a summary of what happened:
• *Tag:** `v1.0.167`
• | Area | Change |
• |------|--------|

• The merge is being blocked by a CI lint check failure. Here's the situation:
• This is a significant new feature:
• **Updated `live-preview/page.tsx`** — Swaps in `LivePreviewTabs` in place of the old `ProjectLivePreviewTab`.
• 3. **Once lint passes**, re-trigger this release agent to merge and tag `v1.0.155`.

• Successfully merged PR #174 and published GitHub release v1.0.154.
• *PR:** feat: Automated Onboarding Documentation Generator
• *Merge method:** Squash merge
• *Tag:** v1.0.154

• *Automatically generated from pipeline failure.**
• *Agent:** testing
• *Error Category:** test failure
• *Description:** Tests are failing — the implementation has correctness issues.

• Everything is done. Here's the full summary:
• **Tag:** `v1.0.137`
• **Title:** v1.0.137 — Per-Project AI Cost & Token Usage Dashboard with Budget Alerts
• **URL:** https://github.com/SaaS-Factory-Live/SaaSFactory.SaaSFactory/releases/tag/v1.0.137

• | Error | File |
• |---|---|
• | `TS2307: Cannot find module '@/lib/routers/platform-billing'` | `src/lib/trpc/root.ts:14` |
• | `TS2307: Cannot find module '@/lib/routers/agent-coordination'` | `src/lib/trpc/root.ts:45` |

• Everything is done. Here's a summary of what was accomplished:
• *feat: Automated Agent Memory & Codebase Knowledge Base**
• **Tag:** `v1.0.135`
• **Release URL:** https://github.com/SaaS-Factory-Live/SaaSFactory.SaaSFactory/releases/tag/v1.0.135

• *Automatically generated from pipeline failure.**
• *Agent:** release
• *Error Category:** unknown
• *Description:** Unclassified error — needs manual investigation.

• Successfully merged PR #140 and published release v1.0.126.
• *PR #140** — "feat: Agent Activity Transparency — Diff Viewer, Reasoning Chain & Files Changed tabs"
• Squash-merged into `main`
• *Release v1.0.126** published at: https://github.com/SaaS-Factory-Live/SaaSFactory.SaaSFactory/releases/tag/v1.0.126

• Everything is done. Here's a full summary of what happened:
• 1. **PR #137 Reviewed** — The PR adds a full AI cost visibility dashboard (985 additions, 18 deletions across 7 files).
• | Component | Description |
• |---|---|

• Successfully merged PR #132 and created release v1.0.117.
• *What was merged:**
• `feat/soc2-trust-center` → `main` (squash merge, SHA: c4dc7c9baa541c2284b0445dd0cfff51507fa187)
• *Pre-merge fixes applied to the branch:**

• *Automatically generated from pipeline failure.**
• *Agent:** testing
• *Error Category:** auth error
• *Description:** Authentication/authorization failure — likely a GitHub token issue or expired credentials.

• Successfully merged PR #131 and published GitHub release v1.0.115.
• *PR #131 — feat: interactive live sandbox demo on landing page**
• ✅ Squash-merged into `main`
• ✅ Release tag `v1.0.115` created

• *Investigation findings:**
• Multiple CI runs dispatched and monitored; all conclude `failure` for the same reason
• All new code reviewed — fleet router, dashboard component, page, and tests are clean and production-ready

• *CI failure analysis:**
• ❌ `tests/inngest/seo-audit-cron.test.ts` — SEO audit cron, unrelated to product status pages
• | Test File | Failure Reason |
• |---|---|

• Looking at the CI output carefully, the **failing tests are**:
• `data-export-fulfillment-cron.test.ts` — unrelated to this PR
• `seo-audit-cron.test.ts` — unrelated
• `analytics.test.ts` — unrelated

• The release is live. Here's a full summary of what was done:
• **Tag:** `v1.0.109`
• **URL:** https://github.com/SaaS-Factory-Live/SaaSFactory.SaaSFactory/releases/tag/v1.0.109
• | Component | What It Does |

• Here is a full summary of the situation:
• *`fix(TPL-M01): add responsive grid reference pattern to dashboard pages`**
• This is a **low-risk, comment-only fix** (plus housekeeping) across 16 files:
• | Area | Change |

• Category: navigation
• File: src/components/breadcrumb-header.tsx

• Category: usability
• File: src/components/support-tickets-dashboard.tsx

• Category: performance
• File: src/app/dashboard/layout.tsx

• Category: usability
• File: src/components/sign-up-form.tsx

• Category: usability
• File: src/components/project-features-tab.tsx

• Category: content
• File: src/app/layout.tsx

• Category: usability
• File: src/components/settings/settings-page-client.tsx

• Category: navigation
• File: src/components/account-sidebar.tsx

• Category: navigation
• File: src/components/app-sidebar.tsx

• Category: navigation
• File: src/components/product-sidebar.tsx

• Category: accessibility
• File: src/components/beast-mode-tab.tsx

• Category: usability
• File: src/components/product-header.tsx

• Category: usability
• File: src/components/settings/settings-page-client.tsx

• Category: navigation
• File: src/components/live-pipeline-detail.tsx

• Category: consistency
• File: src/components/empty-state.tsx

• Category: usability
• File: src/components/notification-bell.tsx

• Category: content
• File: src/app/sign-in/[[...sign-in]]/page.tsx

• Category: usability
• File: src/components/project-features-tab.tsx

• Category: navigation
• File: src/components/app-sidebar.tsx

• Category: navigation
• File: src/components/account-sidebar.tsx

• Category: visual-hierarchy
• File: src/components/dashboard-content.tsx

• Category: consistency
• File: src/components/product-header.tsx

• Category: layout
• File: src/components/live-pipeline-detail.tsx

• Category: consistency
• File: src/components/create-project-form.tsx

• Category: responsive
• File: src/components/settings/settings-page-client.tsx

• Category: usability
• File: src/components/onboarding-wizard.tsx