Mattsson
bb855d2ddc
* feat(branding): implement dynamic branding in service worker and reports * feat(auth): enhance API key scopes and add bookkeeping write scope - Updated transaction write scope description to include additional tools. - Enhanced reports read scope description to reflect new functionality. - Introduced bookkeeping write scope with relevant description. - Updated SCOPE_GROUPS to include bookkeeping domain. - Modified TOOL_SCOPE_MAP to include new bookkeeping operations. - Updated validateApiKey function to return api_key_id and api_key_name for better actor attribution. feat(tests): add unit tests for MCP resource registry - Created tests for data resources to ensure all required fields are present. - Added tests for resource query parsing and retrieval. feat(resources): implement MCP resources for company and accounting data - Added capabilities resource to expose API key capabilities based on granted scopes. - Implemented chart of accounts resource to retrieve active BAS chart. - Created company current resource to fetch active company details. - Developed active fiscal period resource to check posting eligibility. - Implemented recent activity resource to fetch latest journal entries, invoices, and transactions. - Added VAT treatments resource to provide available VAT rates per customer type. feat(pending-operations): introduce risk tiers for operations - Added risk level classification for pending operations to determine auto-commit eligibility. - Implemented functions to classify operation risk levels and identify high-risk operations. feat(migrations): add actor model and risk tier to pending operations - Updated pending_operations table to include actor type and risk level columns. - Enhanced audit_log to mirror actor information for compliance. - Modified validate_and_increment_api_key function to return actor details. - Expanded operation types in pending_operations to include new high-risk operations. * feat: add auto-commit functionality for low-risk pending operations - Implemented shouldAutoCommit function to determine eligibility for auto-commit based on operation type, actor type, and company settings. - Created commitPendingOperation function to handle execution of pending operations with consistent status updates. - Added tests for shouldAutoCommit to cover various scenarios including high-risk operations, user actors, company opt-in status, and monetary thresholds. - Introduced new columns in company_settings for agent_auto_commit_enabled and agent_auto_commit_max_amount to allow companies to opt-in for auto-commit functionality. - Added SQL migration to update the database schema for new auto-commit settings. * feat(idempotency): implement idempotency key handling for safe retries and cleanup * feat: expand API key scopes and pending operations for bookkeeping - Added 'suppliers:write' scope to API key scopes for supplier invoice management. - Updated SCOPE_GROUPS to include the new 'suppliers:write' scope. - Introduced new pending operation types for bookkeeping: close_period, lock_period, run_year_end, set_opening_balances, run_currency_revaluation, explain_voucher_gap, uncategorize_transaction, approve_supplier_invoice, credit_supplier_invoice, and convert_invoice. - Implemented corresponding commit functions for the new operations in the pending operations module. - Enhanced PendingOperation type to include actor model and risk level attributes. - Added tests for new functionality, ensuring proper behavior and constraints in the database. * feat: implement unlockPeriod functionality and related tests * feat: add agent auto-commit settings and related functionality * feat: add attention resource with comprehensive summary of outstanding tasks * feat: enhance pending operations with 'committing' status and immutability checks, improve idempotency handling, and add original voucher reference for credit notes
54 lines
2.0 KiB
TypeScript
54 lines
2.0 KiB
TypeScript
import type { McpResource } from './types'
|
|
|
|
export const periodActiveResource: McpResource = {
|
|
uri: 'gnubok://period/active',
|
|
name: 'Active Fiscal Period',
|
|
description: 'The fiscal period that the current date falls within: lock state, opening-balance status, retention deadline. Use to check whether new entries can be posted.',
|
|
mimeType: 'application/json',
|
|
read: async ({ supabase, companyId }) => {
|
|
const today = new Date().toISOString().slice(0, 10)
|
|
|
|
const { data: active, error: activeError } = await supabase
|
|
.from('fiscal_periods')
|
|
.select('id, name, period_start, period_end, is_closed, closed_at, locked_at, opening_balances_set, retention_expires_at, opening_balance_entry_id, closing_entry_id, previous_period_id')
|
|
.eq('company_id', companyId)
|
|
.lte('period_start', today)
|
|
.gte('period_end', today)
|
|
.maybeSingle()
|
|
|
|
if (activeError && activeError.code !== 'PGRST116') {
|
|
throw new Error(`Failed to read active period: ${activeError.message}`)
|
|
}
|
|
|
|
const { data: settings } = await supabase
|
|
.from('company_settings')
|
|
.select('bookkeeping_locked_through, auto_lock_period_days')
|
|
.eq('company_id', companyId)
|
|
.maybeSingle()
|
|
|
|
const periodLockedAt = active?.locked_at ?? null
|
|
const isClosed = active?.is_closed ?? null
|
|
const companyLockDate = settings?.bookkeeping_locked_through ?? null
|
|
|
|
const canPostEntries = active
|
|
? !isClosed && !periodLockedAt
|
|
: false
|
|
|
|
return {
|
|
active_period: active ?? null,
|
|
company_lock: {
|
|
bookkeeping_locked_through: companyLockDate,
|
|
auto_lock_period_days: settings?.auto_lock_period_days ?? null,
|
|
},
|
|
can_post_entries: canPostEntries,
|
|
reason_blocked: !active
|
|
? 'No fiscal period covers today\'s date'
|
|
: isClosed
|
|
? 'Active period is closed (status: stängd)'
|
|
: periodLockedAt
|
|
? 'Active period is locked (status: låst)'
|
|
: null,
|
|
}
|
|
},
|
|
}
|