feat: SMARTS trading pipeline with Telegram notifications and Miro visualization by AndriiPasternak31 · Pull Request #13 · Abilityai/trinity

AndriiPasternak31 · 2026-02-06T02:04:56Z

Summary

This PR adds comprehensive SMARTS trading pipeline support:

SMARTS Agent Templates

Added 8 new agent templates: market-regime, news-sentiment, discovery, analysis, decision, execution, portfolio-manager, feedback
Support for config.yaml format (SMARTS-style agents)
System-wide template configuration (system.yaml)

Telegram Notifications

Added Telegram to NotificationConfig in process engine
New smarts_summary_service.py for generating trading summaries
Telegram notification handler integration

API & Scheduler

New SMARTS summary endpoints
Scheduler support for periodic summaries

Miro Visualization

Live flow visualization from Supabase to Miro boards
Auto-generated pipeline architecture diagrams
Proper HTML formatting (<br> tags) for card text
data/smarts-flows/ directory for JSON exports

Other

Refactored find_template_file usage across codebase
SMARTS cascade deployment script
Documentation updates

Test plan

Agent templates load correctly
Telegram notifications send successfully
Miro diagrams render with proper formatting
JSON exports contain complete pipeline data

🤖 Generated with Claude Code

- Add scripts/smarts_diagram/ package with: - parser.py: Extracts architecture from agent templates - miro_generator.py: Generates diagram layout - miro_client.py: Miro REST API v2 client - Add scripts/update_smarts_diagram.py entry point - Update .claude/commands/update-docs.md with diagram step - Add MIRO_ACCESS_TOKEN and MIRO_BOARD_ID to .env.example Usage: python3 scripts/update_smarts_diagram.py --dry-run Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Add 8 SMARTS pipeline agents + supporting templates: - market-regime: Market condition detection - news-sentiment: News and sentiment analysis - discovery: Trading opportunity scanner - analysis: Deep technical analysis - decision: Position sizing and decisions - execution: Order execution via Alpaca - portfolio-manager: Risk oversight - feedback: Performance tracking Also includes: - analyst-agent variants (bull, bear, risk, quant) - scanner-agent, executor-agent, synthesis-agent - smarts-trading, smarts-trader-minimal bundles - gcp-log-monitor utility agent - system.yaml configuration Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Add SMARTS summary service for daily trading reports: - Pulls data from Supabase integration_context - Formats comprehensive summaries per agent - Sends to Telegram with deduplication - Scheduler for automated daily reports Add Telegram channel to notification handler: - Support bot_token and chat_id configuration - Environment variable fallback support - Markdown formatting for messages Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Add new endpoints in ops router: - POST /api/ops/smarts/summary - Generate and send summary - GET /api/ops/smarts/test-telegram - Test Telegram connection Integrate summary scheduler in main.py: - Start scheduler on app startup - Stop scheduler on app shutdown Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Add find_template_file() to check template.yaml then config.yaml - Support both template formats for backwards compatibility - Add default resources configuration - Improve credential extraction for SMARTS agents Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Update all template loading code to use find_template_file() for consistent config.yaml support: - routers/credentials.py - routers/templates.py - services/agent_service/crud.py - services/system_agent_service.py Also use DEFAULT_RESOURCES constant for consistency. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Add Telegram channel support to notification step configuration: - bot_token: Telegram bot token (supports env var) - chat_id: Telegram chat ID (supports env var) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Add changelog entries for SMARTS features - Update architecture documentation - Update roadmap progress Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Script to deploy all SMARTS agents in cascade order. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Add flow_visualizer.py to retrieve complete analysis flows from Supabase - Create update_smarts_flow.py CLI entry point - Extract and visualize full decision chain: market_regime → discovery → analysis → decision → execution - Support symbol-specific and auto-select modes - Add SUPABASE_URL/SUPABASE_ANON_KEY to .env.example Usage: python scripts/update_smarts_flow.py --symbol AAPL python scripts/update_smarts_flow.py --dry-run Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Add MiroClient.create_board() for creating new boards via API - Flow visualizer now prefers MIRO_FLOW_BOARD_ID over MIRO_BOARD_ID - Update .env.example with separate board IDs for architecture vs flows Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Remove all text truncation from flow cards (show full data) - Reorganize flow layout: - Market Regime at top-left - News Sentiment cards stacked vertically (up to 3) - Main pipeline in horizontal row: Discovery → Analysis → Decision → Execution - PM Directive below pipeline with connectors - Add visual separator line between architecture and flow sections - Increase card sizes for better readability Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Replace \n with <br> tags for Miro sticky note compatibility - Add <br> spacers between sections for visual grouping - All format_*_content() functions now use HTML line breaks - Cards display with proper section separation Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

- Add changelog entry for flow visualization feature - Create data/smarts-flows/ directory for JSON exports - Add README with usage instructions - Gitignore JSON files (contain live trading data) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

…idate-architecture Backend: unregister 7 Process Engine routers (processes, executions, approvals, triggers, alerts, process_templates, audit) plus the process-docs router; drop startup hooks for execution recovery and the process-engine WebSocket publisher. Services under services/process_engine/ remain in place as dormant code. Frontend: remove 11 process-related routes (/processes, /processes/new, /processes/docs, /processes/wizard, /processes/:id, /executions, /approvals, /executions/:id, /process-dashboard) and the dead isProcessSection computed in NavBar. Keep /alerts and /events legacy redirects to Operating Room. Docs: correct stale count claims in architecture.md (main.py line count, router count 45 -> 53, service count 23 -> 37, MCP tool modules 15 -> 16) and expand database.py scope description to reflect 27 domain op classes. Skill: expand validate-architecture to detect drift between arch.md and code: count alignment (D1), scope coherence (D2), enforced MCP parity under #13 (tool module OR '# mcp: none' opt-out), and inline authorization sprawl detection under #8. Output now includes suggested arch.md edits with line numbers, not just pass/fail. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…ffects (#1084) (#1351) * feat(idempotency): effect-scoped guard primitive for outbound side effects (#1084) Trigger-boundary idempotency (#525, Invariant #18) dedups the execution but not an agent's individual tool calls — so a re-delivered turn (the at-least-once semantics pull-mode / work-stealing will introduce, Epic #1045/#1081) re-emits the same outbound effect. Add the per-sink primitive that enforces exactly-once external effects at the sink, keyed on resolved effect identity. In services/idempotency_service.py (no new module — avoids the untracked-file / Docker-COPY crash class): - make_effect_scope(execution_id) → effect:{execution_id} - make_payment_scope(agent_request_id) → payment:{agent_request_id} - derive_effect_key: {effect_type}:sha256(execution_id \x00 effect_type \x00 resolved_identifying_args \x00 dedup_label) — STABLE identity only, never the LLM-generated body (non-deterministic across a re-run → would defeat dedup); dedup_label lets an agent intentionally send two distinct messages per turn. - resolve_and_validate_execution: generalizes the MEM-001 server-side resolution (the agent supplies execution_id, never its own identity); FAIL-OPEN on missing/invalid/mismatch so an old image or absent arg never 5xxes a real send. - effect_guard async context manager: completed replay → snapshot (no re-send); in_flight replay → raises retryable EffectInProgressError (codex #6, never a silent None-as-success); fresh claim → complete() on clean exit, fail() (release for retry) on exception. Payment scope path for Nevermined (native token). Reuses the existing 24h-default claim TTL (already exceeds the lease window), so a completed row outlives a late re-delivery — no new TTL plumbing. TDD: 22 new unit tests in tests/test_idempotency.py (40 total green) — body independence, dedup_label, fresh-execution-id, in_flight-raises, fail-open, 6h-aged replay, payment scope. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(payments): guard Nevermined settle with payment-scoped effect idempotency (#1084) The highest-stakes sink first. Add NeverminedPaymentService.settle_payment_once, which wraps settle_payment in the effect guard keyed on payment:{agent_request_id} — Nevermined's native exactly-once token IS the dedup scope. A retried paid chat reusing the same token replays the stored settle receipt instead of burning credits twice; the native token remains the real on-chain guarantee, this avoids even attempting a duplicate and gives a fast local replay. - completed replay → returns the stored sanitized receipt (never the raw SDK object), no re-settle. - a FAILED settle raises an internal _SettleNotCompleted so the in_flight claim is RELEASED (only a successful settle persists as completed/replayable) → a later retry can re-attempt. - a concurrent in-flight settle → retryable "already in progress" result, never a silent skip (codex #6). - no agent_request_id → fail-open, settle proceeds without dedup. routers/paid.py Step 4 now calls settle_payment_once; the existing terminal-turn guard (failed execution → no settle, prior learning terminal-applier-status-leak) is the preserved outer layer. TDD: 4 wiring tests (retried→one settle, failed→release+retry, distinct tokens →both, missing token→fail-open). 44 idempotency tests green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(messages): effect-guard proactive send_message on resolved recipient+channel (#1084) Thread execution_id + dedup_label through routers/messages.py → send_message, and wrap the entry in the effect guard keyed on the RESOLVED recipient + channel (never the LLM-generated body, which is non-deterministic across a re-run). When the turn it ran in is re-delivered (pull-mode at-least-once), the same identity within one execution dedupes to exactly one send; a distinct dedup_label lets an agent intentionally send two messages to the same recipient per turn. - send_message refactored: the entry guard wraps a new _send_message_inner (auth → rate-limit → channel delivery), so a success records a replay snapshot and an exception releases the claim for retry. Replay reconstructs the DeliveryResult. - A chunked message is ONE effect (entry guard) — a mid-chunk crash re-sends the whole message on retry (at-least-once for chunks, documented). - Concurrent in-flight duplicate → EffectInProgressError → router returns 409 (retryable), never a silent skip-and-succeed (codex #6). - Fail-open when execution_id absent/invalid (old image). Drive-by: removed two dead imports (time, enum.Enum) + one stray f-prefix to keep the touched files ruff-clean. TDD: 4 wiring tests (re-delivery→one send, dedup_label→two, no-execution_id→ fail-open, distinct-recipient→not-deduped). 48 idempotency tests green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(voip): effect-guard call_user on resolved dial target (#1084) Thread execution_id + dedup_label through routers/voip.py → place_outbound_call, and wrap the dial in the effect guard keyed on the RESOLVED dial target + Twilio account, scoped to execution_id. When the turn it ran in is re-delivered (pull-mode at-least-once), the same number within one execution replays the original {call_id, status, ...} instead of placing a second PSTN call. - place_outbound_call refactored: the entry guard wraps a new _place_call_inner (abuse controls → stage Gemini intent → dial Twilio), so a success records a replay snapshot and a raised HTTPException releases the claim for retry. - The router's boundary Idempotency-Key gate stays the OUTER layer (kept). - Concurrent in-flight duplicate dial → EffectInProgressError → router releases the outer trigger claim and returns 409 (retryable), never a silent skip. - Fail-open when execution_id absent/invalid (old image). Drive-by: removed one dead twilio import to keep the file ruff-clean. TDD: 4 wiring tests (re-delivery→one dial, dedup_label→two, no-execution_id→ fail-open, distinct-number→not-deduped). 52 idempotency tests green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(files): effect-guard share_file on filename + content version (#1084) Thread execution_id + dedup_label through routers/agent_files.py → create_share, and wrap the token-mint + persist in the effect guard keyed on the filename + a sha256 of the extracted CONTENT, scoped to execution_id. A re-run of the same turn sharing the same file replays the original signed URL instead of minting a second token; a changed file under the same name produces a new share. - create_share extracts up-front (so the key can version on content), then the guard wraps a new _finalize_share (MIME/quota/disk → persist → mint token + DB row → URL). Success records the URL snapshot for replay; an exception releases the claim for retry. - ShareFileMcpRequest gains execution_id + dedup_label; the internal agent-server share path passes neither → fail-open (back-compat). - Concurrent in-flight duplicate → EffectInProgressError → router 409. Drive-by: removed a dead typing.Optional import to keep agent_files.py ruff-clean. TDD: 3 wiring tests (re-run→same URL replay, changed-content→new share, no-execution_id→fail-open). 55 idempotency tests green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(mcp): execution_id + dedup_label params on send_message / call_user / share_file (#1084) Inv #13 third surface. Add optional agent-supplied execution_id + dedup_label params to the messages.ts (send_message), voip.ts (call_user) and files.ts (share_file) tools, and thread them into the request bodies in client.ts (sendUserMessage / placeVoipCall / shareAgentFile). The agent reads execution_id from the 'Execution Context' block of its system prompt (same source as write_user_memory / MEM-001) and passes it so the backend effect guard dedupes a re-delivered turn to exactly one effect; omitting it is fail-open (the send proceeds). dedup_label lets the agent intentionally repeat an effect to the same target in one turn. Trusted runtime injection of execution_id (+ fail-closed-when-absent) is deferred — a BLOCKING prerequisite on Epic #1045/#1081 before pull-mode default-ON for side-effect agents. Tests: new messages.test.ts asserts execution_id + dedup_label reach the body (and undefined when omitted), plus a regression assertion that chat_with_agent still derives a non-empty mcp: Idempotency-Key. 31 MCP tests green; tsc clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(reliability): effect-idempotency contract + architecture + pull-mode gate (#1084) - New docs/memory/feature-flows/effect-idempotency.md: the per-sink exactly-once contract — honest scope (local suppression vs true exactly-once), the 6 design decisions, wired sinks table, the BLOCKING pull-mode-default-ON prerequisite, and the documented failure modes (pre-call crash window, chunk at-least-once, git idempotent-by-construction). - architecture.md: extend the RELIABILITY-006 (#525) Idempotency block with the #1084 effect-scoped layer (effect_guard, scopes, body-independent key, in_flight≠completed, 24h-TTL reuse, wired sinks, the gate). - feature-flows.md: Recent Updates row + a Documented Flows entry. - task_execution_service.py: dispatch_async_eligible carries the pull-mode gate comment (trusted execution_id injection + fail-closed-when-absent required before pull-mode default-ON for side-effect agents — Epic #1045/#1081). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(security): CSO --diff audit for effect-scoped idempotency (#1084) CLEAR — no CRITICAL/HIGH. Confirms the load-bearing auth property: a forged or borrowed execution_id fails-open (no claim, no cross-tenant snapshot read) because agent_name is always authenticated and resolve_and_validate_execution checks ownership before the claim. No secrets, no injection (agent-supplied identifying_args/dedup_label are hash-only), no new deps, no new SQL. One LOW noted (share download token at rest in idempotency_keys — same backend-internal trust level, no net exposure). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(idempotency): harden effect-guard replay + cap key inputs (#1084) - Bound execution_id/dedup_label with max_length=200 on send_message and call_user request models so a hostile/oversized value can't bloat the derived effect key. - Replay-with-missing-snapshot (I2): a completed effect replay is terminal, so never re-emit the side effect even when the stored snapshot is NULL/unparseable. share_file raises 409 (cannot rebuild the signed URL); Nevermined settle reports success without a receipt and logs a warning (never re-enters the external settle path → no double-charge). - Track the _finalize_share → _persist_and_register rename in the share_file guard test. Refs #1084 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(test): #679 paid-settle test mocks settle_payment_once after #1084 reroute paid_chat's success path now settles through settle_payment_once (the effect-scoped idempotency wrapper, #1084) rather than bare settle_payment, so the #679 success-still-settles regression test must mock/await the new entrypoint. The cancel/fail siblings keep asserting non-settle (neither entrypoint is reached on a terminal turn). Refs #1084 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(reliability): requirements §10.10.1 + sink-flow pointers for effect idempotency (#1084) Adds requirements.md §10.10.1 documenting the effect-scoped extension to RELIABILITY-006, and cross-reference pointers from the four wired sink flows (voip-telephony, proactive-messaging, file-sharing-outbound, nevermined-payments) to the canonical effect-idempotency flow (one-home-per-feature rule). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…y/citation accuracy (#1358) * docs(#945): correct postcard result-reporting + taxonomy/citation accuracy Audit-driven corrections to the actor-model postcard (the deliverable for #945, which originally landed via PR #1293/#946 with no #945 linkage): - Fix factual error: schedule_execution_completed IS emitted by the scheduler (src/scheduler/service.py) for schedule-triggered runs, but no agent-facing path consumes it and it's not emitted on the agent->agent MCP path the #946 pilot uses. Prior text wrongly said "never emitted"; the polling conclusion is unchanged. - Pin the shipped TaskExecutionErrorCode enum explicitly and note the contract adds OOM/MAX_TURNS on top, so the divergence is intentional. - Fix demotion-map citation: session_id unifies #8-#12 (not #8-#13); #13 inject_result is causation_id; drop the non-existent "continue_session". Closes #945 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(#945): correct stale ParallelTaskRequest field count (15 -> 14) The model has 14 fields today (src/backend/models.py:97-112), not 15 — the demotion map's own code block already listed 14. Fix the prose counts ("13 of its 14 [optional]", "13 silent siblings"), the stale line-ref (:84-99 -> :97-112), and the TARGET_ARCHITECTURE mirror of the claim. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

