Hermes 284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Initial import of AlgaPSA codebase from PSA server
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz

Source: /opt/alga-psa on psa.joliet.tech
2026-06-22 16:12:17 -05:00

179 lines
5.2 KiB
JSON

[
{
"id": "F001",
"description": "Adopt client/contact-owned inbound routing model and de-scope provider-level sender-rule table approach",
"implemented": true,
"prdRefs": [
"Summary",
"Data / API / Integrations > Approach Options"
]
},
{
"id": "F002",
"description": "Add client-level inbound destination reference (`clients.inbound_ticket_defaults_id` or equivalent persisted field)",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Data / API / Integrations > Proposed Data Model"
]
},
{
"id": "F003",
"description": "Add contact-level inbound destination override reference (`contacts.inbound_ticket_defaults_id` or equivalent persisted field)",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Data / API / Integrations > Proposed Data Model"
]
},
{
"id": "F004",
"description": "Add indexes and migration safety for new client/contact destination fields",
"implemented": true,
"prdRefs": [
"Data / API / Integrations > Proposed Data Model",
"Rollout / Migration"
]
},
{
"id": "F005",
"description": "Implement shared effective-destination resolver with precedence: contact override -> client default -> provider default",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Acceptance Criteria (Definition of Done)"
]
},
{
"id": "F006",
"description": "Resolve domain-matched client destination via existing `client_inbound_email_domains` when exact contact is absent",
"implemented": true,
"prdRefs": [
"Users and Primary Flows",
"Requirements > Functional Requirements"
]
},
{
"id": "F007",
"description": "Validate resolved destination defaults are tenant-owned and active; fallback to provider default when invalid",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Observability"
]
},
{
"id": "F008",
"description": "Apply effective destination resolution in `processInboundEmailInApp` new-ticket creation path",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Resolution Integration Points"
]
},
{
"id": "F009",
"description": "Apply the same resolution logic in workflow runtime (`resolve_inbound_ticket_context` + create path) for parity",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Resolution Integration Points"
]
},
{
"id": "F010",
"description": "Keep reply-token and thread-header existing-ticket flows unchanged",
"implemented": true,
"prdRefs": [
"Non-goals",
"Requirements > Functional Requirements"
]
},
{
"id": "F011",
"description": "Preserve exact-contact and domain-to-client matching behavior while introducing destination routing",
"implemented": true,
"prdRefs": [
"Goals",
"Requirements > Functional Requirements"
]
},
{
"id": "F012",
"description": "Add server actions/API support for reading/updating client inbound destination with existing client permissions",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Security / Permissions"
]
},
{
"id": "F013",
"description": "Add server actions/API support for reading/updating contact inbound destination override with existing contact permissions",
"implemented": true,
"prdRefs": [
"Requirements > Functional Requirements",
"Security / Permissions"
]
},
{
"id": "F014",
"description": "Update `ClientDetails` UI to manage client inbound destination",
"implemented": true,
"prdRefs": [
"UX / UI Notes",
"Resolution Integration Points"
]
},
{
"id": "F015",
"description": "Update contact UI to manage optional contact inbound destination override",
"implemented": true,
"prdRefs": [
"UX / UI Notes",
"Resolution Integration Points"
]
},
{
"id": "F016",
"description": "Add precedence helper text in client/contact UIs and ensure clear fallback semantics",
"implemented": true,
"prdRefs": [
"UX / UI Notes"
]
},
{
"id": "F017",
"description": "Add structured logging for destination resolution source and fallback reasons",
"implemented": true,
"prdRefs": [
"Observability"
]
},
{
"id": "F018",
"description": "Add integration coverage for in-app inbound routing across contact override, client default, domain, and provider fallback",
"implemented": true,
"prdRefs": [
"Acceptance Criteria (Definition of Done)"
]
},
{
"id": "F019",
"description": "Add integration coverage for workflow-runtime parity with in-app destination resolution",
"implemented": true,
"prdRefs": [
"Acceptance Criteria (Definition of Done)"
]
},
{
"id": "F020",
"description": "Add regression coverage for idempotency/dedupe and unchanged reply behavior",
"implemented": true,
"prdRefs": [
"Non-functional Requirements",
"Acceptance Criteria (Definition of Done)"
]
}
]