OUT-4015: gate Client Home Actions dropdown on app install published status

[SandipBajracharya]

Changes

• Add an AppInstallStatus enum (draft / published) and expose the new status field on AppInstallsDataSchema — surfaced on the /installs endpoint by POR-21837.
• Gate InstalledAppsService.getActionableInstalls() on status !== AppInstallStatus.DRAFT, so app-builder draft apps no longer appear in the Client Home "Your Actions" dropdown. This is the single choke point feeding both the client-facing card and the editor's Actions toggle list, so drafts drop off both surfaces.
• Denylist semantics: only an explicit draft status is hidden; missing/null status is treated as non-draft and shown (avoids regressing installs without a status).

Testing Criteria

• Loom walkthrough — pending
• Added tests/unit/installed-apps.service.test.ts covering:
  • draft installs are hidden and their notification-settings endpoint is never called
  • a published install with a registered action label is shown
  • only explicit drafts are hidden — undefined/null status is shown (denylist)
  • a published install without a complete action label is excluded
• pnpm vitest run tests/unit → 28 passed · pnpm typecheck clean · pnpm lint clean.

Notes

• Depends on POR-21837 (backend, merged) which adds status to the app-install model / installs endpoint. Frontend should not deploy ahead of that backend change.
• Worth confirming with backend/QA that status is populated for non-app-builder installs (legacy marketplace/native Studio apps) as well, not just newly created app-builder installs.

Impact & Surface Area of Change

• Affects only the "Your Actions" list on Client Home (client preview card + editor Actions toggle), both fed by GET /api/installed-apps. Built-in rows (Invoices, Contracts, Tasks, Forms) are unaffected.
• status is parsed via a strict z.enum on the whole installs array — a future third status value would fail the list parse; only draft/published exist today.

[linear-code]

OUT-4015

[greptile-apps]

Greptile Summary

Adds the app-install publication status to the frontend schema and excludes explicit app-builder drafts from actionable installs before notification settings are fetched.

• Defines AppInstallStatus and parses nullable or missing statuses.
• Applies denylist filtering at the shared actionable-installs service.
• Adds unit coverage for draft, published, nullish-status, and incomplete-label cases.

Confidence Score: 5/5

The PR appears safe to merge, with the new draft gate consistently applied at the shared actionable-installs boundary.

The schema accepts the documented current statuses and preserves legacy nullish values, while the combined lifecycle checks exclude drafts before notification settings are fetched; the added tests exercise the principal filtering paths.

Important Files Changed

Filename	Overview
src/features/installed-apps/lib/installed-apps.service.ts	Adds an explicit draft-status exclusion to the existing actionable-install filter before per-install notification requests.
src/lib/assembly/types.ts	Defines the two supported install lifecycle statuses and adds a nullish status field to the response schema.
tests/unit/installed-apps.service.test.ts	Covers draft exclusion, published inclusion, denylist handling of nullish statuses, request fan-out, and action-label validation.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    A[GET installs] --> B[Parse install status]
    B --> C{Eligible and not draft?}
    C -- No --> D[Exclude install]
    C -- Yes --> E[Fetch notification settings]
    E --> F{Complete action label?}
    F -- No --> D
    F -- Yes --> G[Return in Your Actions]

Loading

_{Reviews (1): Last reviewed commit: "test(OUT-4015): cover non-draft install ..." | Re-trigger Greptile}

[priosshrsth]

maybe install.status === AppINstallStatus.PUBLISHED is better?

[priosshrsth]

lgtm