* chore(mcp): add yaml dependency for pipeline definition parsing The #919 pipeline-introspection tools parse agent-published ~/.trinity/pipelines/*.yaml definitions to produce a compact summary. Add the pure-JS `yaml` (^2.6.1) parser — chosen for its hardening knobs (`uniqueKeys` duplicate-key rejection, `maxAliasCount` billion-laughs guard) and for instantiating no arbitrary classes (no PyYAML-style RCE surface). Lockfile resolves to 2.9.0. Refs #919 Co-Authored-By: Claude <noreply@anthropic.com> * docs(schemas): add authoritative agent-pipeline file contract (#919) The agent owns its long-running multi-stage pipeline (DAG, execution, recovery) per Architectural Invariant #8; Trinity only reads two files the agent publishes inside its container: ~/.trinity/pipelines/<pipeline_id>.yaml — definition ~/.trinity/pipeline-state/<pipeline_id>/<instance>.json — runtime state Add the two JSON Schema (draft 2020-12) documents that pin this contract. The state schema's `required` set (instance_id, current_stage, health, updated_at, escalations) is exactly what the MCP tools read for their summary, so the schema is the single source of truth for the surface — the tools are sync-tested against it. Both schemas are intentionally `additionalProperties: true` (agent-extensible) and document the operator-queue `context` grouping convention. Refs #919 Co-Authored-By: Claude <noreply@anthropic.com> * feat(mcp): add agent workspace file read methods to TrinityClient (#919) Pipeline introspection reads the agent's published files over the EXISTING GET /api/agents/{name}/files (recursive list) and /files/download (read) surfaces — no new backend endpoint (Invariant #8/#13 satisfied by reuse). Extract the auth-header + single 401-reauth-retry + error-mapping logic out of `request<T>()` into a private `_fetch()` that returns the raw `Response`, so the JSON `request` path and the new plain-text `downloadAgentFile` path differ only in `.json()` vs `.text()` and cannot drift on auth/retry/error handling. Add: - listAgentFiles(name, path, showHidden) -> AgentFileTreeResponse - downloadAgentFile(name, path) -> string (download is PlainTextResponse) Plus the AgentFileNode / AgentFileTreeResponse types for the recursive tree (each node carries an ISO-8601 `modified` mtime — the tie-breaker for latest-instance selection). Refs #919 Co-Authored-By: Claude <noreply@anthropic.com> * feat(mcp): add list_agent_pipelines + get_agent_pipeline_state tools (#919) Two thin, read-only MCP tools that give Trinity a uniform window onto an agent's self-published pipelines without owning the DAG (Invariant #8): - list_agent_pipelines(agent_name): enumerate ~/.trinity/pipelines/*.yaml, each with a health summary from its LATEST instance (current_stage, health, open_escalations, updated_at). Selection is by state-file mtime (tie-broken on instance_id), so the read fan-out stays at one download per pipeline. Capped at 50 pipelines with logged (never silent) truncation. A malformed single file is an item-level error that never aborts the list. - get_agent_pipeline_state(agent_name, pipeline_id, instance_id?): full parsed state JSON for one instance; omit instance_id for the latest. Security/robustness: - pipeline_id/instance_id are zod-validated ^[A-Za-z0-9._-]+$ AND reject `..` BEFORE any download — the download endpoint has no deny-list, so this is the P1 path-traversal guard (defense-in-depth over the agent-server's home-prefix confinement). - YAML parsed with a 256 KiB pre-parse size cap + duplicate-key rejection + alias-expansion guard; JSON state size-capped before parse. - Error contract: only a 404 maps to empty/not-found; a 400 (agent stopped) or 5xx (unreachable) surfaces as a distinct real error so "no such pipeline" is never confused with "agent down". Registered in server.ts after the FILES-001 file tools. Refs #919 Co-Authored-By: Claude <noreply@anthropic.com> * test(mcp): cover pipeline introspection tools end-to-end (#919) 60 tests via node:test. Pure helpers (id grammar, latest-instance selection, hardened YAML parse, escalation counting, error discrimination) plus both tools against a mocked TrinityClient: - empty/absent pipelines dir -> [] - multi-pipeline parse + latest-instance pick (asserts only the latest instance is downloaded, never older ones) - zero-instance pipeline -> latest:null - malformed-file item isolation (siblings survive) - get_state explicit / latest / not-found / malformed-JSON paths - P1: pipeline_id/instance_id traversal rejection BEFORE any download (LIST/DOWNLOAD must not be called) - stopped (400) / unreachable (503) discriminated from empty/not-found - schema-fixture test pinning that docs/schemas/*.json required sets match what the tools read (the schema IS the contract) - client _fetch shared by JSON `request` + text `downloadAgentFile` (bearer attached, right endpoints, same API-error mapping) Refs #919 Co-Authored-By: Claude <noreply@anthropic.com> * docs(memory): record pipeline introspection tools (#919) - architecture.md: MCP tool catalog 20 -> 21 modules; add the pipelines.ts row documenting the read-only-over-agent_files design, id validation, hardened parse, mtime latest-instance, and only-404->empty contract. - requirements.md §34.1: flip status to Implemented (2026-06-26) with the MCP-only implementation note (reuse of agent_files, P1 traversal guard, schemas as the contract). - TRINITY_COMPATIBLE_AGENT_GUIDE.md: new "Agent-Defined Pipelines" section documenting the file contract, minimal example, both MCP tools, the open_escalations rule, the operator-queue context grouping convention, the agent-side heartbeat ownership (ships in abilityai/abilities, not Trinity), and the adoption note (existing agents return [] until adopted — by design). Refs #919 Co-Authored-By: Claude <noreply@anthropic.com> * docs(security): add CSO --diff audit for pipeline tools (#919) Daily 8/10-gate diff audit of the #919 surface: no findings at or above the gate. Verifies the path-traversal guard (idSchema + agent-server home-prefix confinement), YAML/JSON parse hardening, auth/authz reuse, the client _fetch refactor, and the yaml supply-chain addition. Records below-gate observations (pre-existing agent-server sibling-prefix check) out of diff scope. Refs #919 Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>

