7 Commits

Include renames

Author	SHA1	Message	Date
Brandon	25a9011f14	feat(ai): analytical tool-set upgrade for the builtin assistant (#3064) ... * fix(assistant): survive tool failures with error and hint results instead of aborting the turn A tool exception used to raise FunctionExecutionError out of the responder loop, turning the whole turn into a generic chat error banner. An unknown tool name was worse: the rescue block itself crashed (fn.name on nil). Tool failures now come back to the model as data ({error, hint}) so the conversation survives and the model can retry once with corrected arguments. The catch-all branch logs and tells the model not to retry. FunctionExecutionError remains defined for API compatibility. * fix(assistant): strict schemas declare every property as required get_categories and get_tags declared an optional page property while inheriting strict mode, which is invalid under strict function calling (every property must be listed in required). Both now opt out of strict mode like every other paginated tool, and gain a page_size param (1..100) while being touched. A registry-walking test asserts the invariant for every current and future tool, preview tools included. * fix(assistant): HistoryTrimmer always keeps the newest turn Trimming iterates newest-first and stopped at the first group over budget. When the newest group alone exceeded the budget, everything was dropped, including the user message the model was being asked to answer, and the provider received only the system prompt. The newest group now always survives. * perf(assistant): compact AI time series and make account history opt-in get_accounts shipped a 5-year monthly series for every account on every call, roughly 60 formatted money strings per account, which dominates the tool payload for multi-account families and swamps small self-hosted context windows. The series is now opt-in (include_balance_series) and bounded by a named period (series_period, default last_365_days). to_ai_time_series states the currency once and emits numeric values instead of formatting every point; the system prompt already tells the model how to render currency. get_accounts also now returns account ids (they are what other tools accept as account_ids filters) and respects the visible scope, so hidden accounts no longer leak into responses. * refactor(assistant): id and name filters replace user-data enums in get_transactions The schema inlined every account, category, merchant, and tag name as enum values on every request. That grows without bound with family data, defeats provider prompt caching (definitions change whenever a name does), and is the pattern that made empty-enum pruning necessary in the first place. Filters are now plain string arrays documented as exact names from the sibling get_* tools, which Transaction::Search already resolves server-side, plus an account_ids UUID filter. New params: page_size (1..100), sort_by amount, types (income/expense/transfer, the way to exclude transfers), and statuses (pending/confirmed). The three now-unused enum helpers are removed from the base class; family_tag_names stays for update_tag, which still identifies tags by name. * feat(assistant): add get_merchants and get_recurring_transactions Merchants were unreachable: names appeared nowhere and update_transaction's merchant_id had no source of ids, making it unusable. get_merchants lists id, exact name, and source, scoped through available_merchants_for so merchants seen only in accounts hidden from the user never leak. Recurring transactions had a model, an Upcoming view, and no assistant reach. get_recurring_transactions lists detected and manual recurring items (status filter defaulting to active, optional upcoming_within_days window) with per-currency totals of active non-transfer items, answering subscription and upcoming-bill questions directly instead of via transaction paging. * feat(assistant): flexible periods on get_balance_sheet and trends on get_income_statement get_balance_sheet was hard-wired to five years of monthly history with no parameters, although Period supports arbitrary ranges and the chart builder takes any interval. It now accepts a named period or custom dates plus an interval, with a 400-point cap so a day-granularity request over a decade returns an error instead of a giant series. The default call is byte-compatible with the old shape. The balance sheet object is also memoized; it was being constructed four times per call. get_income_statement gains the analysis surface the assistant lacked: group_by month for a monthly income/expenses/net series (capped at 36 buckets), compare_previous_period for an equal-length prior window with absolute and percent deltas, and account_ids to scope totals to specific accounts via IncomeStatement#totals_for. Category breakdowns are family-wide by construction, so the account-filtered view omits them and says why. Unknown or inaccessible account ids come back as a soft failure naming the ids so the model can correct itself. * feat(assistant): preview reads for insights and valuations The Insights feed is generated nightly with pre-computed numbers, and the chat assistant could not read a word of it. get_insights returns the visible feed (type filter, acknowledged toggle, limit) without marking anything read; an assistant read is not the user viewing the feed. It sits in PREVIEW_FUNCTION_CLASSES because the feature itself is preview-gated, which also keeps it off the default /mcp surface. record_valuation was write-only: an agent recording provenance-cited valuations had no way to audit what it wrote or find dates already carrying a value. get_valuations lists valuation entries newest first with kind and the citation notes, scoped to accessible visible accounts. * feat(assistant): cache-stable system prompt with session context The prompt interpolated currency mid-text and the date near the end, so no two requests shared a cacheable prefix, and it told the model nothing about the family: not one account name, not a single category. Models opened most conversations blind, either wandering through tools or answering without data. The prompt is now STATIC_INSTRUCTIONS, a frozen constant that is byte-identical for every request (providers discount an exactly-repeated prefix; tool definitions are also stable now that schemas carry no user data), followed by a trailing Session context block holding everything volatile: date, date format, currency details, an account roster with balances, and category names. The static half gains a request-classification rule (CHAT / LOOKUP / ANALYSIS), a reuse-what-you-have rule with an explicit re-fetch carve-out, specific-tool preference, and the error/hint retry-once rule that pairs with the tool soft-fail contract. Context stays cheap by construction: the roster collapses to per-type counts beyond 25 accounts, categories to a count beyond 60 names, and both collapse whenever the configured context window is under 4096 (the self-hosted default is 2048), via the new Assistant::TokenBudget helper. Intro chats are untouched. * feat(assistant): raise tool-round cap to 8 with a no-tools grace turn; instructions-aware history budget Five rounds was tight for a tool surface that now supports real analysis chains, and hitting the cap raised ToolCallLimitError, which surfaced to the user as a dead chat with an error banner. The default is now eight rounds (env override unchanged), and on the final permitted round the follow-up request offers no tools, so the model must answer in text with whatever it gathered. The limit error remains as a defensive backstop. The generic-path history budget reserved a flat 256 tokens for a system prompt that already estimates well past that; the trimmer now budgets against the actual instructions when available. LLM_MAX_RESPONSE_TOKENS was reserved in budget math but never sent to the provider. It is now sent (max_tokens on chat completions, max_output_tokens on the Responses API) only when explicitly configured via ENV or a stored Setting; stock installs keep today's uncapped behavior. * test(evals): chat golden v2 exercising the real prompt and registry The eval runner scored a fiction: hardcoded instructions and four fake permissive tool schemas, so a prompt or registry regression could sail through green. It now runs STATIC_INSTRUCTIONS plus a fixed synthetic session context and builds definitions from Assistant.function_classes against a reference user (classes whose schema cannot build are skipped with a log line, never faked). chat_golden_v2 adds routing scenarios the upgrade cares about: CHAT classification must use no tools, aggregates route to get_income_statement / get_balance_sheet rather than transaction paging, and the new analytical tools are selected with sensible params. The dataset header documents the harness's single-shot limitation. * docs(ai,mcp): current tool tables, responder loop, prompt structure, timeout math Both docs listed 7 tools against a registry of 19, in three separate drift-prone copies. mcp.md now carries the canonical tables (default + preview); ai.md links to them from the MCP section, keeps one grouped functions list for the architecture chapter, and replaces its stale hardcoded registry snippet with a pointer to assistant.rb. The architecture section gains the contracts contributors need when adding a function: the responder loop (rounds vs calls, cap 8, the no-tools grace turn) and the error/hint soft-failure convention, plus the prompt's static/session-context split and its collapse gates. Timeout guidance is recomputed for the new default cap. * fix(assistant): address automated review findings Codex and CodeRabbit findings on the initial push, all verified before changing anything: - AI time series rounded every value to two decimals, which turns 0.001 BTC into 0.0; values now round to the currency's own precision (BTC 8, CLF 4, OMR 3). - get_income_statement validated account_ids against all visible accounts, but totals_for excludes hidden, excluded-from-reports and tax-advantaged accounts, so those ids produced silent zeros. Ids now validate against income_statement.eligible_accounts and the soft failure explains eligibility. - get_recurring_transactions computed totals from the displayed rows, so past the 200-row cap the value labeled a total was partial. Totals now aggregate over the full filtered scope in SQL, and the response carries total_results and a truncated flag. The upcoming_within_days window also starts at today, matching its documentation; overdue items appear in unwindowed calls. - get_valuations silently dropped a malformed date filter and presented unfiltered data as filtered; malformed dates now return invalid_date. - get_balance_sheet returned a generic failure for a reversed custom range because Period's own validation raises past the Date::Error rescue; it now returns the structured invalid_date error. - get_insights documents that its family-wide scope matches the web feed exactly (InsightsController serves Current.family.insights to every member), so the tool exposes nothing the /insights page does not already show the same user. - Tests: limit clamp proven against more insights than the cap, Setting fallbacks stubbed in the provider budget tests, currency precision and reversed-range regression tests added. * refactor(assistant): apply reviewer nitpicks - order declares type alongside its enum, matching sort_by - page-size clamp deduplicated into the base class (MAX_PAGE_SIZE + shared resolved_page_size); dead per-tool copies removed - get_accounts preloads balance rows only when the series is requested - get_income_statement validates the bucket count before running any aggregation work Deliberately unchanged: the balance sheet's monthly_history key. The default response shape stays byte-compatible for existing MCP consumers, and the nested series already states its interval. * fix(assistant): second-round review findings on get_valuations - A reversed date range (start after end) now returns the structured invalid_date error instead of presenting an empty result as filtered data, matching get_balance_sheet's handling. - Page numbers are normalized before pagination: Pagy raises on zero, negative or non-numeric pages. The fix lands as a shared resolved_page helper on the base class and applies to every paginated tool (categories, tags, merchants, transactions, holdings, valuations), since all shared the same page-or-1 pattern; schemas declare minimum: 1. * fix(assistant): round series amounts as BigDecimal before Float conversion Converting to Float first can perturb the value at the requested precision; round the exact decimal, then convert for JSON. * fix(assistant): address maintainer review findings - get_accounts no longer fails the whole listing when one account's start date lies beyond the requested period (start_date derives from the first entry, which can be future-dated); that account simply has no series. The unrescued Period.custom was reachable exactly there. - The balances preload is gone: the series goes through Balance::ChartSeriesBuilder, which runs its own query keyed by account ids, so the eager-loaded rows were loaded and discarded. - Provider::Openai#context_window now delegates to Assistant::TokenBudget, removing the duplicated ENV > Setting > default precedence so prompt assembly and the provider can never disagree about the window. * fix(ai): final no-tools round uses tool_choice none instead of dropping tools Anthropic rejects requests whose messages contain tool_use blocks when no tools are defined, so re-requesting with an empty tool list made the final-round grace die in a provider 400 on Anthropic models. The final round now sends the real tool definitions with tool_choice none, which both providers accept, and the model answers in prose as intended. * fix(assistant): scope every income statement read to the requesting user get_income_statement validated account_ids against the user-scoped statement but computed every total from an unscoped one. IncomeStatement falls back to Current.user, which is nil in the assistant job and the MCP endpoint, so the unscoped reads dropped the included_in_finances_for filter and reported family-wide totals next to ids that had been checked against a narrower set. Route all reads through one memoized user-scoped statement, the idiom get_balance_sheet already uses. Also lets the per-instance memoization in IncomeStatement apply across the eligibility check and the totals. Adds a regression test that fails without the change, plus a companion test asserting eligibility and totals agree on scope. Guard the strictness walk against an empty registry so it cannot silently assert nothing.	2026-08-21 21:58:47 +02:00
Sure Admin (bot)	5c18086089	docs: refresh Sure MCP and external AI setup (#2608) ... * docs: explain self-hosted onboarding modes * docs: refresh MCP and external AI docs * docs: correct MCP auth and tool accuracy * docs: address MCP review comments	2026-08-20 06:37:42 +02:00
4 people	efb7cc3935	Tooling for the wealth + tax agent harness (#2848) ... * Expose the Statement Vault to external agents over MCP A user wants to manage patrimonial history — a document-backed record of a family's wealth where every figure traces back to the statement it came from — by pointing an external agent harness at Sure. That model belongs in the harness, not in Sure: it needs numbered build deltas, golden tests and closed periods that a mutable Postgres row cannot provide. What Sure was missing was the seam. The Statement Vault already does most of the work — original bytes retained, SHA-256 dedup, period detection, account matching with a confidence score, reconciliation against ledger balances, and a month-by-month coverage map — but it is reachable only from the web UI. An agent could not archive a document, cite one, or check for gaps. Adds five preview MCP tools over what already exists, plus a citation grammar for values the agent writes: - upload_account_statement, list_account_statements, get_account_statement, get_statement_coverage - record_valuation, whose source citation is parsed rather than trusted: ["estimated: "] citation [" (grade: A|B|C)"]. An uncited or free-styled value is rejected at the write boundary instead of landing in the ledger looking authoritative. link and reject are deliberately not exposed. Attaching a statement to an account is the human's decision, and the vault UI is where it is made; the agent reports the suggested match and stops there. Assistant.function_classes now takes a user so preview tools stay out of the default surface. They are hidden from tools/list and not callable by name without the preference enabled, and the vault tools re-check the manager role and per-account permissions, since MCP calls never pass through a controller. Docs: the blueprint this implements, and a guide covering which side owns which layer, the vocabulary map between the two, the monthly runbook, and the gaps (non-user holders, non-statement documents, one value per date). No migrations, no API endpoints, no UI. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFDp9HhXDeswadu4cxFojn * Address review feedback on the vault MCP tools Two non-blocking items from the review pass: Document why get_statement_coverage reads through accessible_by rather than writable_by. It reports which documents exist and writes nothing, so read access is the right bar — and tightening it would hide coverage gaps from people who can already see the figures those gaps sit behind. The comment exists so a future refactor doesn't "fix" it. Close the acknowledged verification gap with tests rather than a one-off manual check. The review noted that nothing proved a real vault payload serializes cleanly out through tools/call — vault responses are richer than the other tools' output, with nested account hashes, decimal balances, dates and a compacted hash. Two integration tests now drive the real /mcp endpoint end to end against a real AccountStatement: one listing it, one uploading bytes and reading back the SHA-256. Permanent regression coverage instead of a smoke test someone has to remember to repeat. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFDp9HhXDeswadu4cxFojn * docs(llm-guides): replace patrimonial blueprint with its final revision Swap the embedded early draft for the authoritative final revision of the wealth + tax modelling blueprint (MIT © 2026 diegomarino): - rename the domain vocabulary: patrimonial -> wealth, fiscal -> tax (tax_data/, the tax layer, tax_runner) - add §9.5 (the intel file: shape, generation, and the capture loop) - tighten worked examples down to placeholders - add the MIT header; keep the in-repo NOTE block (adapted to the new vocabulary) and the filename untouched so cross-links don't break * docs(llm-guides): align agent-harness guide with blueprint + fix reconcile semantics Follow the blueprint rename (patrimonial -> wealth, fiscal -> tax, fiscal_data/ -> tax_data/, "Phase 7 (fiscal layer)" -> "(the tax layer)") so the two docs stop disagreeing on vocabulary. Correct the reconciliation mapping, which conflated two different invariants: - blueprint reconcile-or-abort (§7 pass 3) is parse-integrity (parsed parts == the document's own printed total); Sure's reconciliation_checks is ledger agreement (statement balances vs the ledger). Sure has no parse-integrity check and never aborts. - opening_balance / closing_balance are user-entered, not auto-extracted, so over MCP reconciliation is "unavailable" until a human fills them. - tolerance differs: blueprint 1.00/account-period vs Sure's fixed 0.01. State in the ownership table, the invariants section, the vocabulary map and the monthly runbook that parse-integrity and the abort belong to the harness extractor. * Correct the vault tools' reconciliation claims and citation parsing Review findings from @diegomarino, all verified against the code before changing anything. The reconciliation claim was the serious one. get_account_statement told agents the checks were "the trustworthy part" and returned "the balances read off it" — but nothing reads balances off a document. MetadataDetector never touches them and create_from_prepared_upload! never sets them; they are user-editable fields in the Statement Vault UI. So a statement archived over MCP always came back with an empty check list, which an agent could easily read as "the document agrees with the ledger" when it means "nobody has entered the figures". The description now says so, and the payload carries a reconciliation_note spelling it out for anything reading only the JSON. Also noted that these checks are ledger agreement, not parse integrity: nothing here verifies a document's parts sum to its printed total. Provenance::Citation had two patterns disagreeing about spacing. GRADE_SUFFIX allowed "(grade:A)" but FORMAT required exactly one space, so that citation passed the pre-check and then parsed as ungraded with the grade swallowed into the text — silently discarding the reliability the caller supplied, which is the one thing this parser exists to prevent. list_account_statements downcases content_sha256 before querying. The column is constrained to lowercase hex, so uppercase input could never match, and an agent would read the empty result as "not archived" and upload a duplicate. Its period filters are renamed overlapping_from / overlapping_until, since they match on overlap and the old names claimed otherwise to anyone reading the schema without the descriptions. has_more now explains that there is no cursor and the way forward is a bigger limit or narrower filters. record_valuation no longer overwrites the entry's notes. Re-recording a date would destroy a note a person had written there. Nothing is removed now: an identical citation is a no-op, a changed one is appended, and the trail of what was cited when survives. Detecting "did this tool write that line?" is not possible — almost any prose parses as a valid ungraded citation — so the code does not guess. Minor: accept urlsafe base64 on upload, and explain in the code why record_valuation checks the account ACL rather than the vault manager role, so nobody "tightens" it into the wrong permission later. Tests cover each: the grade-spacing cases both ways, uppercase SHA lookup, overlap window boundaries, note preservation and no-stacking, the unavailable reconciliation note appearing and disappearing, and — per the review — that the download URL's signed id actually expires, rather than trusting the description's claim. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFDp9HhXDeswadu4cxFojn * Repair a bad merge in the MCP controller test The merge of main spliced the incoming `tools/call executes update_transaction` test into the middle of the upload round-trip test, before its closing `end`. That left the file one `end` short, so it did not parse — taking out both `ci / lint` (Lint/Syntax) and `ci / test_unit` (the whole file failed to load). Restores the missing `end`. Both tests are kept as their authors wrote them; nothing else changes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFDp9HhXDeswadu4cxFojn * docs: use wealth history wording (#2885) * Stop the vault tools promising verification they don't perform Three findings from the automated review passes, all confirmed against the code before changing anything. The download URL was dead on arrival for the caller it was built for. Sure serves stored files through Active Storage controllers that config/initializers/active_storage_authorization.rb gates on `viewable_by?(Current.user)` — a signed-in browser session. An MCP client has a bearer token and no session, so following the URL would have redirected to sign-in. Removed it rather than leaving a link that cannot work, and the description now points at search_family_files or the vault UI. Coverage called a month `covered` when a document merely existed. An unreconciled statement is not mismatched, so it took the `covered` branch, and the payload carried nothing to correct the reading — the same "advertised verification that never happened" bug fixed last round in get_account_statement, in a second place. Months now carry their own reconciliation_status, and the description says covered means presence, not agreement. Listing filtered visibility after limiting. Beyond underfilling a page, with no cursor and a 100-row cap an accessible statement behind enough newer invisible ones was unreachable. Visibility now lives in the query, mirroring viewable_by? for a statement manager. Also: rescue unexpected upload failures into a tool error instead of a raw exception string, derive the documented size limit from MAX_FILE_SIZE, list every coverage status in mcp.md, and cover the failed-reconciliation and base64-normalisation branches. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFDp9HhXDeswadu4cxFojn * Keep storage exception detail out of the MCP response The upload_failed message interpolated the exception text, which crosses out to an external agent. A storage failure can carry bucket names, object keys, paths or request details, so the agent now gets a fixed message and the exception stays in the server log. The test asserts the absence of detail rather than pinning the leaked string into the contract. Also fixes a test that did not test what it claimed: the urlsafe-base64 case used a fixture encoding to plain base64, so it exercised the padding branch and never the "-_" translation. It now uses content whose encoding contains both characters and asserts that up front. Renames "rejects content that decodes to zero bytes" to "rejects blank content", which is what it actually covers — Base64.strict_encode64("") is "", which is blank and returns before the decoder runs, so invalid_content is correct and empty_file is not reachable from this path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFDp9HhXDeswadu4cxFojn * docs: align wealth blueprint review feedback * Correct the harness runbook: parse before publishing The guide told an implementer to archive each document to Sure first and work from there. That strands them. Sure never returns a document's bytes over MCP — Active Storage serves stored files only to a signed-in browser session — and there is no text fallback either, because statements archived through upload_account_statement never enter the vector store, so search_family_files cannot see them. A statement in Sure is metadata to an agent and nothing more. That blocks exactly three blueprint steps, all of them operating on bank and broker statements: the extractors, the parts-vs-printed-total check, and the glyph decoder. Everything else it parses — tax returns, capital accounts, annual accounts — the harness already holds locally. So the order inverts: the harness ingests into its own vault, extracts there with the whole file in reach, and publishes to Sure afterwards. This restores principle 8 rather than bending it — the recurring pipeline reads from the canonical store, and treating Sure as canonical forced a re-fetch the architecture never sanctioned. Both sides hash the same bytes, so the SHA-256 verifies Sure holds the identical document without moving it. Writes down the two consequences: a statement uploaded straight into Sure's UI can be known but never parsed (reliability C or PENDING until a copy reaches the harness), and neither vault backs up the other. Also drops a stale tools-table row still advertising the 15-minute download URL removed earlier, corrects get_account_statement's description where it suggested search_family_files as a fallback it cannot be, and disambiguates "the vault" in the MCP tool table, which is what misled me in the first place. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JFDp9HhXDeswadu4cxFojn --------- Signed-off-by: Juan José Mata <juanjo.mata@gmail.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: diegomarino <diegomarino@users.noreply.github.com> Co-authored-by: Sure Admin (bot) <sure-admin@splashblot.com>	2026-08-04 23:33:01 +02:00
AtlasandJuan José Mata	53a87a7645	fix(mcp): assign OAuth clients read_write scope (#2884) ... * fix(mcp): assign OAuth clients read_write scope * fix(mcp): default registered OAuth scope --------- Co-authored-by: Juan José Mata <juanjo.mata@gmail.com>	2026-08-04 23:10:39 +02:00
Josh	60d9a70aff	Refresh Pipelock integration for v2.8 receipts (#2406) ... * chore(pipelock): refresh integration for v2.8 receipts * Clarify Pipelock receipt key mounts	2026-06-19 17:16:38 +02:00
JoshandJuan José Mata	ca895416a4	chore(helm): bump pipelock to 2.5.0 and surface 2.5 config (#1913) ... * chore(helm): bump pipelock to 2.5.0 and surface 2.5 config Bumps pipelock.image.tag from 2.2.0 to 2.5.0 and exposes the most relevant 2.5 features as structured Helm values: - pipelock.requestBodyScanning: scan outbound bodies and sensitive headers for prompt-injection and DLP payloads. Disabled by default; roll out with action=warn before flipping to block. - pipelock.healthWatchdog: structured config for the wedge-detection watchdog with an exposeSubsystems toggle for /health detail. - pipelock.mcpToolPolicy.rules: structured values for rendering mcp_tool_policy.rules including redirect-profile references. Also fixes a latent config-validation regression: pipelock 2.x rejects an enabled mcp_tool_policy with no rules, but the chart previously defaulted to enabled=true with an empty rules list, which hard-fails 'pipelock check'. The default is now enabled=false; operators must explicitly enable and provide at least one rule. Refreshes README, CHANGELOG, docs/hosting/pipelock.md, docs/hosting/ai.md, compose example pin comment, and pipelock.example.yaml to call out 2.5 highlights (Audit Packet v0 verifiers, SPIFFE-strict envelopes, scanner attribution on MCP block receipts, pipelock doctor). Also fixes a stale docs/hosting/mcp.md reference to the removed compose.example.pipelock.yml. * chore(helm): fail helm template when mcp_tool_policy enabled with no rules Adds a guard in asserts.tpl so an operator who sets pipelock.mcpToolPolicy.enabled=true without populating pipelock.mcpToolPolicy.rules gets a clear render-time error instead of a container crash-loop with the pipelock validation message. Per CodeRabbit feedback on #1913. * Versions --------- Co-authored-by: Juan José Mata <jjmata@jjmata.com>	2026-05-24 13:50:44 +02:00
3 people	a0b1029ba9	Documentation for review AI Assistant features, MCP and API additions (#1168) ... * Create MCP server endpoint documentation * Add Assistant Architecture section to AI documentation * Add Users API documentation for account reset and delete endpoints * Document Pipelock CI security scanning in contributing guide * fix: correct scope and error codes in Users API documentation * Exclude `docs/hosting/ai.md` from Pipelock scan --------- Co-authored-by: askmanu[bot] <192355599+askmanu[bot]@users.noreply.github.com> Co-authored-by: Juan José Mata <jjmata@jjmata.com>	2026-03-16 18:24:28 +01:00