b68c082ef5
* fix(bank-sync): cron backfills the gap since the last successful sync The daily incremental sync always asked the bank for the last 7 days. Any pause longer than that (a lapsed subscription paid again, a consent renewed after expiry, an outage) silently lost the days in between: the connection came back, looked healthy, and the missing transactions never arrived. The lookback now widens to cover the gap since last_synced_at plus one day of overlap, capped at the 90-day PSD2 limit, and a gap of a month or more asks for strategy=longest like the manual sync route does. Dedup via external_id makes the overlap harmless. First syncs keep their 90-day path. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdcDV7CngLkWUvfKSsxFhS * feat(bank-sync): chip warns seven days before a bank consent expires The transactions-page chip only reacted once a connection was already dead (expired/error) or had gone stale. A consent that is about to end looked healthy until the morning it stopped syncing. New "expiring" state when a live connection's consent_expires is within seven days, the same threshold as the consent-expiry email in the sync cron. Precedence: attention, expiring, stale, healthy. getChipState moves to lib/transactions/bank-sync-chip-state.ts so the precedence is unit-tested; the component keeps the rendering only. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdcDV7CngLkWUvfKSsxFhS * feat(bank-sync): chip says paused when the subscription lapsed The daily cron filters connections by the bank_sync capability, so a company whose trial or subscription ended keeps status=active rows with a frozen last_synced_at. The chip read that as "stale, check the connection", which sends the user to re-authorise a connection that is perfectly alive. 56 of 191 active connections on prod were in this state on 2026-09-01. New "paused" state, ranked above everything else, when the company lacks bank_sync: hosted points at billing, self-host at the connector key, the same split BankSyncNowButton already makes. getChipState takes an options object so the clock stays out of render (react-hooks/purity). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdcDV7CngLkWUvfKSsxFhS * feat(api): agent-triggerable bank sync in v1 and MCP Closes the first wish in the F2 report: an integration could read bank data but never refresh it. New POST /api/v1/companies/{id}/bank-connections/ {connectionId}/sync and MCP gnubok_sync_bank, both on a shared runner (extensions/general/enable-banking/lib/trigger-sync.ts). Cost is bounded structurally, not by policy: the window is never caller-controlled (the cron's gap-aware 7 to 90 day lookback), a connection synced within 15 minutes answers BANK_SYNC_COOLDOWN with next_allowed_at (429 + Retry-After on v1; synced=false in-band on MCP so the agent reads on instead of retrying), and a failing connection is throttled per process by attempt time. A dead session is flipped to expired with a remediation that hands the user the connect link: no API call revives a consent. Gated on bank_sync like gnubok_connect_bank; scope transactions:write. Registry, scope map, load-routes, spec snapshot and the generated accounted-api skill updated; five BANK_SYNC_* / BANK_SESSION_EXPIRED codes added to the structured-error registry. The web Synka-nu route is left as is (see DECISIONS.md). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdcDV7CngLkWUvfKSsxFhS * test(bank-sync): use the options object in the remaining chip-state calls Four multi-line calls still passed the clock positionally after getChipState moved to an options object; tsc flagged them (vitest did not, the extra argument was ignored at runtime). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdcDV7CngLkWUvfKSsxFhS * fix(api): address skeptic findings on the agent-triggered bank sync Three refutations from the pre-publish skeptic pass: 1. Core imported the extension. The v1 sync route pulled the runner straight from @/extensions, which the core-build gate rejects and which left a live bank endpoint on zero-extension builds. The route now resolves it through the registry's services channel against a contract in lib/bank-sync/trigger-sync-contract.ts (same pattern as the Skatteverket read service) and answers EXTENSION_DISABLED when the extension is absent. 2. The idempotency cache stored the handler-level 429. A same-key retry after Retry-After, which is the documented retry, replayed the stale cooldown as a 400 for the cache's 24-hour TTL. withApiV1 no longer caches 429 responses; regression test added. The endpoint's pitfall no longer claims Idempotency-Key is mandatory (it was never enforced). 3. Two cron tests read the clock twice and failed whenever a millisecond passed between the reads. They now pin the clock with fake timers. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QdcDV7CngLkWUvfKSsxFhS * fix(bank-sync): durable cooldown lease and review wording Resolves the PR #2165 review findings in one pass. Superagent P1: the attempt throttle was a process-local Map, so two agent calls on different serverless instances (or a retry after a cold start on a failing connection) could each bill an Enable Banking call, contradicting the one-sync-per-15-minutes promise. New bank_connections.sync_lease_until (migration 20260902150000), claimed with one conditional UPDATE before the bank is called; Postgres row locking makes exactly one claimer win, the rest answer BANK_SYNC_COOLDOWN. The lease stays for the full window on success and failure. Tests cover the claim order, a failed attempt seen from a second instance, a lost race, and an expired lease. CodeRabbit: the =1 plural branch now reads "in 1 day" / "om 1 dag" (daysUntilConsentExpiry rounds a partial day up, so "tomorrow" could be today); the cooldown pitfall on the v1 endpoint, the MCP description and the in-band cooldown instruction now say a cooldown can follow a failed attempt and tell the agent to compare last_synced_at before deciding. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0125TMQQBjBBZG9YxP7wQWub * fix(bank-sync): lease claim as a literal filter for the schema guard CI's no-phantom-columns guard counts runtime-built query expressions and its ceiling is exact; the templated `.or('sync_lease_until.is.null,...')` claim added one. The column now defaults to epoch (NOT NULL), so "never claimed" is just "expired long ago" and the atomic claim is a single literal `.lte('sync_lease_until', now)` the guard can check. Migration is unshipped (same PR), so it is edited in place. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0125TMQQBjBBZG9YxP7wQWub * fix(bank-sync): runner verifies company membership before the lease Superagent (round 3): the MCP path reached the shared runner without a membership check of its own. Both callers do enforce it upstream (withApiV1's company resolution and resolveMcpCompanyContext in the MCP dispatcher), but the runner writes transactions and bills a bank call, so it now checks company_members itself, before the cooldown and the lease claim, and answers NOT_FOUND for a non-member. The viewer check that was buried inside the sync block moves up with it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0125TMQQBjBBZG9YxP7wQWub --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
181 lines
8.9 KiB
TypeScript
181 lines
8.9 KiB
TypeScript
/**
|
|
* Capability keys: the single namespace behind the SaaS paywall AND the
|
|
* per-tenant modularity / marketplace vision. Each key names one gateable
|
|
* feature; a company "has" it when an unexpired capability_grant exists
|
|
* (entitlement) and it isn't explicitly disabled (enablement).
|
|
*
|
|
* These keys are a STABLE CONTRACT: grant rows, the future marketplace catalog,
|
|
* and per-tenant module toggles all reference them. Add keys; never rename one.
|
|
*/
|
|
export const CAPABILITY = {
|
|
/** AI assistant chat, onboarding composer, and document field extraction (Anthropic/Bedrock). */
|
|
ai: 'ai',
|
|
/** Bank sync / PSD2 (Enable Banking). Freeze-and-retain: tokens are NOT revoked on downgrade. */
|
|
bank_sync: 'bank_sync',
|
|
/** Skatteverket filing/sync (VAT, AGI, skattekonto) via BankID. */
|
|
skatteverket: 'skatteverket',
|
|
/** Outbound transactional email: invoices, reminders, payslips (Resend). Auth/account email is never gated. */
|
|
email_send: 'email_send',
|
|
/** Org-number lookup / enrichment (TIC). NOT gated: identity/lookup is always free. */
|
|
org_lookup: 'org_lookup',
|
|
/** EU VAT-number validation (VIES). NOT gated: identity/lookup is always free. */
|
|
vat_validation: 'vat_validation',
|
|
/** Riksbanken FX auto-fetch. NOT gated at launch (kept free); manual rate entry is always allowed. */
|
|
currency_rates: 'currency_rates',
|
|
/** Cloud backup to Google Drive. NOT gated at launch (kept free: never hold a customer's data hostage). */
|
|
cloud_backup: 'cloud_backup',
|
|
/** Migration import from other systems (Fortnox/Visma/Bokio/BL/Briox). Kept open so new payers can migrate IN. */
|
|
migration: 'migration',
|
|
/** Bolagsverket iXBRL årsredovisning filing. Reserved (extension not yet enabled). */
|
|
bolagsverket: 'bolagsverket',
|
|
/** Stripe Connect: auto payment links on invoices + payment/payout sync. */
|
|
stripe_payments: 'stripe_payments',
|
|
/** WooCommerce store sync: orders/refunds imported as a transaction feed. */
|
|
woocommerce_sync: 'woocommerce_sync',
|
|
/** Shopify store sync: orders/refunds imported as a transaction feed. */
|
|
shopify_sync: 'shopify_sync',
|
|
/**
|
|
* Multiple people working in one company. Without it only the OWNER can
|
|
* enter the company: every other membership goes dormant (never deleted)
|
|
* after a 20-day post-lapse grace window, and new invites are blocked.
|
|
* See lib/entitlements/multi-user.ts for the derived entitled/grace/frozen
|
|
* state; company_capability_config does NOT apply to this key (it gates
|
|
* member access, not a feature surface).
|
|
*/
|
|
multi_user: 'multi_user',
|
|
/**
|
|
* Invoice email from the company's own verified sending domain (Resend
|
|
* domain per company). Opt-in: granted manually per company, NOT part of
|
|
* PAID_CAPABILITIES, so it is never trial-seeded or written by the Stripe
|
|
* subscription sync. Without the grant the settings section is hidden and
|
|
* mail keeps leaving from the platform sender.
|
|
*/
|
|
custom_sender_domain: 'custom_sender_domain',
|
|
} as const
|
|
|
|
export type CapabilityKey = (typeof CAPABILITY)[keyof typeof CAPABILITY]
|
|
|
|
/**
|
|
* The set actually withheld from non-payers (manual tier) at the 2026-07-07
|
|
* cutover. Founder decision (2026-06-28): gate the high-value recurring external
|
|
* services only.
|
|
*
|
|
* KEPT FREE on purpose:
|
|
* - identity & lookup: TIC org_lookup, VIES vat_validation, BankID login:
|
|
* they aid onboarding/data quality; gating them is friction in the wrong place.
|
|
* - currency_rates (FX auto-fetch) and cloud_backup.
|
|
* Internal bookkeeping is always fully usable on the manual tier.
|
|
*
|
|
* NOTE: bank_sync and skatteverket stay PAID even though their flows use BankID
|
|
* as an auth step: what's charged for is the bank data sync and the VAT/AGI
|
|
* filing service, not the identity check.
|
|
*/
|
|
export const PAID_CAPABILITIES: readonly CapabilityKey[] = [
|
|
CAPABILITY.ai,
|
|
CAPABILITY.bank_sync,
|
|
CAPABILITY.skatteverket,
|
|
CAPABILITY.email_send,
|
|
CAPABILITY.stripe_payments,
|
|
CAPABILITY.woocommerce_sync,
|
|
CAPABILITY.shopify_sync,
|
|
// Founder decision (2026-09-01): multiple users per company is paid.
|
|
// Trial-seeded and Stripe-synced like the rest; enforcement is the
|
|
// owner-only dormancy rule in lib/entitlements/multi-user.ts.
|
|
CAPABILITY.multi_user,
|
|
] as const
|
|
|
|
/**
|
|
* Capabilities that a SELF-HOSTED instance cannot provide on its own because
|
|
* they run on services Accounted operates (the PSD2/AISP bank connection,
|
|
* the Skatteverket API client, the TIC lookup contract, the migration
|
|
* gateway). On hosted these follow the normal paywall (bank_sync and
|
|
* skatteverket are in PAID_CAPABILITIES; org_lookup and migration are free).
|
|
* On a self-host every other capability is always on, and exactly these fall
|
|
* through to the grant lookup: the hourly connector sync writes
|
|
* `source = 'connector'` grants for them from the instance's connector key
|
|
* (lib/connect/instance, arriving with the connector-keys stack PR #1748).
|
|
* A self-host serving an upstream from its OWN credentials holds that
|
|
* capability outright (see own-credentials.ts): only keyless-and-credential-
|
|
* less connector capabilities are withheld. Deliberately NOT part of
|
|
* PAID_CAPABILITIES and NOT seeded by the trial trigger: hosted companies
|
|
* never receive connector grants.
|
|
*/
|
|
export const CONNECTOR_CAPABILITIES: readonly CapabilityKey[] = [
|
|
CAPABILITY.bank_sync,
|
|
CAPABILITY.skatteverket,
|
|
CAPABILITY.org_lookup,
|
|
CAPABILITY.migration,
|
|
] as const
|
|
|
|
export function isConnectorCapability(key: CapabilityKey): boolean {
|
|
return (CONNECTOR_CAPABILITIES as readonly string[]).includes(key)
|
|
}
|
|
|
|
/**
|
|
* Paid MCP tools → required capability. The MCP/agent path is a paid chokepoint
|
|
* just like the HTTP routes, so the dispatcher gates these the same way it gates
|
|
* API-key scope (see mcp-server `tools/call`). External-service WRITE tools
|
|
* appear here: send_invoice (email) and the two Skatteverket submissions. The
|
|
* read/local SKV tools (generate_agi, vat_declaration_validate/status, agi_status)
|
|
* stay free: the §4 carve-out forbids blocking a statutory filing obligation.
|
|
*
|
|
* The document upload tools invoke AI (Bedrock document OCR via
|
|
* extractInvoiceFields), so they are gated on CAPABILITY.ai: the same paywall
|
|
* the HTTP inbox upload/attach/retry paths enforce. Without these entries a
|
|
* free-tier API key could trigger paid AI extraction. bank_sync gates
|
|
* gnubok_connect_bank (the onboarding connect link) and gnubok_sync_bank
|
|
* (the agent-triggered PSD2 sync, a paid Enable Banking call per account).
|
|
*/
|
|
export const MCP_TOOL_CAPABILITY_MAP: Readonly<Partial<Record<string, CapabilityKey>>> = {
|
|
gnubok_send_invoice: CAPABILITY.email_send,
|
|
gnubok_vat_declaration_submit: CAPABILITY.skatteverket,
|
|
gnubok_agi_submit: CAPABILITY.skatteverket,
|
|
// Onboarding connect-link tools (issue #1814): gated like the links' targets.
|
|
gnubok_connect_bank: CAPABILITY.bank_sync,
|
|
// Agent-triggered PSD2 sync: a paid Enable Banking call per account.
|
|
gnubok_sync_bank: CAPABILITY.bank_sync,
|
|
gnubok_connect_skatteverket: CAPABILITY.skatteverket,
|
|
// AI document OCR (Bedrock): the inbox's paid extraction, reachable via MCP.
|
|
gnubok_create_document_upload: CAPABILITY.ai,
|
|
gnubok_complete_document_upload: CAPABILITY.ai,
|
|
gnubok_upload_document: CAPABILITY.ai,
|
|
} as const
|
|
|
|
/**
|
|
* Paid pending-operation types → required capability. Keyed by
|
|
* `pending_operations.operation_type`. This is the commit-time twin of
|
|
* MCP_TOOL_CAPABILITY_MAP: it gates the actual external-service call inside
|
|
* commitPendingOperation, so an operation staged during the trial cannot be
|
|
* committed once the grant has expired, regardless of caller (MCP approve tool
|
|
* or the UI approval path). Keep the values in sync with MCP_TOOL_CAPABILITY_MAP.
|
|
*/
|
|
export const PAID_OPERATION_CAPABILITY_MAP: Readonly<Partial<Record<string, CapabilityKey>>> = {
|
|
send_invoice: CAPABILITY.email_send,
|
|
submit_vat_declaration: CAPABILITY.skatteverket,
|
|
submit_agi: CAPABILITY.skatteverket,
|
|
} as const
|
|
|
|
/**
|
|
* Extension workspace → required capability, keyed by `sector/slug`. This is the
|
|
* page/nav twin of the API-route gates: an extension whose entire value is a
|
|
* paid service should not just 403 its writes but be hidden from the sidebar and
|
|
* blocked at the page so a non-payer never lands on a dead workspace.
|
|
*
|
|
* invoice-inbox is fully gated on `ai`: its reason to exist is the AI field
|
|
* extraction (extractInvoiceFields / gnubok_upload_document), already the paid
|
|
* chokepoint on every other surface (HTTP upload/attach/retry, the MCP tool).
|
|
* Both the sidebar item and the /e/[sector]/[slug] page read this map so the two
|
|
* surfaces can never drift apart.
|
|
*/
|
|
export const EXTENSION_REQUIRED_CAPABILITY: Readonly<Partial<Record<string, CapabilityKey>>> = {
|
|
'general/invoice-inbox': CAPABILITY.ai,
|
|
} as const
|
|
|
|
/** Which paid capability (if any) an extension workspace requires to be usable. */
|
|
export function requiredCapabilityForExtension(
|
|
sector: string,
|
|
slug: string,
|
|
): CapabilityKey | undefined {
|
|
return EXTENSION_REQUIRED_CAPABILITY[`${sector}/${slug}`]
|
|
}
|