…rror (#1167) Sequential agent loops (#740) were fail-fast: the first failed iteration aborted the whole loop. Add a per-loop policy to tolerate failures and keep going, bounded so a fully-broken agent still terminates. - config: `on_failure` ('abort' default = current fail-fast, backward compatible; 'continue' tolerates a failed iteration) + `max_consecutive_failures` (default 3, range 1–100). Both plumbed end to end (Invariant #13). - runner (loop_service.py): both failure surfaces gated — raised exception AND non-success TaskExecutionResult. Continue mode finalizes the failed agent_loop_runs row, increments failed_runs/consecutive_failures, and proceeds; a success resets the streak. Reaching max_runs (or stop-signal) with tolerated failures finalizes as `completed_with_errors`; hitting the consecutive cap finalizes `failed`/`stop_reason=max_consecutive_failures`. {{previous_response}} keeps the last *successful* response (a failed iteration never overwrites it). - schema/migration: agent_loops gains on_failure, max_consecutive_failures, failed_runs (schema.py + tables.py Core + versioned migration). New terminal status `completed_with_errors`. - api: POST /loops accepts on_failure/max_consecutive_failures; LoopStatusResponse surfaces failed_runs/on_failure/max_consecutive_failures. - mcp: run_agent_loop gains the two params (tools/loops.ts + client.ts). - ui: LoopsPanel failure-policy controls + failed_runs/completed_with_errors surfacing. - tests: abort unchanged, continue past a failed run (both surfaces), consecutive cutoff, streak-reset; schema-parity + migrations green. 42 passed. Related to #1167 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

… email-request parity + MCP owner-disclosure removal (#186) (#1455) * fix(auth): uniform 404 in agent-access deps + equalize email-request (#186) Tier 1: collapse the four agent-access dependency helpers to a uniform 404 for both non-existent and inaccessible agents. Evaluate existence and access booleans before branching so query-count (hence timing) is equal, and run the connector-scope check before the existence lookup so a connector key gets a uniform 403 across all non-bound names. Tier 2: POST /api/auth/email/request now returns a byte-identical body + status for whitelisted, non-whitelisted, and rate-limited emails, and dispatches the code email fire-and-forget so the whitelisted path's latency matches the immediate-return paths. Over-limit is WARN-logged server-side instead of a 429 (fail-loud for ops, no client-visible membership oracle). Closes the differential-response enumeration oracles from UnderDefense pentest 3.3.3 at the highest-leverage surfaces. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(auth): sweep router-level agent-enumeration oracles (#186) Tier 3 — collapse ad-hoc 404-then-403 sequences that bypass the dependency helpers: - avatar.py generate/regenerate/delete → OwnedAgentByName (uniform 404; now also connector-scope gated, intended hardening). - nevermined.py _require_read/_require_write_access → uniform 404. - event_subscriptions.py create → collapse source-agent 400-vs-403 into a single uniform 403 for cross-agent subscriptions. - schedules.py webhook generate/status/revoke → AuthorizedAgent so the schedule-404 is only reachable by an authorized accessor. Tier 4 — close the open-GET authz hole + 404-vs-200 existence oracle on agent_config.py capabilities/timeout/public-channel-model/guardrails GETs (raw agent_name + get_current_user, no access check) by binding them to AuthorizedAgentByName. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(mcp): remove owner disclosure + uniform agent-access reason (#186) Tier 5 (Invariant #13). chat.ts checkAgentAccess: collapse the 'not found' vs 'owned by X (not shared)' branches into a single uniform 'Agent X not found or not accessible' reason and REMOVE the owner-username interpolation — a user-scoped caller could otherwise learn who owns any agent (the most serious item the review found: a disclosure, not just a status differential). Consumer classifiers adjusted for the backend 403->404 flip: - reports.ts: treat a 404 on the dep-gated report endpoint as not_authorized (alongside 403). - messages.ts: match the dep's exact 'Agent not found' detail as not_authorized before the generic recipient-404 branch, so an agent-access denial isn't misclassified as recipient_not_found. - nevermined.ts: document that an inaccessible agent now reports configured:false (intentional, enumeration-safe). agents.ts needs no change — its agent-scoped permission denials name caller/target only (no owner leak) and are already uniform w.r.t. existence. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * test(auth): enumeration-uniformity coverage for #186 - New tests/unit/test_186_enumeration_uniformity.py: real-DB (db_harness) assertions that all four agent-access deps return a byte-identical 404 for non-existent vs inaccessible agents (incl. admin-on-nonexistent and owner positive control); real-handler email-request body/no-429 uniformity; and a static guard that the four Tier-4 agent_config GETs now bind get_authorized_agent_by_name. 16 tests, all green. - test_access_control.py: flip the 15 dep-routed owner/read asserts from 403 to 404; admin-gated asserts stay 403. - test_28_voip / test_brain_orb: dep-override denial tests updated to the 404 contract. - test_public_links.py: owner skip-guards tolerate 404. - test_email_auth.py: tighten the unknown-email assert to ==200 (dead 429 branch removed) and assert no expires_in_seconds leaks. Verified in a py3.12 venv: new file 16/16, test_28+test_brain_orb 104/104. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs: record enumeration-uniformity contract for #186 - architecture.md Invariant #8: add the self-uniform (never 404-then-403) rule and the uniform-404 dependency behavior + MCP mirror. - requirements/auth.md §2.1: email-request identical body/status/timing. - requirements/security.md §20.7: new subsection recording #186. - feature-flows/email-authentication.md: revision-history row for the request-code change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(feature-flows): sync #186 enumeration-uniformity contract - feature-flows.md: Recent Updates row for #186. - agent-permissions.md: uniform-404 dependency behavior, MCP checkAgentAccess uniform reason + owner-username removal, refreshed error-handling table + self-uniform contract note. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * test(auth): nevermined helper enumeration-uniformity + equal-query-count read path (#186) Close the sibling-path gap for the nevermined router's own module-level access helpers (they predate the dependency helpers): - _require_read_access now evaluates existence AND access unconditionally (no short-circuit) so the query count — hence timing — is identical for the non-existent and the existing-but-inaccessible case, matching _require_write_access and the dependencies.py helpers (#186 equal-query-count discipline). - Add real-DB tests asserting both helpers raise a byte-identical uniform 404 for a missing vs inaccessible agent, admin-on-nonexistent still 404s, and the write helper keeps owner-only enforcement (shared reader reads but cannot write) — guards the sibling codepath the dependency-helper tests don't reach. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(avatar): path-component barrier + stabilize #186 enumeration test (#186) Two order-dependent CI failures on this branch, both test/analysis-level (no product behaviour change to the enumeration fix): 1. backend-unit-test regression diff (seed 99999): test_186's _agent_exists probe resolved a truthy leaked Mock. A sibling unit test leaves services/services.docker_service as Mocks in sys.modules; _no_docker's dotted-string monkeypatch landed on a different auto-mock than the one `from services.docker_service import get_agent_by_name` resolves, so a non-existent agent read as existing and the admin-nonexistent 404 never fired. Capture the real modules at collection and pin them into sys.modules (monkeypatch.setitem, auto-restored) before stubbing the probe. Verified green across all three CI seeds. 2. CodeQL: 18 new py/path-injection alerts in avatar.py. Moving the inline db.get_agent_owner() check into the OwnedAgentByName dependency removed the barrier CodeQL saw on agent_name before AVATAR_DIR / f"{agent_name}...". Add _safe_avatar_component(): an explicit single-path-component basename guard at the top of generate/regenerate/delete — defense-in-depth (traversal is not reachable given OwnedAgentByName + charset-restricted names, but the constraint now lives in a callee CodeQL can't trace) with a uniform 404 that preserves the #186 no-existence-oracle contract. +10 barrier unit tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(avatar): normpath+within-root path barrier CodeQL recognizes (#186) The first attempt (_safe_avatar_component, an os.path.basename guard in a helper) did not clear the 18 py/path-injection alerts: basename is not a CodeQL-modeled sanitizer and the guard sat in a callee, so CodeQL saw tainted-in/tainted-out — the same cross-function-barrier blind spot that hiding the check in OwnedAgentByName created. Replace it with _avatar_path(agent_name, suffix): os.path.normpath(join(base, …)) then require the result stay under AVATAR_DIR (the CodeQL SafeAccessCheck barrier documented in the py/path-injection help). A barrier guard severs taint flow even from inside a helper, since the guarded return only runs when contained. Route the 11 path sites in the four flagged functions (generate/regenerate/delete + _generate_emotions_background) through it; the unflagged GET handlers are left as-is to keep this scoped to #186. Produces byte-identical paths for real (charset- restricted) agent names; uniform 404 on escape preserves the no-existence-oracle contract. Barrier tests updated to assert containment/escape. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(avatar): match CodeQL SafeAccessCheck path barrier verbatim (#186) Prior barrier used `full != base and not full.startswith(base + os.sep)`; the `base + os.sep` expression and compound condition didn't match CodeQL's SafeAccessCheck guard model, so the 18 py/path-injection alerts persisted. Align _avatar_path with the exact pattern from the py/path-injection query help: fullpath = os.path.normpath(os.path.join(base, name)) if not fullpath.startswith(base): raise ... Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Andrii Pasternak <anpast31@gmail.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com>

* fix(agent): make agent /tmp tmpfs size configurable via AGENT_TMP_SIZE (#1231) (#1233) Agent containers mounted /tmp as a hardcoded 100 MB noexec,nosuid RAM-backed tmpfs. It fills easily — e.g. `gh` CLI install artifacts (~38 MB) that hardcode /tmp and bypass the #1098 TMPDIR redirect — after which every /tmp write fails with "No space left on device", including git's commit scratch, so autonomous scheduled runs "complete" but silently fail to persist. The size being a literal meant operators couldn't tune it without a code change + base-image rebuild. - capabilities.py: AGENT_TMPFS_MOUNT size now read from AGENT_TMP_SIZE (env on the backend service, which builds the agent mount spec), default 512m, validated `^\d+[mg]$` with empty/invalid → default. noexec,nosuid stay hardcoded — only size is configurable, and it stays bounded (counts against the agent memory cgroup). Single source of truth, so create (crud.py) and recreate (lifecycle.py) can't drift. - Wire AGENT_TMP_SIZE=${AGENT_TMP_SIZE:-512m} on the backend service in both docker-compose.yml and docker-compose.prod.yml; document in .env.example. - architecture.md Container Security: note the now-configurable size. - tests/unit/test_1231_agent_tmp_size.py: default, valid m/g, case-fold, invalid→default, and the security flags are never dropped. Mount specs are creation-time: existing agents pick up a new size on recreate, not restart. Builds on #1098 (TMPDIR redirect) — closes the gap for tools that hardcode /tmp. The agent-side git-sync silent-persist-failure is a separate issue in the abilities repo, per the ticket. Related to #1231 Co-authored-by: Eugene Vyborov <1073874+vybe@users.noreply.github.com> * feat(ui): per-schedule performance scorecards on Agent Detail (#1115) (#1149) Surface per-schedule performance on the Overview tab and the Schedules tab, both from a SINGLE compact aggregate (no N per-schedule round-trips) — extends #1107 (Overview) and generalises #868 (per-schedule deep analytics). Backend: - db `get_agent_schedules_summary(agent, hours)` — one rollup row per non-deleted schedule (zero-run schedules included): terminal success_rate (success / (success + failed[incl. error]); None when zero terminal), NULL-skipping avg_duration_ms, cost_total, context_avg, tool_call_total (parsed over newest 5,000 rows agent-wide, tool_calls_sampled flag), and last-run outcome. Cheap grouped SQL; iso_cutoff window (Invariant #16). - GET /api/agents/{name}/schedules/analytics-summary?window=7d|14d|30d (AuthorizedAgent). Declared BEFORE /{schedule_id} in routers/schedules.py so the literal segment isn't captured as a schedule_id (Invariant #4) — putting it in analytics.py would be shadowed (schedules_router mounts first). - models: ScheduleSummaryRow + AgentSchedulesSummaryResponse (Invariant #14). Frontend (single fetch, two consumers — Invariant #7): - executions.js fetchSchedulesSummary, cached per ${name}:${window} like fetchAgentAnalytics. - OverviewPanel: "Schedules performance" section, honors the existing 7/14/30d window selector, each row deep-links to the Schedules tab; hidden at zero. - SchedulesPanel: inline mini-stats per row (success rate, avg duration, runs, last-run dot) — badge style, no new chart/modal — from the same call. Tests: tests/unit/test_1115_schedules_summary.py (6) — terminal success rate, NULL-skip avg, tool-call total, zero-run-still-appears, soft-delete excluded, out-of-window excluded. Full analytics suites green (30 passed). Frontend prod build clean; endpoint verified live across 7/14/30d windows. Related to #1115 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <1073874+vybe@users.noreply.github.com> * feat(ui): in-app bug reporting from the floating Help widget (#1116) (#1283) * docs(readme): document the Trinity Ops Agent and PostgreSQL backend/migration (#1290) Adds a top-of-README callout recommending PostgreSQL for production (SQLite remains the zero-config dev default, opt-in via DATABASE_URL, #300), links the public Trinity Ops Agent (trinity-ops-public) for instance operations, and documents migrating existing SQLite instances via its /migrate-to-postgres skill. Also adds a Database section, a DATABASE_URL env row, and an ops-agent entry in the docs index. Co-authored-by: Eugene Vyborov <eugene@beingluminous.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * refactor(reliability): unify the SUB-003 auth-class failure classifier into one shared module (#1088) (#1297) The `is_auth_failure` + `AUTH_INDICATORS` + `NON_AUTH_KILL_MARKERS` (#904) logic was duplicated inline in `subscription_auto_switch.py` and `scheduler/service.py`, kept in sync by a hand-written "keep these lists in sync" comment — exactly how the #904 kill-marker bug class re-appears. Consolidate into one canonical module: - New `src/backend/services/failure_classifier.py` — canonical, pure-stdlib classifier (55 lines). `subscription_auto_switch.py` now re-exports `is_auth_failure` unchanged, so existing importers (`routers/chat.py`, `services/task_execution_service.py`) and their test patch targets keep working. - New `src/scheduler/failure_classifier.py` — byte-identical vendored mirror. The scheduler runs in a separate container and cannot import `backend.services`; it uses the classifier for log-labelling only (picks the `logger.error` wording, never gates a switch). The agent-runtime classifier in `error_classifier` is intentionally NOT merged — it diverges semantically and stays kill-safe by `_classify_signal_exit` precedence (D4). - Byte-identity is enforced by `tests/unit/test_904_sigkill_no_false_auth.py::TestBackendSchedulerParity`; the re-export is pinned by `TestBackendReExportGuard`. No hand-sync. Pure structural refactor, no behavioral change (verified by SHA-256 equality of the two copies and line-for-line comparison vs the deleted code). The test rewrite also drops the prior `exec(compile(...))` source-slicing in favour of `importlib` path-loading, removing the only injection primitive in scope. Tests: 19/19 pass in `test_904_sigkill_no_false_auth.py`. CSO --diff: CLEAR (docs/security-reports/cso-diff-2026-06-21.md). Refs #1088 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(orchestration): pull-pilot routing for agent→agent MCP chat behind default-OFF flag (#946) (#1293) * feat(orchestration): pull-pilot routing for agent→agent MCP chat behind default-OFF flag (#946) Phase 2 PoC for pull/work-stealing (Epic #1045, umbrella #1081). When MCP_AGENT_CHAT_PULL_ENABLED is ON, a sequential agent→agent (scope='agent', non-self) chat_with_agent is routed by the MCP server through the durable async /task path instead of the synchronous held /chat; the caller gets an immediate {accepted|queued, execution_id} receipt and polls get_execution_result. scope='user', self-tasks, and parallel=true are unchanged. Default OFF — flag flip + MCP routing revert is the whole rollback. - config.py: canonical MCP_AGENT_CHAT_PULL_ENABLED registry entry (both services read the SAME env key, so a single-.env deploy can't drift). - settings.py: surface mcp_agent_chat_pull_enabled in /api/settings/feature-flags (auth-gated, observability-only — not a UI surface). - chat.py: release the idempotency claim on the two /task dispatch-breaker-open (CircuitOpen) deny paths, mirroring /chat and CapacityFull (T5 fix) — without it a breaker-open reject silently blocks same-key retries for 24h. - mcp-server: scope-based pull routing + D8 dispatch-mode idempotency token so a flag flip can't replay a wrong-shape snapshot across endpoints; startup log of the routing mode for the soak's control/treatment window. - tests: chat.test.ts (routing fork + key behavior), test_946_task_idempotency_on_deny.py (deny-path claim release), feature-flag exposure tests. - docs: ACTOR_MODEL_POSTCARD (#945 resolved), PULL_PILOT_946_SOAK harness + go/no-go record, CSO diff audit (CLEAR), TARGET_ARCHITECTURE/architecture updates. Refs #946 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(feature-flows): document pull-pilot routing (#946) + AGENT_TMP_SIZE tmpfs (#1231) Sync feature-flow docs with recent changes: - agent-to-agent-collaboration.md: new Pull-Pilot Routing (#946) section — flag-gated MCP routing fork to the durable async /task path, poll-for-result receipt contract, D8 idempotency route token, feature-flag exposure, and the T5 /task dispatch-breaker-open deny-path claim release. - container-capabilities.md: refresh stale tmpfs facts — agent /tmp size is now operator-configurable via AGENT_TMP_SIZE (default 512m, noexec,nosuid fixed), plus the TMPDIR=/home/developer/.tmp heavy-scratch redirect (#1098). - feature-flows.md: add Recent Updates index rows for #946 and #1231. Refs #946 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com> * feat(agent): runtime data_paths with portable export/import (#1169) (#1294) * feat(agent): runtime data_paths with portable export/import (#1169) Declare an agent's runtime data (SQLite DBs, datasets) under data/ on the already-durable home volume — no separate volume, no platform schema change. - template.yaml `data_paths:` surfaced by template_service (github + local) and materialized at creation by crud.py -> git_service.materialize_data_paths: writes ~/.trinity/data-paths.yaml and appends data/ + entries to the agent's own .gitignore (idempotent). Opt-in; empty list is a no-op. - S4 persistent-state and data_paths now share one extracted heredoc/list primitive (materialize_trinity_yaml_list / _read_trinity_yaml_list). - New routers/agent_data.py: POST /data/export (stream | base64, 413 over cap, manifest-only tar when data/ missing) and POST /data/import (proxies to the agent-server restore primitive; data/** allowlist + traversal guard; Idempotency-Key). Both serialized per agent by a cross-worker Redis op lock. - MCP tools export_agent_data / import_agent_data (Invariant #13). - Validation checks DP-001..DP-005 in agent-validation-spec. - Docs: architecture, requirements, feature-flows index + agent-data-volumes flow, agent guide; CSO diff audit report (0 critical/high). Tests: ~30 unit + TestClient tests (export/import endpoints, allowlist, gitignore, template surface). PR2 (scheduled snapshots + pre-snapshot quiesce hook + retention/cascade) deferred. Closes #1169 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(agent-data): satisfy sys.modules pollution lint in #1169 tests The two new data_paths test files copied the baselined `patch.dict` + bare `del sys.modules[...]` loader from test_persistent_state_allowlist.py, which the sys.modules pollution lint flags as NEW (non-baselined) violations. Adopt the blessed snapshot/restore exception (precedent: test_telegram_webhook_backfill.py): declare a top-level `_STUBBED_MODULE_NAMES` list + an autouse `_restore_sys_modules` fixture, and install the stubs / evict the cached module directly (the fixture owns restoration). Removes the bare `del sys.modules[...]` entirely rather than hiding it. Drop the now-unused `patch` import from the gitignore test. Lint passes (no new violations); both files' 16 tests still green; no cross-file leakage. Refs #1169 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(feature-flows): sync recent changes — #1231 tmpfs, #1115/#1231 index rows Fix container-capabilities.md for the now-configurable agent /tmp tmpfs (#1231): default 100m → 512m via AGENT_TMP_SIZE, and correct the stale full_capabilities ternary excerpts to the shared AGENT_TMPFS_MOUNT constant (noexec,nosuid always applied, both modes). Add Recent Updates index rows for the per-schedule performance scorecards (#1115) and the tmpfs-size fix (#1231); the #1169 and #1116 rows already shipped in-commit. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com> * fix(security): authenticate the in-container agent server on the shared agent network (#1159) (#1292) * fix(security): authenticate the in-container agent server on the shared agent network (#1159) The in-container agent server (:8000) had zero inbound auth on trinity-agent-network: any agent could read a sibling's .env secrets or run arbitrary Claude on it. Every backend->agent call now carries a per-agent X-Trinity-Agent-Token = HMAC-SHA256(AGENT_AUTH_SECRET, "trinity-agent-auth:v1:"+name), verified by a pure-ASGI middleware on all HTTP and WebSocket routes (constant-time compare; only /health exempt). - Derive-don't-store: the master AGENT_AUTH_SECRET lives only in the backend env (auto-generated by start.sh like SECRET_KEY); each container receives only its own token, so a compromised agent cannot compute a sibling's. Fail-closed -- derive raises on an empty secret. - Callers route through services/agent_auth.py (agent_httpx_client / build_agent_auth_headers / merge_auth_headers); a static guard test fails any new raw agent-{name}:8000 caller that bypasses them. - Removed the dead, unauthenticated /ws/chat route (ran arbitrary Claude) and the agent server's wildcard CORS (internal-only). - Grace path for old images: empty TRINITY_AGENT_AUTH_TOKEN -> allow; check_agent_auth_token_env_matches forces a one-pass recreate to inject. - Retired the unused src/scheduler/agent_client.py. Tests: unit (matcher, middleware, header guard, derivation) + security isolation test. CSO diff audit in docs/security-reports/cso-diff-2026-06-20.md. Closes #1159 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(feature-flows): document agent-server authentication (#1159) + sync recent flows Add a feature-flow doc for the in-container agent-server inbound auth shipped in this PR, and sync the index with two recent merged changes. - New feature-flows/agent-server-authentication.md: end-to-end trace of the derived X-Trinity-Agent-Token (HMAC over AGENT_AUTH_SECRET), the pure-ASGI middleware enforcing it on every HTTP/WS route, fail-closed vs grace path, recreate reconciliation, and the migrated callers + static guard. Added to the Authentication & Security catalog in the index. - container-capabilities.md: refresh the stale /tmp tmpfs size (was a hardcoded 100m) to the configurable AGENT_TMP_SIZE (default 512m, #1231). - Recent Updates rows for #1159, #1231, and the previously-missing #1115. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com> * docs(voip): genericize moved-issue reference in feature-flow #1039 (configurable data-retention) moved to the private enterprise tracker; replace the now-private issue number in voip-telephony.md with a generic description so the public doc doesn't deep-link a private issue. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(agents): server-side compatibility validation with auto-fix (#668) Run ~100 best-practice checks (11 categories) against a running agent's workspace, surfaced non-blocking in the Overview tab with one-click auto-fix for the 10 gitignore checks, plus an MCP tool. - services/compatibility/ package (spec/collector/static_checks/ai_checks/fixes): ONE docker exec -> in-container python -> JSON snapshot (secret files existence-only, size/binary caps); pure STATIC checks (HARD-only) + category-batched AI checks (Haiku, iterate-expected, fail-open, capped at SOFT, secret-redacted); runtime-aware (claude-only checks skipped for Codex/Gemini). - GET/POST endpoints (read AuthorizedAgentByName; fix OwnedAgentByName, gitignore only, per-agent Redis lock, atomic write, uncommitted until next sync; include_ai path rate-limited). agent_compatibility_results table (dual-track SQLite + Alembic) persists the latest snapshot; cascade/rename via AGENT_REFS. - CompatibilityPanel.vue (two-phase fetch, grouped checklist, per-check fix, re-run) in OverviewPanel; get_agent_compatibility_report MCP tool. - 35 fixture-driven unit tests; spec sync-tested against docs/agent-validation-spec.md. Persistence departs from the issue's "no DB table" note so AI verdicts show without re-spend + enable fleet aggregation (see requirements section 41). Fixes #668 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(compat): remove polynomial-ReDoS in secret-assignment regex (#668) CodeQL py/polynomial-redos (high): `_ASSIGN_RE` captured the value as `[ \t]*(.+?)[ \t]*$`. The lazy `.+?` and the surrounding `[ \t]*` can both match a tab, giving polynomial backtracking when `_redact()` runs the pattern over up to 48 KB of agent-supplied file text. Capture the value greedily to end-of-line (`(.*)$`) and let the callers strip — both `_looks_placeholder()` callers already `.strip()`, so secret detection and redaction are behaviourally identical (verified: `=`, `:`, `export`, and indented forms still match). 35 unit tests pass. * feat(sso): OSS gated surface for enterprise SSO (OIDC) (#32) Companion to trinity-enterprise#36. OSS carries only the entitlement-gated surface; all SSO logic lives in the private submodule. - Login.vue: "Sign in with <IdP>" buttons (shown only when the `sso` feature is entitled and a provider is enabled), plus OIDC callback-fragment handling (`/login#sso=ok|mfa|error`) — reuses the existing 2FA challenge UI when the IdP login still requires a local second factor. - stores/auth.js: completeSsoLogin() (reuses _finalizeLogin / _setMfaChallenge) + fetchSsoProviders() (empty in OSS-only builds — endpoint 404s). - Settings.vue: admin-gated "SSO" tab → SsoPanel.vue (provider CRUD + test + policy). Gated by enterpriseStore.isEntitled('sso'), same as the 2FA tab. - Bump enterprise submodule to the SSO module commit. - docs: architecture enterprise-modules row + requirements §40 (SSO/OIDC). No new backend dependency (python-jose + httpx already in the image) and no OSS Python changes — the mint/whitelist/mfa seams already exist. Stacked on feat/5-2fa-totp (reuses the OSS mfa_gate + 2FA challenge surface). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore(sso): bump enterprise submodule to OIDC hardening (#32 review) Pulls in the email_verified / issuer-pinning / login-CSRF fixes (trinity-enterprise 87c8f97). OSS gated surface unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(planning): note incubating goal-directed direction; reword voip flow Add an "Incubating Directions (Not Yet Decided)" section to TARGET_ARCHITECTURE.md capturing the goal-directed control-surface idea (Objective + policies + roster + externally-measured evals), explicitly bounded by CLAUDE.md §8 and sequenced after the pull migration + #300. Incubating in trinity-enterprise#27. Reword the voip-telephony flow note to drop a stale #1039 reference in favor of describing the LOG_* data-retention no-op class directly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(security): add CSO 2026-06-21 posture report Routine /cso full-audit posture report (Phases 0–14, daily 8/10 gate). Follows the docs/security-reports/ convention; no real secrets reproduced. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(user-docs): video library + per-page links, v0.6.1 What's New, sync dev features - Add videos.md (35 published videos, newest-first by topic) and a README Watch section - Add 'Watch' callouts to 32 feature pages linking the most relevant, newest videos - Add user-facing whats-new/v0.6.1.md (translated from release notes; no issue numbers) - Document dev-only features: agent runtimes (Claude Code/Codex/Gemini CLI, #1187), agent data paths + export/import (#1169), compatibility validation (#668), in-app bug reporting (#1116), subscription hot-reload (#1089), pull-pilot routing (#946), configurable AGENT_TMP_SIZE (#1231), Postgres migration-runner groundwork (#1160) - Index agent-runtimes, agent-data, and the previously-orphaned agent-session pages Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(setup): first-run operator intake + admin email login (abilityai/trinity-enterprise#38, #82) Capture an optional operator email/company at first-run setup with an explicit, unchecked-by-default opt-in to "occasionally receive important security & product updates", submitted once to a new /v1/operator-intake endpoint on #1116's Cloudflare intake app. The same email binds as the admin's sign-in identity so the operator can log in with email + password — no verification email is sent (a fresh install has no Resend key; the email is bound, not code-verified). The code-based email second factor stays Phase 2 on the existing mfa_gate seam. - backend: operator_intake_service (fire-and-forget, at-most-once via a system_settings marker, DO_NOT_TRACK aware, owns installation_id); setup endpoint captures profile + binds admin email; authenticate_user resolves the admin by username OR registered email (password guard blocks code-only users); PUT /api/users/me/email for the existing-admin transition - frontend: SetupPassword email/company + consent checkbox; Login "username or email" field; Settings -> General "Admin sign-in email" card - config: OPERATOR_INTAKE_ENABLED / OPERATOR_INTAKE_URL (+ .env.example) - docs: requirements section 43, architecture catalog, first-time-setup feature flow - tests: 16 unit tests (intake idempotency/guards, email-login resolution, setup) Fixes abilityai/trinity-enterprise#38 Fixes #82 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(feature-flows): index row for first-run intake + admin email login (trinity-enterprise#38, #82) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(setup): de-ambiguate email regex to clear CodeQL polynomial-ReDoS (#82) The _EMAIL_RE pattern duplicated into setup.py and users.py had two [^@\s]+ atoms around the literal \. that both also match '.', giving the engine many ways to place the dot and backtracking polynomially on user-controlled email input (CodeQL alerts #211, #212). Constrain only the final segment to [^@\s.]+ (no dot) so the trailing \. can align with exactly one position -> linear matching. Behaviour is unchanged: multi-subdomain addresses still validate; an 80k-char pathological input now resolves in ~2ms. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(credentials): curated credential file-type injection (SA keys, certs, SSH, binary) (#1305) * feat(credentials): curated credential file-type injection — SA keys, certs, SSH, binary (enterprise#11) Widens CRED-002 injection from the fixed 3-path exact allowlist (.env/.credentials.enc/.mcp.json) to a curated set of credential file *types*, without reopening the arbitrary-path RCE surface (#183/#590/#598). - New services/credential_paths.py — single-source policy: ALLOW (.config/gcloud/**, .kube/config, *.pem/*.key/*.crt/*.cert/*.p12/*.pfx, .ssh/id_*, + existing exact set) with deny-precedence over anything executed/sourced at startup (shell rc, CLAUDE.md/AGENTS.md/.claude/**, .mcp.json.template, .ssh/authorized_keys/config, .git*, bin/**) and `..`/absolute traversal. Vendored byte-identically into the agent image (Invariant #5) with a parity test. - Agent-server hardening: the inject + update file loops now enforce the policy AND a resolve-under-home traversal guard the original write path lacked; parent-dir creation + chmod 0o600 preserved. New GET /api/credentials/list for export discovery. - Binary-safe: inject carries files_b64 (base64); agent writes via write_bytes. .credentials.enc gains a v2 {files, files_b64} envelope (legacy flat archives still decrypt); encrypt/decrypt stay flat for the single-secret callers (SIEM/2FA/SSO). - Export now captures the FULL injected set (via /list) + binary, not just the 2 defaults. - Three surfaces in sync (Invariant #13): MCP inject_credentials gains files_b64; frontend CredentialsPanel gains a file-upload affordance (text vs base64 auto-detected). - Tests: allowlist test now exercises the REAL policy (newly-allowed + still-blocked), + credential_paths parity test + binary archive round-trip test. 61 pass. - docs/memory/architecture.md: credential-path policy documented. Related to Abilityai/trinity-enterprise#11. Loosens a deliberately-tight boundary — run /cso on the diff before merge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(credentials): close /cso findings on the injection widening (#11 review) Security review of the widening surfaced one HIGH regression + hardening items; all fixed here. #1 (HIGH, RCE): the #598 .mcp.json content-validation guard was bypassable via the new files_b64 (binary) channel — validate_mcp_config only checked `files`, so `files_b64={".mcp.json": base64(<stdio-command MCP server>)}` skipped it and configured an RCE MCP server on the target agent. Fix: .mcp.json may only arrive as TEXT (files), where it is validated; rejected in files_b64 at the backend inject router AND the agent-server write helper. #2 (defense-in-depth): import/auto-import wrote decrypted archives via the agent-server /inject layer only. Added validate_credential_set() (curated path policy + .mcp.json content + no-binary-.mcp.json) on the backend import boundary so enforcement is dual-layer as the issue mandates. (Archives are AES-GCM with the server key, so a forged archive wasn't practical — but the layer belongs.) #3: .ssh/ is now locked to id_* only — a stray *.key/*.pem under .ssh is no longer accepted (policy was previously broader than the "SSH keys = id_*" intent). #4 (noted): .config/gcloud/** can hold a google-auth executable credential_source; only honored under non-default GOOGLE_EXTERNAL_ACCOUNT_ALLOW_EXECUTABLES=1. Documented in credential_paths.py. +6 regression tests (169 pass). CSO report: docs/security-reports/cso-2026-06-22-11-diff.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(credentials): exclude vendor dirs from cert globs + accurate export count (#11 live test) Found while testing PR #1305 against a real local instance: 1. Over-capture: the broad *.pem/*.key/*.crt globs matched bundled CA files (e.g. .local/.../site-packages/certifi/cacert.pem), so export's /list walk swept vendored cert material into .credentials.enc. Added node_modules, site-packages, .local, .venv/venv, .cache, go/pkg to the deny-list (both root and nested forms) so cert globs only catch real credential files. 2. export's files_exported count re-read just the 2 default files (reported 1 while the archive actually held 5). export_to_agent now returns the true captured count; dropped the redundant stale read. Verified end-to-end on a live agent: allowed types inject (text+binary, 0600, parent dirs), blocked paths 400 (incl. .ssh non-id_*, .mcp.json-via-files_b64, weaponized .mcp.json text), and binary round-trips through export→import with matching sha256. +5 regression tests (72 pass). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(security): annotate CSO 2026-06-21 findings as remediated; drop stale voip hunk Two review-driven fixes ahead of the v0.7.0 cut: - Annotate the CSO posture report (.md + .json) with post-audit remediation status. The report audited `main` pre-cut and listed F1/F2/F3 as open VERIFIED findings; they are already remediated on `dev` and ship in v0.7.0: - F1 (unauth agent-server) -> #1159 X-Trinity-Agent-Token middleware - F2 (fastmcp -> hono/undici) -> #1255, #1289; fastmcp ^4.3.0 - F3 (form-data CRLF via axios) -> #1254 - F4/F5/F8 exploit path closed by #1159 (auth gate) Adds a top-of-report banner, per-row status tags, per-finding notes, and a machine-readable `remediation_status` block in the JSON. Avoids publishing a stale "open CRITICAL + exploit" to a PUBLIC repo without its fix context. - Drop the voip-telephony.md reword: it is superseded by already-merged #1301, which made the identical `#1039` -> `LOG_*` change on `dev`. Restoring to merge-base removes the redundant/conflicting hunk from this PR. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore: set version to 0.7.0 * feat: streamline first-time setup wizard (abilityai/trinity-enterprise#49) Drop the log-copied setup token, require an admin email, and rebuild the first-run page as a welcoming animated welcome screen. Backend (routers/setup.py, main.py): - Remove the setup-token machinery entirely (ensure_setup_token / clear_setup_token / Redis-shared token + the main.py startup emission). Setup no longer depends on Redis — the admin write goes straight to SQLite. - Make admin email REQUIRED (sign-in identity): missing -> 422 at the model layer; blank/typo -> 400, validated before any write so setup never half-completes. Password complexity (OWASP ASVS 2.1) still enforced. - get_setup_status keeps setup_available:true for frontend back-compat. Frontend (SetupPassword.vue): - Full redesign: dark branded hero with an animated orbiting fleet constellation (Trinity mark core + agent nodes on three rings), split layout (stacks on mobile), prefers-reduced-motion aware. - No setup-token field; email required; order email -> password (+confirm) -> company -> updates opt-in. Removed the Redis-wait panel + polling. Security tradeoff (chosen: accept + document): removing the token leaves the unauthenticated first-run window with no proof-of-control. Documented as an operator responsibility (deploy behind a tunnel/VPN until setup completes) in docs/DEPLOYMENT.md Security Recommendations; endpoint still self-disables after first success. See docs/security-reports/cso-diff-2026-06-23.md (F1). Docs: DEPLOYMENT.md security note, architecture.md, requirements.md (§15.2/§43), feature-flows/first-time-setup.md. Tests: remove obsolete test_1165_setup_token_shared.py; update test_setup.py (no token, email required) and test_setup_operator_profile.py (email required, model-layer + blank/invalid rejection). 7 operator-profile unit tests pass; new contract verified live (422/400 negative paths). Fixes abilityai/trinity-enterprise#49 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(setup): full-bleed setup screen via normal flow, not position:fixed The redesigned first-run page used `position:fixed; inset:0` for its root. On wider viewports this left a band of the light `#app` (bg-gray-100) background showing through on the right/bottom — a fixed root is clipped to the nearest transformed/contained ancestor instead of the viewport, so its coverage isn't guaranteed. Switch the root to the original component's proven normal-flow approach (`position:relative; width:100%; min-height:100vh`), which fills the full-width `#app`, and make the decorative aurora/grid `position:absolute` within it. Verified covering the full viewport at 2560x1440 (light mode, the repro case) and stacking correctly at 430px. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(tests): defer routers.setup import so unit collection can't be corrupted The CI backend-unit regression gate runs `cd tests && pytest unit/` (the whole unit suite). test_setup_operator_profile.py imported `routers.setup` at module (collection) time; that import — pulling in database/dependencies/services and their many `utils.*` leaves — failed/perturbed sys.modules during collection and INTERRUPTED the entire `unit/` collection (head collected ~2 of 2734 → the diff gate flagged it as a new failure). Defer the `import routers.setup` to a cached `_get_setup()` accessor used inside the tests, so module collection imports only stdlib/pytest/fastapi/pydantic and can never corrupt the suite. `_get_setup()` also spec-preloads the backend `utils.*` leaves (helpers/errors/credential_sanitizer/password_validation/ url_validation/image_optimize) the same way conftest preloads `utils.helpers`, without touching `sys.modules["utils"]`, so the import resolves cleanly at run time regardless of harness utils state. Verified with the exact CI command (`cd tests && pytest unit/ --co`): the full suite now collects 2734 items with no interruption, and the 7 setup tests pass. No conftest changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(tests): drop sys.modules preload — plain lazy import (passes #762 lint) The previous commit's `_get_setup()` spec-preloaded backend utils leaves via `sys.modules[...] = …` / `.pop`, which tests/lint_sys_modules.py (#762) bans outside conftest. It's also unnecessary: in the backend-unit gate (`cd tests && pytest unit/`), tests/unit/conftest.py already installs src/backend/utils as the canonical `utils` package, so a plain lazy `import routers.setup` resolves the backend `utils.*` leaves natively. Simplify `_get_setup()` to a cached plain lazy import — no sys.modules mutation. Verified: lint clean (no new violations), `pytest unit/ --co` collects 2734 with no interruption, and the 7 setup tests pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(tests): update #858 guards for setup-token removal (#49) Removing the setup token (trinity-enterprise#49) deleted `routers/setup.py::ensure_setup_token` and the lifespan token emission, so two #858 regression guards asserted gone behavior and failed in the backend-unit gate: - test_ensure_setup_token_logs_token_via_logger_warning - test_lifespan_emits_setup_token_via_logger_before_event_bus The #858 invariant itself is intact: the lifespan still emits the first-run notice via `logger.warning` (not print), after setup_logging() and before event_bus.start(). Replace the token-specific guard with one that matches the new FIRST-TIME SETUP warning by content + ordering, drop the now-obsolete ensure_setup_token guard, and remove the unused BACKEND_SETUP constant. The Dockerfile PYTHONUNBUFFERED parity checks and the no-print-in-lifespan guard are unchanged. 4 passed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(whatsapp): deliver ChannelResponse.files as Twilio MediaUrl (#1315) WhatsApp agents can now send files to users. send_response delivers ChannelResponse.files as Twilio MediaUrl attachments (one message per file, text first), reaching parity with the Slack adapter. - New create_share_from_bytes() persists in-memory bytes through the FILES-001 pipeline (MIME-blocklist/quota/disk/DB) and mints a public ?sig= URL; both it and create_share now share the extracted _persist_and_register helper. - Per-agent file_sharing_enabled gate; 1h share TTL (cleanup reaper purges). - Caps (image/audio/video ~5MB, documents ~16MB) on the detected MIME; graceful text-link fallback when public_chat_url is unset/non-HTTPS, the MIME is unsupported, or the file is oversized — never silently dropped. - Per-file isolation: a rejected/failed file never aborts the text or siblings. - 42 unit tests; requirements.md + whatsapp-integration.md updated. Fixes #1315 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(whatsapp): webhook routes to backend, not frontend (#1281) (#1316) The WhatsApp panel's deployment-prerequisite notice told operators to route /api/whatsapp/webhook/* to the "frontend service". That path is a backend FastAPI route (Twilio HMAC-verified); pointing tunnel ingress at the static SPA silently drops inbound messages. Corrected to the backend service (http://backend:8000), matching the cited PUBLIC_EXTERNAL_ACCESS_SETUP.md. Related to #1281 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(ui): loading skeletons for Dashboard graph & timeline (#1266) (#1312) The initial fleet/metrics load can take 20s+ on 10+ agent fleets (#1265); until now the Dashboard rendered the "No agents" empty state (or blank timeline) during that wait, so the UI looked frozen/broken. - New reusable `SkeletonLoader.vue` (dark-mode aware, accessible role=status/aria-busy, reserves space to avoid layout shift) with `rows` (timeline/list) and `nodes` (collaboration graph) variants. - `stores/network.js`: add `loading` (defaults true so the first paint is a skeleton, not the empty state) + `loadError` (distinct failed-load state), toggled in `fetchAgents` (finally-cleared so a failure never shows an infinite skeleton). - `Dashboard.vue`: graph canvas and timeline now render skeleton → error → empty → content off those flags. Loading shows immediately on nav; error states offer a Retry (reuses `refreshAll`). Frontend-only; pairs with the backend perf work in #1265. `vite build` passes. Related to #1266 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(db): set SQLite end-of-support to September 1, 2026 + Postgres migration notes (#1278) (#1314) Records the firm SQLite end-of-support date and the SQLite → PostgreSQL migration announcement/guidance. Documentation/decision only — SQLite code removal stays with the migration work (#300/#1183/#746). - docs/migrations/SQLITE_TO_POSTGRES.md (new): authoritative guide — EOL date, what changes and when, switching a fresh deployment (DATABASE_URL + postgres profile), migrating an existing deployment (backup-first; no turnkey data-copy tool yet — honest cutover options), verification, and release-notes copy. - docs/releases/v0.6.2.md (new, draft): EOL announcement section linking the guide, seeding the next release notes. - docs/planning/TARGET_ARCHITECTURE.md + docs/memory/architecture.md (Invariant #3): reference the EOL date so it's discoverable outside the release. - Cross-links the in-repo reminder companion (#1279). Related to #1278 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: stop disclosing enterprise functionality in public docs (trinity-enterprise#45) (#1311) * docs: stop disclosing enterprise functionality in public docs (trinity-enterprise#45) The public repo documented the full design, feature catalog, and gating strategy of the paid enterprise tier — a free blueprint of what we monetize and how it's built. This removes that competitive content and keeps only the generic open-core seam public. - Delete 4 strategy/design docs (OSS_ENTERPRISE_SPLIT_RESEARCH, ENTERPRISE_ARCHITECTURE, feature-flows/enterprise-modules, ENTERPRISE_LOCAL_DEV) - architecture.md "Enterprise Modules" table -> neutral seam pointer (no paid-feature catalog, no enterprise_* table DDL, no per-module detail) - requirements.md §35 -> abstract EntitlementService seam (drop the enumerated module list + dead links to the deleted strategy docs) - audit-trail.md: neutralize the lone enterprise-pillar mention - CLAUDE.md: standing rule — enterprise designs live only in trinity-enterprise - CI: enterprise-docs-guard.yml fails the build if live public docs reintroduce paid-feature / private-schema tokens Content is preserved (relocated to the private trinity-enterprise repo, see the companion PR). Git-history scrub of the deleted files + point-in-time historical docs (archive/, releases/, security-reports/) tracked as a follow-up. Related to Abilityai/trinity-enterprise#45 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci(enterprise-docs-guard): add least-privilege permissions block Clears CodeQL actions/missing-workflow-permissions (medium). The guard only checks out and greps, so contents: read is sufficient. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(releases): add 0.7.0 release notes * fix(#1115): port get_agent_schedules_summary to SQLAlchemy Core (Postgres-safe) The #300 SQLAlchemy migration dropped the get_db_connection import from db/schedules.py but left get_agent_schedules_summary (#1115) calling it, so the /schedules/analytics-summary endpoint raised NameError at runtime. Surfaced for the first time by the v0.7.0 release-PR full-suite run (dev pushes only lint). Port the method to get_engine() Core queries like its siblings, and replace the SQLite-only bare-column-with-MAX last-run query with a portable ROW_NUMBER() window so it works on PostgreSQL too. Also refresh the test_login_rate_limit_split config stub, which went stale when auth.py grew a PUBLIC_ACCESS_REQUESTS_ENABLED dependency (trinity-enterprise#10) — 8 collection errors under HEAD. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(voip): per-agent VoIP config panel + persisted voice (abilityai/trinity-enterprise#28) Add the missing per-agent VoIP config UI (agent Settings/Sharing tab) and a persisted per-agent Gemini voice. Shipped as plain OSS gated on the existing voip_available platform flag — NOT entitlement-gated (a UI gate over a money-spending OSS backend would be cosmetic; deliberate simplification of the issue's original "entitlement-gated" framing). Backend: - agent_ownership.voice_name (default Kore) via dual-track migration (SQLite db/migrations.py + Alembic 0004 + schema.py/tables.py). db get/set_voice_name with read-path fallback to Kore for unset/invalid values. - GET/PUT /api/agents/{name}/voice/name (PUT owner-only, validated against GEMINI_VOICE_NAMES). _get_voice_name and voip_service now read the persisted voice instead of the two hardcoded "Kore" sites. - PUT /api/agents/{name}/voip/enabled toggle (owner-only, 404 when no binding); create_binding upsert no longer forces enabled=1 so re-saving credentials preserves a disabled state (call path already refuses disabled bindings). Frontend: - VoipChannelPanel.vue (modeled on WhatsAppChannelPanel) mounted in SharingPanel under voip_available; shared src/constants/voices.js (drift-guarded vs backend); AgentWorkspace picker defaults to the persisted voice; sessions store surfaces voip_available. Tests: tests/unit/test_28_voip_voice_config.py — voice fallback/roundtrip/ invalid->default, enable toggle + re-PUT-preserves-disabled (H3), and the frontend/backend voice-list drift guard. Schema-parity + voip-db guards green. Refs abilityai/trinity-enterprise#28 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * test(voip): HTTP-level endpoint tests for /voice/name + /voip/enabled (#28 review I1) Pre-landing /review flagged that the new endpoints were covered only at the DB layer. Add FastAPI TestClient tests (mount real routers, override auth deps, stub db/voip_service) asserting: - PUT /voice/name: owner-gated (403), 400 on unknown voice, empty clears to default, valid voice persists; GET returns voice_name + available_voices. - PUT /voip/enabled: owner-gated (403), 404 when no binding / when voip flag off, 200 reflecting state with no auth_token leaked. Also capture a durable learning (docs/memory/learnings.md): the schema-parity test is blind to db/tables.py drift — a missing Column there passes parity but breaks at runtime; guard it with a db-accessor unit test that executes a live select on the new column. Refs abilityai/trinity-enterprise#28 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * refactor(docs): agent-readable zero-to-value onboarding (#1280) (#1336) * refactor(docs): agent-readable zero-to-value onboarding (#1280) Make the repo's entry points machine-first so an autonomous agent can self-orient and reach a useful result without a human translating context. - AGENTS.md: add a "Using this file" machine-contract header (declares it the authoritative agent entry point, states the AGENTS/CLAUDE/README boundary, explains how to traverse). Rebuild Route-by-task with an explicit "Done when" zero-to-value signal per persona. - CLAUDE.md: cross-link to AGENTS.md and frame CLAUDE.md as the contributor working agreement (auto-loaded by Claude Code), not the agent landing page. - Fixes from a context-free agent onboarding test (AC#5 validation): AGENTS.md deploy verify no longer assumes an undefined $TOKEN (leads with `trinity agents list`, shows token derivation); deploy section states the running-instance prerequisite; README CLI example adds the `trinity agents list` verify step; docs/CLI.md leads with `pip install trinity-cli` (PyPI) and marks `-e src/cli/` as the from-source/dev variant. Validated by an agent performing a zero-to-value deploy task using only repo files, no human context: self-oriented in 2 hops (README -> AGENTS.md) to a correct deploy+verify answer; friction items above are its findings, folded back in. Repo-root AGENTS.md is hand-authored; the CLAUDE.md->AGENTS.md mirror (#1187) is per-agent-container (startup.sh), so these edits are conflict-free. Related to #1280 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(templates): machine-readable starter-template catalog (#1280) Affordance sweep for agent self-selection. Previously an agent had to `ls` config/agent-templates/ (24 dirs, 7 of them test fixtures) and open each template.yaml to find a starting point. - config/agent-templates/README.md: catalog grouping the 17 real templates (single-purpose: scout/sage/scribe/demo-*/trinity-system; the dd-* due- diligence suite) with one-line affordances, how-to-use, and an explicit "not starting points" list for the test/canary fixtures - AGENTS.md: link the catalog from the Deploy-an-agent section so the zero-to-value path is "pick a ready-made template", not "author from scratch" Related to #1280 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> * fix(tests): un-quarantine and fix the 15 unmasked unit failures (#1103) (#1338) Removes the @pytest.mark.skip quarantines added in #300 and fixes the underlying issues. Each group fixed at root cause, not by matching assertions to current behavior. Environmental (git identity): - tests/unit/conftest.py: set GIT_AUTHOR/COMMITTER_NAME/EMAIL process-wide so in-test `git commit` works on a CI runner with no global git identity ("Author identity unknown"). Fixes test_reset_preserve_state_guardrails (3) and the test_git_pull_branch end-to-end setups. Test-setup bug (production code was correct): - test_git_pull_branch.py: the repos did `git push -u origin main` but `git init` defaults to `master` (no init.defaultBranch), so origin/main never existed and _get_pull_branch correctly fell back to the working branch — the assertions expecting "main" failed. Force `git init -b main` (local + bare). Fixes all 5 (TestGetPullBranch 2 + TestGitPullFromMainEndToEnd 3). Test-isolation bug (assertions were correct): - test_orphaned_execution_recovery.py: shared module-level mocks were reset with plain reset_mock(), which keeps return_value/side_effect — so one test's get_agent_container.side_effect bled into later tests under random ordering, skewing recovery counts ("assert 3 == 2"). Reset with reset_mock(return_value=True, side_effect=True). Stable across 5 seeds. Real lint findings: - docker/base-image/startup.sh: shellcheck now exits 0. Converted the 4 fragile file-iteration loops to `find -print0 | while read` (SC2010/SC2045/SC2044), hardened 8 `cd` with `|| exit 1` (SC2164), split the SC2155 export, and documented-disabled SC2001 on the two regex `sed` lines that ${//} can't express. `bash -n` clean. Un-skips test_startup_sh_shellcheck_clean. backlog (3) and 929 (1) were already un-quarantined on dev (db_harness schema), so no change needed there. Verified: the 11 un-skipped tests pass across multiple random seeds; full unit suite shows no regressions from these changes (the unrelated pre-existing test_1115_schedules_summary / test_admin_email_login failures fail on dev too). Related to #1103 Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> * chore(deps-dev): bump happy-dom (#1326) Bumps the patch-and-minor group in /tests/git-sync with 1 update: [happy-dom](https://github.com/capricorn86/happy-dom). Updates `happy-dom` from 20.10.5 to 20.10.6 - [Release notes](https://github.com/capricorn86/happy-dom/releases) - [Commits](https://github.com/capricorn86/happy-dom/compare/v20.10.5...v20.10.6) --- updated-dependencies: - dependency-name: happy-dom dependency-version: 20.10.6 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: patch-and-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps-dev): bump @types/node in /src/mcp-server (#1327) Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 25.9.3 to 26.0.0. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump fastmcp (#1325) Bumps the patch-and-minor group in /src/mcp-server with 1 update: [fastmcp](https://github.com/punkpeye/fastmcp). Updates `fastmcp` from 4.3.0 to 4.3.2 - [Release notes](https://github.com/punkpeye/fastmcp/releases) - [Commits](https://github.com/punkpeye/fastmcp/compare/v4.3.0...v4.3.2) --- updated-dependencies: - dependency-name: fastmcp dependency-version: 4.3.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump the patch-and-minor group (#1329) Bumps the patch-and-minor group in /src/frontend with 5 updates: | Package | From | To | | --- | --- | --- | | [axios](https://github.com/axios/axios) | `1.18.0` | `1.18.1` | | [@playwright/test](https://github.com/microsoft/playwright) | `1.61.0` | `1.61.1` | | [autoprefixer](https://github.com/postcss/autoprefixer) | `10.5.0` | `10.5.1` | | [@rollup/rollup-darwin-arm64](https://github.com/rollup/rollup) | `4.62.0` | `4.62.2` | | [@rollup/rollup-linux-arm64-musl](https://github.com/rollup/rollup) | `4.62.0` | `4.62.2` | Updates `axios` from 1.18.0 to 1.18.1 - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](https://github.com/axios/axios/compare/v1.18.0...v1.18.1) Updates `@playwright/test` from 1.61.0 to 1.61.1 - [Release notes](https://github.com/microsoft/playwright/releases) - [Commits](https://github.com/microsoft/playwright/compare/v1.61.0...v1.61.1) Updates `autoprefixer` from 10.5.0 to 10.5.1 - [Release notes](https://github.com/postcss/autoprefixer/releases) - [Changelog](https://github.com/postcss/autoprefixer/blob/main/CHANGELOG.md) - [Commits](https://github.com/postcss/autoprefixer/compare/10.5.0...10.5.1) Updates `@rollup/rollup-darwin-arm64` from 4.62.0 to 4.62.2 - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](https://github.com/rollup/rollup/compare/v4.62.0...v4.62.2) Updates `@rollup/rollup-linux-arm64-musl` from 4.62.0 to 4.62.2 - [Release notes](https://github.com/rollup/rollup/releases) - [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md) - [Commits](https://github.com/rollup/rollup/compare/v4.62.0...v4.62.2) --- updated-dependencies: - dependency-name: axios dependency-version: 1.18.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: "@playwright/test" dependency-version: 1.61.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: autoprefixer dependency-version: 10.5.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: "@rollup/rollup-darwin-arm64" dependency-version: 4.62.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: "@rollup/rollup-linux-arm64-musl" dependency-version: 4.62.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * feat(executions): propagate cancelled terminal status end-to-end (#679) (#1333) Defense-in-depth follow-up to #671. Make the agent task-runner aware that an operator cancel happened and surface a third terminal outcome — `cancelled` — alongside success/failed, so a cancel is never recorded as a billable success or an agent failure. Agent server: - ProcessRegistry records a `_terminated[execution_id]` marker on a successful SIGINT send; `was_terminated()` (read-only, 300s lazy TTL, cleared on register) lets the sync chat handler and async result callback relabel a graceful-exit-0 / SIGKILL->504 turn as cancelled. - `record_task_finish` accepts a neutral finish (success=None): a cancel neither resets nor increments the dispatch-breaker failure counter (#526). Backend: - 3-way status map (success->SUCCESS, cancelled->CANCELLED, else->FAILED) in the async callback (routers/agents.py) and the sync applier (task_execution_service). An auth/rate terminal is never reclassified as a cancellation — guarded at the backend trust boundary too (CSO finding 2). - Consumers (message_router, chat, paid, public, validation_service) treat cancelled as non-delivery; paid no longer settles on cancel (money bug). - terminate writes CANCELLED only when it actually stopped a running turn; on already-finished the agent's real terminal stands (Issue 7). Tests: 9 new unit suites (64 cases) + execution-termination integration additions; 85 unit tests pass locally. CSO diff audit: CLEAR. Refs #679 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(ui): unify Chat + Session into one Chat tab with a session-mode toggle (#1112) (#1340) Collapse the redundant Chat + Session tabs on Agent Detail into a single "Chat" tab carrying a "Session mode" toggle (default ON), keeping the legacy stateless surface as a first-class user-selectable mode rather than dead code. - AgentDetail.vue: single `{ id: 'chat' }` tab (drop the separate Session entry). New `chatMode` ref ('session'|'legacy', default 'session') persisted per-user in localStorage['trinity.chatMode']. `sessionAvailable` = feature flag on AND runtime has --resume (not Codex); `effectiveChatMode` forces legacy when the Session surface is unavailable and hides the toggle. The toggle swaps SessionPanel ↔ ChatPanel in-place (v-if). isFullscreenTab keys on the single 'chat' id; `?tab=session` aliases to 'chat' (hinting session mode). - Execution-resume: ExecutionDetail "continue as chat" (?tab=chat&resumeSessionId) forces legacy ChatPanel (which owns resume) via a transient, non-persisted routeForcedMode — without rewriting the user's saved preference. - No backend change (session_tab_enabled already exists). MobileAdmin unaffected: its openChat is a self-contained mobile chat overlay, not an AgentDetail deep-link, so there is nothing to repoint. - docs: architecture Session Tab block + requirements §5.8 note. Related to #1112 Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> * feat(access): Access tab — manage Trinity operators per agent (trinity-enterprise#17) (#1317) New Access tab on Agent Detail that manages Trinity operators (platform users) with access to an agent, distinct from the Sharing tab's external channel clients. Draws the operator-vs-client line on the read path. Backend: - db.get_agent_operator_access(): outer-joins agent_sharing × users on the grantee email (lower-cased, engine-based → PG+SQLite). Resolved → active operator (username/role/last_active); unresolved → pending invite. - GET /api/agents/{name}/access (AgentOperatorAccess model). Add/remove reuse the existing /share + /share/{email}. Frontend: - AccessPanel.vue: operator roster (status + role badges, last-active), add by email, remove. Access tab wired into AgentDetail (owner-gated). - SharingPanel.vue: Team Sharing allow-list removed (moves to Access); dead share-management script + stale "Team Sharing below" copy cleaned/repointed. - stores/agents.js: getAgentAccess(). Tests: active-vs-pending classification + agent scoping. vite build passes. Note: the strict client-vs-operator split (non-user emails → a dedicated client roster) is deferred to the Sharing-side redesign (#18/#20); removing them here now would orphan those grants, so all allow-list entries stay visible on Access. Related to Abilityai/trinity-enterprise#17 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(ui): slim the Overview executions-by-type bars The "Executions by type" stacked bars rendered full-width with a 1px gap, so a busy agent's week read as a solid wall of color. Cap each bar at 56px and center it inside its (still full-width) hover column, and soften the top corner. The column stays flex-1 so spacing/tooltips are unchanged and wider windows (14d/30d) thin naturally. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(voip): add Gacrux to the Gemini Live voice picker Adds the "Gacrux — Mature" prebuilt voice to the per-agent VoIP voice selector (and the shared AgentWorkspace per-session picker, which reads the same list). Updated in lockstep across the three mirrored sources so the frontend↔backend parity test stays green: - src/frontend/src/constants/voices.js — single frontend source of truth - src/backend/config.py GEMINI_VOICE_NAMES — write-validation allowlist + read-path fallback - tests/unit/test_28_voip_voice_config.py — hardcoded parity tuple Follow-up to #1323 (per-agent VoIP config panel + persisted voice). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * feat(ui): reframe Sharing tab to external-client sharing via channels (#1347) Part of the Access/Sharing redesign (Epic trinity-enterprise#16). The Access tab (#17) already owns Trinity operators; this scopes the Sharing tab to the operator → external-client surface. - Google-Docs-style "Share this agent" framing; operator language removed (operators live on the Access tab). - External access policy collapsed into one **Restricted ↔ Open** segmented control over require_email/open_access (Restricted = approval-gated, Open = anyone verified; identity proof always on for external sharing). - Pending requests kept, reframed as external clients awaiting approval. - Channels rendered as compact collapsible summary rows (new ChannelDisclosure.vue). Detailed config stays reachable inside the expanded row as a non-regressing interim seam — #19 replaces the body with a modal dialog. No channel functionality removed. - Outbound file sharing + public links nudged into a separate "Distribution" section (distribution, not client access). Frontend-only; no API changes. SharingPanel prop/emit contract unchanged. Verified: both SFCs compile (vue/compiler-sfc), design-token check passes. Related to abilityai/trinity-enterprise#18 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(architecture): trim architecture.md under the 150k-char context limit (#1344) architecture.md had grown to ~156.7k chars (on dev), past the 150k soft limit Claude Code warns about when auto-loading it each session (it's `@`-imported by CLAUDE.md). Over the limit the file risks silent truncation and eats a large slice of the context window every session. Compressed the densest Cross-Cutting Subsystem narratives, the migration and non-root-container invariants (#3/#17), a few catalog/endpoint rows, and the longest frontend UI prose — preferring summary + pointer where a dedicated `feature-flows/` doc already owns the deep detail (the doc's own editorial rule). Result: 156.7k → 149.3k chars (~4.8% smaller). No facts dropped: every issue tag, field name, default, and error-string is preserved; protected SQLite DDL (tracked by /validate-schema) untouched; heading/code-fence/table counts unchanged; all 12 added flow-doc links resolve. Related to the over-limit warning surfaced in Claude Code. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore(deps): bump js-yaml from 4.2.0 to 5.1.0 in /src/frontend (#1330) Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.2.0 to 5.1.0. - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](https://github.com/nodeca/js-yaml/compare/4.2.0...5.1.0) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * fix(ci): guard the Alembic (Postgres) track in schema-parity (#1342) (#1345) * fix(ci): guard the Alembic (Postgres) track in schema-parity (#1342) The schema-parity required check validated only the SQLite track (migrations.py ↔ schema.py). A schema change that ships the SQLite migration but omits the Alembic revision under src/backend/migrations/versions/ passed every required check green yet broke PostgreSQL — init_database() runs alembic_runner.upgrade_to_head(), which applies revision files only and does not autogenerate from tables.py. Two PRs reached "green CI but PG-broken" and had to be held by hand. Add a cross-track guard, folded into the existing required schema-parity job (no new required-check to manage): - scripts/ci/check_alembic_parity.py — fails a PR that ADDS schema DDL to db/{migrations,schema,tables}.py without a net-new revision file under src/backend/migrations/versions/. Pure stdlib, PR-only (diffs base...head). - Heuristic / false-positive guard: the signal is a DDL keyword on an *added, non-comment* line (SQL: CREATE/ALTER/ADD COLUMN/…; SQLAlchemy: Column(/Table(/Index(/…). Comment edits, data-only and down migrations carry no DDL keyword, so they don't trip it. Documented in the script docstring and the workflow header. - tests/unit/test_alembic_parity_guard.py — 20 tests incl. the acceptance fixtures (SQLite-only change fails; dual-tracked passes; comment/data-only pass). Wired into the parity pytest run. Also notes the enforcement in architecture.md Invariant #3. Verified locally: 24 tests pass; end-to-end smoke across clean / SQLite-only (exit 1) / paired-revision (exit 0) scenarios behaves correctly. Related to #1342 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(ci): tighten Alembic guard to require a new MIGRATIONS entry (#1342) Verifying against real repo history surfaced a false positive: the migration-runner refactor #1263 (_atomic_rebuild table rebuilds) re-emits CREATE TABLE / CREATE INDEX for *existing* tables in a rename-swap but adds no actual schema and no new MIGRATIONS entry — yet the original "any added DDL keyword" heuristic flagged it, violating AC #4 (non-schema edits must not trip). Tighten the signal to two conjuncts: a schema change must (1) register a net-new ("name", _migrate_fn) entry in the MIGRATIONS list AND (2) carry a DDL keyword. Runner refactors / table rebuilds add no entry → exempt; data-only new migrations carry no DDL → exempt; real column/table adds do both → caught. Validated against real commits: • #740 agent_loops, #526 agent_ownership column → FAIL (correctly blocked) • #668 compat, voice_name (both shipped an Alembic revision) → PASS • #1263 runner refactor → PASS (false positive fixed) A full post-Alembic history scan finds 0 outstanding missing revisions, so no backfill is owed; the pre-Alembic columns are already in 0001_baseline. 28 tests pass (added MIGRATIONS-entry detection + the #1263 rebuild case). Related to #1342 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com> * docs(dependab…

…rror (#1167) Sequential agent loops (#740) were fail-fast: the first failed iteration aborted the whole loop. Add a per-loop policy to tolerate failures and keep going, bounded so a fully-broken agent still terminates. - config: `on_failure` ('abort' default = current fail-fast, backward compatible; 'continue' tolerates a failed iteration) + `max_consecutive_failures` (default 3, range 1–100). Both plumbed end to end (Invariant #13). - runner (loop_service.py): both failure surfaces gated — raised exception AND non-success TaskExecutionResult. Continue mode finalizes the failed agent_loop_runs row, increments failed_runs/consecutive_failures, and proceeds; a success resets the streak. Reaching max_runs (or stop-signal) with tolerated failures finalizes as `completed_with_errors`; hitting the consecutive cap finalizes `failed`/`stop_reason=max_consecutive_failures`. {{previous_response}} keeps the last *successful* response (a failed iteration never overwrites it). - schema/migration: agent_loops gains on_failure, max_consecutive_failures, failed_runs (schema.py + tables.py Core + versioned migration). New terminal status `completed_with_errors`. - api: POST /loops accepts on_failure/max_consecutive_failures; LoopStatusResponse surfaces failed_runs/on_failure/max_consecutive_failures. - mcp: run_agent_loop gains the two params (tools/loops.ts + client.ts). - ui: LoopsPanel failure-policy controls + failed_runs/completed_with_errors surfacing. - tests: abort unchanged, continue past a failed run (both surfaces), consecutive cutoff, streak-reset; schema-parity + migrations green. 42 passed. Related to #1167 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

…rror (#1167) (#1339) * feat(loops): configurable failure policy — fail-fast vs continue-on-error (#1167) Sequential agent loops (#740) were fail-fast: the first failed iteration aborted the whole loop. Add a per-loop policy to tolerate failures and keep going, bounded so a fully-broken agent still terminates. - config: `on_failure` ('abort' default = current fail-fast, backward compatible; 'continue' tolerates a failed iteration) + `max_consecutive_failures` (default 3, range 1–100). Both plumbed end to end (Invariant #13). - runner (loop_service.py): both failure surfaces gated — raised exception AND non-success TaskExecutionResult. Continue mode finalizes the failed agent_loop_runs row, increments failed_runs/consecutive_failures, and proceeds; a success resets the streak. Reaching max_runs (or stop-signal) with tolerated failures finalizes as `completed_with_errors`; hitting the consecutive cap finalizes `failed`/`stop_reason=max_consecutive_failures`. {{previous_response}} keeps the last *successful* response (a failed iteration never overwrites it). - schema/migration: agent_loops gains on_failure, max_consecutive_failures, failed_runs (schema.py + tables.py Core + versioned migration). New terminal status `completed_with_errors`. - api: POST /loops accepts on_failure/max_consecutive_failures; LoopStatusResponse surfaces failed_runs/on_failure/max_consecutive_failures. - mcp: run_agent_loop gains the two params (tools/loops.ts + client.ts). - ui: LoopsPanel failure-policy controls + failed_runs/completed_with_errors surfacing. - tests: abort unchanged, continue past a failed run (both surfaces), consecutive cutoff, streak-reset; schema-parity + migrations green. 42 passed. Related to #1167 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(loops): honor inter-run delay on the exception failure surface (#1167 review) Continue mode skipped delay_seconds when an iteration *raised* (the exception path `continue`d past the delay block), while a non-success result honored it. Extract the inter-run delay (with its cooperative-stop check) into a helper and call it on both surfaces so continue-mode pacing is consistent. Add a test asserting the delay fires after a raised iteration. * fix(db): add Alembic revision for agent_loops failure-policy columns (#1167) #1167 shipped the SQLite migration + DDL but no Alembic revision, so an existing PostgreSQL deployment would miss on_failure / max_consecutive_failures / failed_runs on `alembic upgrade head`. Chains 0011 after 0010 (single head). Related to #1167 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore: reset stale submodule pointers to dev's (.claude, src/backend/enterprise) The branch carried accidental gitlink changes from a stale local checkout: src/backend/enterprise pointed at a commit only reachable from an unmerged side branch (feature/88-local-dev-submodule-docs), and .claude at a commit divergent from dev's pointer. Neither bump was intended by this PR. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com>

…160) The MCP surface for the A2A interoperability management plane — the third surface (Invariant #13) over the entitlement-gated enterprise backend (trinity-enterprise#160, /api/enterprise/a2a/*). Distinct from the runtime call_a2a_agent (#736). New src/mcp-server/src/tools/a2a.ts (7 tools): - get_agent_a2a_config, set_agent_a2a_exposure, get_agent_a2a_card (proxies the OSS #737 served-card endpoint), set_a2a_inbound_allowlist, register_a2a_endpoint, list_a2a_endpoints, remove_a2a_endpoint. - Honest gating: an unentitled 403 ("not licensed") / OSS-only 404 return a structured { not_entitled | not_found } — never a silent success. Mutations are owner/admin + human-only, enforced at the backend (agent-scoped key → 403 human_only). Outbound credentials are write-only — the backend returns only has_credentials, so no tool echoes a secret. client.ts: 8 A2A methods (getA2AExposedMap swallows OSS-404/unentitled-403 → {}). agents.ts: list_agents/get_agent best-effort merge a2a_exposed (mirrors mcp_exposed, #846) — omitted in editions without A2A, no OSS↔enterprise coupling. server.ts: register the tool group (connector-denied visibility, like the rest). Tests: src/mcp-server/src/tools/a2a.test.ts (10) — proxy contract, credentials never echoed, entitlement/human-only/404 gating. Full suite 100 pass; tsc clean. Related to #160 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

… terminal (#1578) (#1680) * docs(requirements): system-emitted task completion events (#1578) Rule #1 — document the new capability before implementing it. Adds §17.2a beside EVT-001: backend emits agent.task.completed/failed at every CAS-won terminal, matching-sub gated, reserved namespace + recursion-break, EVT-001 dispatch (best-effort to a running subscriber), inert by default. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * feat(events): event_dispatch_service — extracted delivery + system emit helper (#1578) New services/event_dispatch_service.py: - trigger_subscription / _interpolate_template / _get_internal_token moved verbatim out of routers/event_subscriptions.py so a service (TES) can reuse the EVT-001 dispatch primitive without importing a router (Invariant #1). - emit_task_terminal_event + spawn_task_terminal_event (#1578): the single shared helper the backend fires at every CAS-won terminal — matching-sub gated (empty => no row, no dispatch), recursion-break on triggered_by='event', flat interpolable payload incl. fan_out_id/loop_id, fail-open. - trigger_subscription stamps the reserved-namespace loopback with X-Event-Trigger so the spawned task persists triggered_by='event'. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * feat(events): reserved-namespace guards + recursion-break wiring (#1578) - event_subscriptions.py: import the extracted event_dispatch_service (delete the moved defs); reject agent emits into agent.task.* on both emit routes (400); block reserved-namespace self-subscription on create AND update (400); dispatch via event_dispatch_service.trigger_subscription. - chat.py: read X-Event-Trigger on /task; a reserved-namespace dispatch persists triggered_by='event' (threaded via triggered_by_override) so the emit helper suppresses that task's own terminal event — the recursion-break. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * feat(events): emit agent.task.* at every task_execution terminal (#1578) - apply_result SUCCESS won path -> agent.task.completed (sanitized_resp, cost, duration); covers both #1083 paths (inline sync + async result-callback both converge here). - apply_result FAILURE won path -> agent.task.failed (envelope.status carries failed/cancelled; salvage cost). - _write_terminal_and_gate gains agent_name and emits agent.task.failed on won — covering the timeout / budget-exhausted / unexpected-exception (+ inline circuit-open/capacity/ephemeral) terminals that never reach apply_result, the exact wedge case the feature exists for. agent_name threaded from all 4 execute_task call sites. All emits are CAS-won only, fire-and-forget, fail-open. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * feat(events): emit agent.task.failed at the #1083 lease-reaper terminals (#1578) _sweep_stale_slots' two per-execution CAS-won sites (async lease expired with no result callback) now emit agent.task.failed — waking a subscribed orchestrator on the exact wedge the feature exists for. Fire-and-forget + fail-open; the bulk watchdog sweeps stay a documented residual (no per-row context). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * feat(events): emit agent.task.* at the pull-sink terminal (#1578) apply_task_result's CAS-won path now emits agent.task.completed/failed. Dark until a pull pilot is enabled (#1081) but wired so a pilot doesn't silently regress report-back. CAS-won only (replay/late report short-circuits or loses the CAS), fire-and-forget + fail-open. Coordinate with obasilakis (his file). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(mcp): note reserved agent.task.* namespace in events.ts (#1578) Invariant #13 doc-only: emit_event notes agent.task.* is reserved/backend-emitted (rejected if emitted); subscribe_to_event notes you can subscribe to a source agent's agent.task.completed/failed for an automatic report-back task instead of polling, with the payload shape and the no-self-subscription rule. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * test(events): unit coverage for system-emitted task completion events (#1578) 27 tests, all green: - Emit helper: fired (success/failed/cancelled), not-fired-no-sub (AC #1/#5), recursion-break, status-as-.value (#1085 footgun), payload shape (fan_out_id/loop_id), duration/cost row fallback, truncation, fail-open. - Every CAS-won terminal writer spawns on won / not on lost CAS: apply_result inline path, _write_terminal_and_gate (timeout class — the critical pin), the #1083 lease-reaper, and the pull sink. - Both #1083 terminal paths GENUINELY (dossier §5): inline apply_result call AND the async result-callback endpoint driving the REAL apply_result — distinct entry points, not two tests on the same inline call. - Reserved-namespace guards: emit 400, create self-sub 400, PUT self-sub 400, cross-agent subscribe allowed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(feature-flows): task-completion-events flow + index + cross-links (#1578) New feature-flows/task-completion-events.md: end-to-end report-back path, the terminal-writer coverage table, system- vs agent-emitted split, 3-layer loop safety, honest best-effort delivery note, content-trust note, test map. Adds the Recent Updates row + category index entry (feedback: always add the index row), and cross-link pointers from task-execution-service.md and agent-event-subscriptions.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(architecture): Task Completion Events cross-cutting block (#1578) - New 'Task Completion Events (#1578)' subsystem block: system- vs agent-emitted, shared event_dispatch_service helper, CAS-won terminal-writer coverage table, 3-layer loop safety, honest best-effort delivery note. - Pointer from Fire-and-Forget Dispatch (#1083); services-catalog row for event_dispatch_service.py; reserved-namespace note on the events.ts MCP row + the agent_events DDL. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * docs(target-arch): reconcile §Async-First — completion events implemented (#1578) Mark the agent.task.completed/failed contract IMPLEMENTED, note the divergence (EVT-001 subscription dispatch, best-effort to a running subscriber; durable pull-queue delivery deferred; not the WS event_bus) and the pull-sink coverage. Add a '├─ Bankable win 3' #1578 row under the #1081 umbrella. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(events): authenticate recursion-break header + sanitize task-event summary (#1578) Two review findings on the #1578 completion-event path, both pre-merge: 1. Spoofable recursion-break. The reserved-namespace loopback was suppressed purely on an `X-Event-Trigger` header, so an external `/task` caller could spoof it to suppress a real agent's completion event. The header is now honored ONLY with a valid backend-internal `X-Internal-Secret` (C-003): `trigger_subscription` stamps both, `execute_parallel_task` verifies via `event_dispatch_service.verify_internal_dispatch_secret` (constant-time) before persisting `triggered_by="event"`. 2. Un-sanitized failure summary. Success/pull terminals sanitize upstream, but the failure error strings (`envelope.error` / `str(exc)`) reached the emit helper raw. `emit_task_terminal_event` now credential-sanitizes at the single chokepoint over a 2x-cap window BEFORE the final truncation, so a secret straddling the `TASK_EVENT_SUMMARY_MAX` boundary can't leak an un-redactable head fragment. Tests: +7 (spoof-guard at the helper AND the router call-site; sanitize incl. the boundary-straddle case) -> 37 pass. Docs: architecture.md delivery note + feature-flow recursion-break/second-terminal notes updated. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com>

#1296) (#1694) * docs(requirements): agent self-reminders §10.14 (#1296) Requirements-first per Rule of Engagement #1: document the new agent self-reminders capability (durable one-shot deferred self-trigger) before implementing it — AC 1-7, storage fork, scheduler fire home, at-least-once delivery, autonomy hold, and retention. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(db): agent_reminders table — 5-track migration (#1296) Durable one-shot deferred self-trigger storage. Byte-consistent DDL across all five coordinated edits (Invariant #3): - db/schema.py: TABLES entry + two indexes (agent + partial active) - db/migrations.py: _migrate_agent_reminders_table + MIGRATIONS tail - migrations/versions/0028_agent_reminders (off head 0027) - db/tables.py: SQLAlchemy Core Table (byte-matched to DDL) - db/agent_cleanup.py: AGENT_REFS CASCADE (rename cascade + purge + soft-delete filter; source_agent_name left unregistered per the agent_loops precedent) schema-parity, alembic-parity, and cleanup-parity all green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(executions): wire triggered_by="reminder" into all three trigger constants (#1296) A new triggered_by value must hit all three sites or reminder executions silently vanish from the Overview chart, fail to filter, or misclassify their failure alert: - _TRIGGER_BUCKETS + _BUCKET_ORDER (db/schedules.py) — first-class "Reminders" bucket (mirrors the #1150 loops precedent) - _AUTONOMOUS_TRIGGERS (task_execution_service.py) — a reminder fires unwatched, so a FAILED reminder earns an operator alert - _VALID_TRIGGERS (routers/executions.py) — the fleet Executions ?triggered_by= filter accepts it Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(reminders): backend create/list/cancel surface (#1296) Three-layer backend for agent self-reminders (Invariants #1/#2/#8/#14/#18): - models.py: ReminderCreate (fire_at XOR delay_seconds validator) + Reminder/ReminderSummary + env-tunable abuse-bound constants - db/reminders.py: RemindersOperations (SQLAlchemy Core, tenant-scoped by-id ops, CAS cancel, pending/daily counts, retention prune+count) - database.py: facade delegation - services/reminder_service.py: thin create — resolved-window bound, timeout clamp to agent cap (#929 parity), pending + durable daily caps, provenance, relative→absolute, insert - services/idempotency_service.py: derive_reminder_key over RAW input - routers/reminders.py: self-only gate (current_user.agent_name==name) + _reject_connector_principal; create-idempotency (header wins else raw-input key; terminal rows excluded from replay; fail() only pre-insert); tenant-scoped cancel (200/409/404); main.py registration Self-only auth mirrors reports; connector keys stay off the auth-entry allowlist AND are explicitly rejected. Verified against a real migrated SQLite DB; models-centralized + enumeration-uniformity green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(scheduler): arm/fire/reconcile agent self-reminders (#1296) The standalone scheduler (single-instance) owns the reminder fire path — a near-clone of the RETRY-001 one-shot DateTrigger machinery: - models.py: Reminder dataclass (naive-UTC fire_at/firing_at) - database.py: committed CAS methods (claim_reminder_firing pending→ firing, mark_fired/failed, release_to_pending, set_execution) + get_active_reminders (pending∪firing JOIN agent_ownership, filters deleted_at + autonomy_enabled=1) + _row_to_reminder via parse_scheduler_ts - service.py: _schedule_reminder_job (DateTrigger), _execute_reminder (at-least-once: CAS claim → create real execution row (__manual__, triggered_by=reminder) → dispatch via _call_backend_execute_task → timeout=assume-dispatched no-force-FAILED / clean-failure=status- guarded FAILED + bounded retry), _reconcile_reminders (fail-open, arms pending + reclaims stale firing) wired into initialize() (own try after _recover_pending_retries), _sync_schedules() (own try, NOT under the cron try — Codex C5), and reload_schedules() (Codex C6) - config.py: MAX_REMINDER_FIRE_ATTEMPTS (default 3) All 207 existing scheduler tests green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(mcp): set_reminder/list_reminders/cancel_reminder tools (#1296) Third surface (Invariant #13) mirroring loops.ts 1:1: - tools/reminders.ts: createReminderTools → {setReminder, listReminders, cancelReminder}; reuses the inline getClient + resolveAgentName self-scoping (an agent-scoped key defaults to its bound name); Zod carries the abuse bounds (message.max(4000), delay 60..2592000, fire_at ISO string). Idempotency is enforced server-side over the raw input, so a naive retry dedupes without a client-supplied key. - client.ts: setReminder/listReminders/cancelReminder thin request wrappers - server.ts: import + register in the tools array No agent-server mirror (backend-only scheduling primitive). tsc build clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(retention): agent_reminders retention sweep + #1644 guard wiring (#1296) A durable status table needs a retention story (the AGENT_REFS CASCADE only cleans on agent delete; terminal rows on a LIVE agent accumulate). Decision: wire the FULL #1644 blast-radius guard (lightweight, mirrors agent_reports exactly, honors #1638/#1644 discipline): - settings_service.py: agent_reminders_retention_days in OPS_SETTINGS_ DEFAULTS (90, wide/safe), OPS_SETTINGS_DESCRIPTIONS, and RETENTION_OPS_KEYS (surfaced at GET /api/settings/retention, protected from /ops/reset, logged at boot). NOT a community-floor key. - cleanup_service.py: _sweep_agent_reminders_retention — DELETE terminal (fired/cancelled/failed) rows past the window (pending/firing never deleted), chunked, gated via _guard_allows + _after_guarded_prune (default MAX_ROWS_PER_SWEEP floor); CleanupReport.agent_reminders_pruned. retention-guard suite green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * test(reminders): backend + scheduler coverage (#1296) Backend (tests/unit/test_1296_reminders.py, 33 tests): migration + tables.py live-select accessor guard (the guard schema-parity misses), the three trigger constants (parametrized), ReminderCreate XOR, derive_reminder_key raw-input stability, db round-trip + tenant-scope + cancel CAS states, retention (terminal pruned / pending+firing kept), reminder_service bounds (min/max window, timeout>cap, pending 429, daily 429), and router self-gate ATTACK (sibling 403, connector 403), tenant-scope 404, idempotency edges (dup replay, in-flight 409, cancel-then-recreate-fresh), cancel outcomes, list default-pending. Scheduler (tests/scheduler_tests/test_1296_reminders.py, 17 tests): committed single-fire CAS + multi-connection contention (exactly one wins, Codex C8), _execute_reminder outcomes (claim-loss / success / timeout=assume-dispatched-no-force-FAILED / clean-failure-retry / bounded-failed), _reconcile (arm-once, past-due, stale-firing reclaim, Z-suffix no-raise, missing-table no-op, soft-delete/autonomy-off filtered), reload path (Codex C6). Scheduler suite 224 green; backend reminder+parity+guard sweep 124 green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(architecture): agent self-reminders subsystem (#1296) - New 'Agent Self-Reminders (#1296)' subsystem section (sibling to Sequential Agent Loops): storage fork, scheduler fire home, at-least-once delivery, self-only auth + abuse bounds, autonomy hold + AGENT_REFS cascade + retention - agent_reminders DB schema block (dual-track migration, CASCADE) - router/service catalog entries (reminders.py, reminder_service.py) - MCP tools table row (reminders.ts × 3) - Scheduler Service + Cleanup Service background-service rows updated - API Endpoints section for the 3 reminder endpoints Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(feature-flows): agent-self-reminders flow doc + index (#1296) New feature-flow doc mirroring run-agent-loop.md: the two design forks, MCP/backend/scheduler layers, single-fire + at-least-once delivery semantics, the 5-track migration, retention, and the three trigger constants. Adds a Recent Updates row + a Core Agent Features category row to the index (per the always-add-an-index-row rule). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * chore(config): wire agent-reminder tunables into compose + .env.example (#1296) The six REMINDER_*/MAX_*REMINDER* caps are backend os.getenv() levers with working code defaults, so the feature ships functional — but without compose wiring the .env levers are inert on deploy (the #1056/#1039 packaging class), mirroring how REPORT_RATE_LIMIT (#918) is wired into all three files. Adds the block to .env.example, docker-compose.yml, and docker-compose.prod.yml backend.environment: with defaults matching models.py/routers. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix: resolve .env.example conflict left in the previous merge commit (keep both #1296 REMINDER_* and #1632 OPERATOR_QUEUE_* blocks) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Eugene Vyborov <eugene@beingluminous.com>

AndriiPasternak31 and others added 14 commits February 6, 2026 01:03

feat(process-engine): add Telegram to NotificationConfig

c1b0aa3

Add Telegram channel support to notification step configuration: - bot_token: Telegram bot token (supports env var) - chat_id: Telegram chat ID (supports env var) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

docs: update changelog, architecture, and roadmap

76eea3a

- Add changelog entries for SMARTS features - Update architecture documentation - Update roadmap progress Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

chore(scripts): add SMARTS cascade deployment script

6d806d8

Script to deploy all SMARTS agents in cascade order. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

AndriiPasternak31 changed the title ~~feat: SMARTS Miro flow visualization with improved formatting~~ feat: SMARTS trading pipeline with Telegram notifications and Miro visualization Feb 6, 2026

AndriiPasternak31 closed this Feb 6, 2026

This was referenced Apr 29, 2026

Architecture Validation: 2 critical violations found (2026-04-29) #572

Closed

Schema Validation: 14 critical/high schema drift issues found (1 P0, 13 P1) #604

Closed

This was referenced May 15, 2026

feat: per-agent MCP exposure flag — dynamic dedicated tool per exposed agent #846

Closed

Add per-agent model override for public communication channels #894

Closed

vybe mentioned this pull request May 23, 2026

Computer Use: sandbox desktop sidecar per agent #916

Open

23 tasks

dolho mentioned this pull request May 25, 2026

feat(#929): agent cap enforces schedule ceiling + clearer SIGKILL msg #930

Merged

6 tasks

vybe mentioned this pull request May 28, 2026

Spike: Integrate Claude Code effort configuration into Trinity #972

Open

7 tasks

This was referenced Jun 24, 2026

feat(sharing): per-agent custom instructions for public & channel chats (#1205) #1337

Merged

feat(loops): configurable failure policy — fail-fast vs continue-on-error (#1167) #1339

Merged

dolho mentioned this pull request Jun 26, 2026

feat(connector): per-agent MCP connector — playbooks as tools (ent#46, PR1) #1355

Closed

This was referenced Jun 26, 2026

docs(#945): correct actor-model postcard — result-reporting + taxonomy/citation accuracy #1358

Merged

feat(mcp): agent-defined pipeline introspection tools (#919) #1359

Merged

AndriiPasternak31 mentioned this pull request Jul 4, 2026

fix(security): close user & agent enumeration oracles — uniform 404 + email-request parity + MCP owner-disclosure removal (#186) #1455

Merged

vybe mentioned this pull request Jul 5, 2026

feat(mcp): ask_trinity docs Q&A tool in the Trinity MCP server #1460

Open

6 tasks

vybe mentioned this pull request Jul 7, 2026

Executable schedules: add a command/script execution mode alongside LLM triggers #1512

Open

12 tasks

vybe mentioned this pull request Jul 9, 2026

Let agents read back their old reports via MCP #1538

Open

5 tasks

dolho mentioned this pull request Jul 9, 2026

feat(voice): voice replies v2 — per-message capability, agent-level config, runtime ElevenLabs key (trinity-enterprise#117) #1549

Merged

vybe mentioned this pull request Jul 11, 2026

One-click copy MCP connection config (with embedded user key) for an exposed agent — connect external agents in seconds, playbooks as tools #1575

Open

10 tasks

This was referenced Jul 15, 2026

feat(mcp): A2A control tools — exposure, card, allow-list, endpoints (ent#160) #1627

Closed

feat(a2a): A2A interoperability — inbound server (well-known + JSON-RPC/SSE) + control MCP tools (ent#157/#160) #1628

Open

vybe mentioned this pull request Jul 17, 2026

feat(events): system-emitted agent.task.completed/failed at execution terminal (#1578) #1680

Merged

7 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: SMARTS trading pipeline with Telegram notifications and Miro visualization#13

feat: SMARTS trading pipeline with Telegram notifications and Miro visualization#13
AndriiPasternak31 wants to merge 14 commits into
Abilityai:mainfrom
AndriiPasternak31:feature/smarts-miro-diagram

AndriiPasternak31 commented Feb 6, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

AndriiPasternak31 commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

SMARTS Agent Templates

Telegram Notifications

API & Scheduler

Miro Visualization

Other

Test plan

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

AndriiPasternak31 commented Feb 6, 2026 •

edited

Loading