104 Commits

Author	SHA1	Message	Date
HAL9000	2778bde95a	fix(repositories): derive PlanResult.success from result_success column instead of error_message ... ISSUES CLOSED: #7501	2026-05-07 14:22:57 +00:00
HAL9000	8384f53e28	test(cli): cover actor remove format regression (#6491) ... Add Robot regression coverage for `actor remove --format json`, document the flag in the CLI synopsis, and record the fix in the changelog.\n\nISSUES CLOSED: #6491	2026-05-06 01:07:15 +00:00
hurui200320	85c579b51f	fix(cli): display full session IDs in session list output ... Remove the [:8] truncation from session IDs in the Rich table row, Most Recent summary, and Oldest summary fields of list_sessions() and _session_list_dict(). Session IDs are 26-character ULIDs and must be usable directly for copy-paste into session tell, session show, and other session commands. The structured output (JSON/YAML) already used full IDs in the sessions[*].id field, but the summary panel leaked the truncation into those formats as well. Added Behave scenarios: - Rich table displays full 26-character ULIDs (scoped to table region) - Summary panel shows full ULIDs for unnamed sessions (scoped to panel) - Summary panel shows session names for named sessions - Full ULID from list output works with session tell (round-trip, uses parsed ULID, not hardcoded constant) Review Cycle 2 fixes: - docs/specification.md: Updated YAML output example to full ULIDs - docs/showcase/*.md: Updated all example output blocks to full ULIDs - docs/reference/session_cli.md: Replaced placeholder with full ULID - features/session_cli.feature: Consecutive When steps -> And - features/steps/session_cli_steps.py: Summary panel asserts both IDs, 8-char negative guard in table output, ULID capture scoped to table region with fixture verification, named-session absence check for second session - CHANGELOG.md: Added [Unreleased] entry for the behavioral change ISSUES CLOSED: #10970	2026-05-05 10:56:18 +00:00
HAL9000	7ece6f1530	docs(spec): rename checkpoint triggers on_tool_write → before/after_tool_execute ... Update the Automatic Checkpoint Triggers table and configuration reference in docs/specification.md to use the trigger names that match the actual implementation in ToolRunner and config_service.py: - on_tool_write → before_tool_execute - on_tool_write_complete → after_tool_execute The implementation (PR #3474) chose before_/after_ prefix pattern for consistency with event naming conventions and because _execute is more precise than _write. The spec was not updated at that time. ISSUES CLOSED: #4745	2026-04-30 17:48:19 +00:00
HAL9000	0ade2526eb	docs(cli): update agents validation attach synopsis to use --key value named option format ... Update docs/specification.md to clarify that agents validation attach extra arguments use --key value named option format (not positional [<ARGS>...] format). Updates synopsis, argument description, and all inline references across the specification. ISSUES CLOSED: #4747	2026-04-29 17:08:17 +00:00
HAL9000	581dff6b43	spec(acms): add comprehensive ACMS v1 specification section (v3.4.0) ... Adds a comprehensive ACMS v1 (Advanced Context Management System) specification section covering all aspects of the context management architecture for milestone v3.4.0 — ACMS v1 + Context Scaling. Sections included: - Overview and design goals - Architecture: UKO (Unified Knowledge Ontology), CRP (Context Request Protocol), Context Pipeline, Storage Tiers (hot/warm/cold) - Module Definitions across all 4 architecture layers (Domain, Application, Infrastructure, Presentation) - Data Models: ContextFragment, ContextBudget, ProjectContextPolicy, ContextView, AssembledContext/ContextPayload, IndexMetadata - Key Interfaces: ACMSPipeline, ContextBudgetEnforcer, UKOStore, ContextTierService, RepoIndexingService - 10-Component Pipeline Architecture (3 phases: Strategy Orchestration, Fragment Fusion, Context Finalization) - Context Strategies: 6 built-in strategies with fallback degradation path - CLI Commands: agents context list/add/show/clear and agents project context set/show/inspect/simulate - Integration Points: Plan Lifecycle, Resource System, Actor/Agent, Configuration, DI Container - Database Schema: repo_indexes and indexed_files tables - v1 Known Limitations with planned conformance path - Acceptance Criteria for milestone v3.4.0 Replaces stuck [AUTO-ARCH-19] worker from Cycle 26. [AUTO-ARCH-20] Cycle 27 # Conflicts: # docs/specification.md	2026-04-26 18:45:44 +00:00
HAL9000	3975ad244c	docs(spec): fix invariant reconciliation, add ACMS thread safety, v3.6.0 section, ADR-049 ... - Fix invariant glossary entry: reconciliation now documented as occurring at each phase boundary (before Strategize, Execute, Apply, and after Apply) rather than only at start of Strategize (closes #9899) - Add Multi-Phase Invariant Enforcement note to Plan Lifecycle section - Add ACMS Thread Safety subsection documenting threading.RLock concurrency contract for ContextAssemblyPipeline and all context stores (closes #9859) - Append M7: Advanced Concepts and Deferred Features (v3.6.0) milestone spec section covering advanced invariant lifecycle, ACMS observability, plan hierarchy enhancements, and CLI communication pattern migration - Add ADR-049: CLI Communication Pattern documenting local CLI exemption from A2A boundary requirement and M9 migration path	2026-04-26 17:09:22 +00:00
HAL9000	663a6d2397	docs(decomposition): enhance docstrings and add spec section for selective subtree recomputation	2026-04-24 08:26:59 +00:00
HAL9000	dddfa48eb4	docs(spec): extend diagnostics example to cover all providers ... - update agents diagnostics examples to show all provider checks across rich, plain, JSON, and YAML formats - refresh error scenario samples to reflect the expanded provider coverage and recommendation counts - align CLI diagnostics output with the spec by adding explicit provider display names and consistent ordering Closes #5320	2026-04-24 03:51:32 +00:00
HAL9000	835bc580e2	spec: document JSON-RPC 2.0 A2A wire format (AUTO-ARCH-8) ... Updates the A2A Protocol section to reflect the rename of A2aRequest/ A2aResponse fields to standard JSON-RPC 2.0 names (method, id, result, error). Documents A2aVersionNegotiator for backward compatibility. Closes #8787	2026-04-15 08:44:55 +00:00
HAL9000	510cb03d99	docs(spec): add v3.8.0 Server Implementation milestone plan and update status table (#7701) ... Co-authored-by: CleverThis <hal9000@cleverthis.com> Co-committed-by: CleverThis <hal9000@cleverthis.com>	2026-04-14 16:46:31 +00:00
HAL9000	a3094dea2b	docs(spec): clarify path containment, datetime, and plugin security contracts ... Three implementation contracts clarified in response to security/correctness bugs surfaced by the bug hunt pool: 1. Path containment: Sandbox path validation MUST use Path.is_relative_to() not string prefix comparison. String prefix allows /tmp/sandboxmalicious to pass a /tmp/sandbox root check. Canonical implementation provided. 2. Datetime handling: All stored ISO timestamp comparisons MUST parse back to timezone-aware datetime objects before comparing. String comparison of ISO timestamps is incorrect when timezone offsets differ in format. Canonical parse_utc_ts() pattern provided. 3. Plugin protocol validation: Protocol compliance MUST be checked structurally via issubclass() — never by instantiating the plugin class. Instantiation runs __init__ side effects before the plugin is approved. These are minor clarifications (implementation contracts, not architectural changes) added to the existing Security and Extensibility sections. Refs: BUG-HUNT issues #7336 (path traversal), #7341 (datetime comparison), #7331 (plugin instantiation)	2026-04-13 00:44:44 +00:00
freemo	87d1a64cf2	docs(spec): document MCP 1.4.0 error extraction from content[0].text in MCPToolAdapter ... The MCPToolAdapter execute() section now documents the MCP 1.4.0 error response protocol: when isError is true, the error message is extracted from content[0].text rather than a non-standard top-level error key. Falls back to 'unknown error' when content is absent or malformed. This aligns the spec with the implementation fix in PR #2600 and the approved proposal in issue #3330. ISSUES CLOSED: #3330	2026-04-10 09:14:33 +00:00
HAL9000	06073bfcec	docs(spec): add Milestone Plan section for v3.2.0 through v3.7.0 ... Add a comprehensive Milestone Plan section to docs/specification.md mapping architectural features to verifiable deliverables for each milestone from v3.2.0 (Decisions + Validations + Invariants) through v3.7.0 (TUI Implementation). Each milestone section includes: - Goal statement aligned with Forgejo milestone descriptions - Spec coverage cross-references to existing spec sections - Deliverables table with spec reference and verifiable check per item - Key architectural constraints specific to that milestone - Definition of Done criteria Also adds: - Cross-Milestone Quality Gates table (unit/integration/typecheck/lint/ coverage/security/performance/docs) - Cross-Milestone Architectural Invariants (10 invariants that must hold across all milestones) This section serves as the authoritative mapping between the detailed architectural spec and the milestone-level work tracked in Forgejo, enabling implementers to understand which spec sections govern each milestone's work and what constitutes completion.	2026-04-08 19:57:23 -04:00
freemo	658b86c976	docs(spec): document DEPENDENCY_ORDERED subplan execution mode ... Add the DEPENDENCY_ORDERED execution mode to the Child Plan Execution Modes section. This mode performs topological sorting of subplan dependencies and executes independent subplans concurrently in waves. Also adds the dependency-ordered row to the failure handling table. Closes #4034	2026-04-06 09:20:16 +00:00
freemo	3f4d984da6	docs(spec): add skeleton_fragments to AssembledContext and update pipeline pseudocode ... Add skeleton_fragments field to the AssembledContext dataclass in the spec to match the implementation (PR #3676). Update the pipeline assemble() method signature to include skeleton_ratio and parent_fragments parameters, and add Step 10 (SkeletonCompressor invocation) to Phase 3 of the context assembly pipeline pseudocode. Closes #3783	2026-04-06 06:47:28 +00:00
freemo	2b22c9f40e	docs(spec): document automatic checkpoint triggers in main specification ... Add documentation for the four automatic checkpoint triggers (on_tool_write, on_tool_write_complete, on_subplan_spawn, on_error) that were implemented in PR #3474 and documented in the reference doc (docs/reference/checkpointing.md) but missing from the main specification. Also adds the sandbox.checkpoint.auto-create-on config key to the configuration reference table. Closes #3784	2026-04-06 06:46:19 +00:00
freemo	96470f39dc	docs: update specification — add agents plan errors command ... Reviewed and APPROVED. Closes #2883.	2026-04-05 21:16:20 +00:00
freemo	bb97f87a31	docs(spec): fix invariant precedence chain (3-tier->4-tier) and document non_overridable flag ... Approved proposal: #3064 Changes: - Glossary (line 92): Fix 3-tier precedence claim to correct 4-tier chain (plan > action > project > global) and add non_overridable exception note - Line 18980: Fix Invariant Reconciliation Actor step 5 precedence reference - Line 18991: Fix Strategize phase invariant reconciliation precedence reference - Lines 19601-19604: Update Precedence and conflict resolution section to include action tier as a distinct scope (not promoted to plan tier) and add non_overridable exception clause - Line 19618: Fix invariant view calculation precedence reference - Lines 19621+: Add Non-overridable global invariants documentation block Rationale: The glossary and two Strategize-phase descriptions incorrectly stated a 3-tier precedence chain (plan > project > global), contradicting ADR-016 which defines a 4-tier chain (plan > action > project > global). The implementation in actor/reconciliation.py and application/services/plan_lifecycle_service.py correctly uses the 4-tier model. The non_overridable field on the Invariant domain model was implemented but completely undocumented in the spec.	2026-04-05 08:27:30 +00:00
freemo	325f63d050	docs: update specification — add agents plan errors command ... Documents the agents plan errors CLI command in both the Command Synopsis and Command Reference sections of the specification. The command was already implemented in src/cleveragents/cli/commands/plan.py and referenced in the TUI slash catalog but was absent from the CLI documentation sections. Changes: - Command Synopsis: added 'agents plan errors <PLAN_ID>' after plan rollback - Command Reference: added '##### agents plan errors' section with synopsis, purpose, arguments, and Rich/Plain/JSON output examples Approved via proposal issue #2883. ISSUES CLOSED: #2883	2026-04-05 04:08:40 +00:00
freemo	c678fcdcc3	docs(spec): document inline PermissionQuestionWidget for single-file permission requests ... Add inline permission question widget section to TUI documentation in docs/specification.md and update ADR-044 Prompt Architecture section to distinguish between single-file (inline widget) and multi-file (PermissionsScreen) permission request handling. Changes: - docs/specification.md: Add '### Inline Permission Question Widget' section documenting PermissionQuestionWidget, InlinePermissionQuestion domain model, PermissionRequestType enum, PermissionDecision enum, keyboard shortcuts, and routing logic (single-file vs multi-file) - docs/adr/ADR-044-tui-architecture-and-framework.md: Update Prompt Architecture item 3 from QuestionWidget to PermissionQuestionWidget with inline rendering description; add QuestionWidget as item 4 for non-file-specific choices Triggered by PR #2181 (docs(tui): document PermissionQuestionWidget). Approved via proposal issue #2178. ISSUES CLOSED: #2178	2026-04-03 19:03:04 +00:00
eugen.thaci	f66fb5a19a	docs(spec): align ASCII UI tables in specification and related pages ... Align Unicode box-drawing blocks and related tables in specification.md, ADR-044/045/046, and reference pages for consistent MkDocs rendering. ISSUES CLOSED: #1171	2026-04-03 04:55:21 +00:00
freemo	48cdcb6ea7	docs(spec): remove optional parentheses from required --config flags in command synopsis (#1573) ... Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>	2026-04-02 22:00:58 +00:00
freemo	71ce95fdf6	docs(specification): reorder command synopsis to separate validation commands (#1552) ... Implements issue #1552. Reorders the command synopsis in the specification to logically group validation commands separately from regular commands for better clarity. Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>	2026-04-02 21:30:26 +00:00
freemo	6c94ad9552	Merge pull request 'fix: add --required/--informational flags to validation add CLI' (#1222) from bugfix/m5-validation-required-flag into master	2026-04-02 17:39:19 +00:00
freemo	62caf63d61	docs(spec): align spec with v3.7.0 cycle-3 implementation discoveries ... - DomainEvent: add user_identity and correlation_id fields (PR #1257) user_identity carries authenticated user in server mode (None in local mode); correlation_id is a ULID linking related events in one request chain. Both were implemented but missing from the spec model. - EventType: promote to StrEnum, add PLAN_ESTIMATION_COMPLETE, CORRECTION_APPLIED, CONFIG_CHANGED, ENTITY_DELETED, AUTH_SUCCESS, AUTH_FAILURE, TIER_PROMOTED, TIER_DEMOTED, TIER_EVICTED, VALIDATION_FIX_ATTEMPTED, VALIDATION_FIX_SUCCEEDED, VALIDATION_FIX_EXHAUSTED (all present in implementation, missing from spec enum). - Audit log event details: enrich plan_applied row with changeset statistics (lines_added, lines_removed, resources_modified, apply_duration) per PR #1300; enrich plan_cancelled row with progress context (cancelled_phase, last_completed_step, subplan_count) and resource cleanup context (sandbox_refs, changeset_id, resources_pending_cleanup) per PR #1301. - Estimation actor: document 4-level fallback chain wired in use_action() (PR #1310) and Strategize-to-Estimate lifecycle hook that emits PLAN_ESTIMATION_COMPLETE on success. ISSUES CLOSED: #1310 #1300 #1301 #1257	2026-04-02 17:34:09 +00:00
freemo	e8fa13d35c	docs(spec): align spec with v3.7.0 cycle-2 implementation discoveries ... - Add audit.* config key group (audit.retention-days, audit.async, audit.queue-maxsize) — PR #1279 added async write-behind queue to AuditService; spec had no audit config keys documented - Document UKO runtime services (UKOQueryInterface, UKOInferenceEngine, UKOGraphPersistence) — PR #1312 operationalized UKO runtime; spec described UKO conceptually but not the service API - Add UKOIndexer.index_graph() inference and layer population note No-action PRs this cycle: - #1307 (PermissionsScreen): implementation matches spec exactly - #1310 (estimation actor): spec already documents actor.default.estimation - #1278 (CorrectionDryRunReport): internal refactor, spec not affected - #1300/1301 (event enrichment): event payload details not in spec scope - #1305/1263/1262 (CLI fixes): spec alignment fixes, no spec change needed ISSUES CLOSED: none (minor clarifications only)	2026-04-02 17:19:30 +00:00
freemo	62ab0b5e65	docs(spec): align spec with v3.7.0 implementation discoveries ... - Add context slash command group (/context:inspect, :set, :simulate) to TUI slash command catalog — 70 commands across 14 groups now documented - Document AutomationGuard sub-model fields, GuardScope enum, GuardResult model, and check_guard() evaluation order (denylist→allowlist→calls→ budget→writes→apply) - Document SubplanConfig.max_parallel (default 5, range 1–50) and ThreadPoolExecutor-based parallel execution cap - Document CheckpointService operations: create_workspace_snapshot() (diff-based), selective_rollback() (atomic), archive_artifacts() All changes reflect implementation discoveries from merged PRs: #1204 (guard enforcement), #1201 (parallel scaling), #1199 (checkpoint rollback wiring), #1239 (slash command catalog), #1250 (help panel) ISSUES CLOSED: none (minor clarifications only)	2026-04-02 16:56:52 +00:00
brent.edwards	a5cc81354d	fix: add --required/--informational flags to validation add CLI ... Add --required and --informational as mutually exclusive boolean options to the `agents validation add` CLI command. When specified, they override the `mode` field from the YAML config file. This aligns the CLI with the specification (specification.md line 22339) which states the validation mode can be set "via --required/--informational on agents validation add". The fix resolves the spec contradiction by: - Implementing the flags in the CLI (per Core Concepts > Validation Mode) - Updating the formal CLI reference to include the new flags - Adding an exception to Design Principle #3 for validation add - Removing the spurious positional name argument from the walkthrough TDD tests from #1102 now run normally with @tdd_expected_fail removed. New edge-case tests cover mutual exclusivity (both flags rejected). Also excludes tool/wrapping.py from semgrep exec/compile rules since that module intentionally uses exec() in a controlled sandbox for the validation transform feature. ISSUES CLOSED: #1038	2026-03-31 07:42:06 +00:00
freemo	532ea100e3	Docs: updated spec with --image tag	2026-03-30 22:12:17 -04:00
CoreRasurae	007af498b8	refactor(autonomy): rename automation profile task flags to spec names ... Renamed all 11 task-type confidence threshold fields in AutomationProfile from phase-transition semantics to spec-defined task-type semantics. Updated all 8 built-in profiles, CLI formatting, YAML schema, services, and all Behave/Robot tests referencing the old field names. Post-review fixes: - Fixed 24 stale old field names in M6 fixture files (automation_profiles.json, autonomy_guardrails.json) - Added model_validator(mode='before') to detect legacy field names and raise actionable ValueError with rename mapping - Added semantic bridge comments in PlanLifecycleService mapping task-type thresholds to phase-transition gates - Added threshold_field to structured log messages for observability - Restored categorised CLI automation-profile show output to match spec (Phase Transitions / Decision Automation / Self-Repair / Execution Controls) instead of flat list - Added missing access_network field to spec show output examples (Rich, Plain, JSON, YAML variants) - Aligned ADR-017 profile fields table to all 11 fields with descriptions matching spec Automatable Tasks table - Aligned automation_profiles.md threshold descriptions with spec - Added spec section references in phase_reversion.md, error_recovery.md, and plan_execute.md for field naming context - Extended repository roundtrip test to assert all 11 threshold fields - Fixed benchmark _make_profile() passing safety fields as top-level kwargs instead of via SafetyProfile sub-model (incompatible with extra="forbid") - Aligned CLI JSON/YAML output structure for automation-profile show with the specification grouped format (phase_transitions, decision_automation, self_repair, execution_controls) - Moved safety boolean fields into the Execution Controls section of Rich output per spec examples - Reverted auto profile description to "Fully automatic except apply" per specification (line 16703, line 28406) - Improved bridge comments in test steps with semantic context for threshold-to-gate mappings ISSUES CLOSED: #902	2026-03-30 13:18:07 +01:00
freemo	c65e8a5285	feat(resource): add cloud infrastructure resources ... Implement cloud resource types (aws, gcp, azure) with credential fields, region/tenant metadata, and stubbed sandbox strategies. Credential resolution uses environment variables and profile names with no secrets logged. Key changes: - Add CloudResourceHandler with aws/gcp/azure type definitions - Add credential resolution from env vars and profile names - Add stubbed sandbox strategies (validate config, raise NotImplementedError) - Register cloud types in bootstrap_builtin_types - Credential masking via existing redaction patterns - Add Behave BDD tests, Robot integration tests, ASV benchmarks ISSUES CLOSED: #343	2026-03-17 13:14:37 -04:00
freemo	d5b122d4a3	Docs: Updated to A2A and integrating rest standard	2026-03-11 13:19:55 -04:00
freemo	e98c8e6c79	Docs: Added and revised server-client protocol details	2026-03-11 10:02:27 -04:00
freemo	82def1112b	docs(tui): promote TUI to top-level section and fix mkdocs nav warnings ... Restructure the TUI specification from a nested subsection under "Behavior > UI / Interaction Model" to a top-level "## TUI" section, giving it equal standing with Core Concepts, Behavior, Configuration, and Architecture. All headings within the TUI section are promoted one level (#### → ###, ##### → ####). Fix mkdocs build nav warnings by adding ADR-044/045/046 to the mkdocs.yml nav and registering three missing reference pages (acms_fusion, context_indexing, resource_type_inheritance) in the gen_ref_pages.py nav builder.	2026-03-11 00:39:57 -04:00
freemo	c129ea5098	docs(tui): add exhaustive detail for block cursor, settings, notifications, per-window hotkeys, and secondary screens ... Expand the TUI specification section with comprehensive detail that was identified as missing in a gap analysis against the original design prompt and Toad TUI feature inventory. The flat "Global Hotkey Reference" table is replaced with 16 per-window/overlay hotkey tables. New specification content: Block Cursor and Context Menu: - Block cursor navigation (alt+up/down, space, enter) - Floating context menu with 7 actions: copy to clipboard (c), copy to prompt (p), export as Markdown (e), export as SVG (v), maximize (m), retry (r), show raw data (d) - New diagram: context menu popup Conversation Block Details: - Tool call states with 4 lifecycle phases (pending, completed collapsed, completed expanded, failed) and tools.expand setting (never/always/ success/fail/both) - Actor thought block with collapsed (max 10 lines) and expanded states - Permission question widget with allow/reject options and queue behavior - New diagrams: tool call states, thought block, question widget Prompt Architecture Detail: - History navigation with per-mode JSONL files (prompt vs shell), up/down at start/end of TextArea, 10K entry cap - Key passthrough from conversation Window to prompt on printable chars - Multiline detection (newlines, triple backticks, shift+enter) - Shell danger detection with heuristic patterns (rm -rf, chmod 777, dd, fork bombs, mkfs, sudo) and configurable shell.warn_dangerous setting Notification System: - Flash messages (4 semantic styles: default, success, warning, error) - Desktop notifications via notifypy (never/on-blur/always), 5 trigger events, low-severity suppression - Terminal title management with VT escape sequences, state-dependent icons, and configurable blink on input-needed - Sound effects (4 event sounds, graceful degradation) Clipboard Operations: - Auto-copy on selection (ui.auto_copy), block copy via context menu, pyperclip with OSC 52 fallback Session Persistence and Resume: - SQLite storage schema (10 columns) at ~/.local/state/cleveragents/tui.db - 6-step resume workflow via ctrl+r or /session:import Sessions Screen: - New diagram: sessions modal with active + saved session sections - Time formatting, session state indicators, keyboard bindings Settings Screen: - New diagram: schema-driven settings modal with search - Complete settings schema: 7 categories, 30+ settings with types, defaults, ranges, and descriptions (UI, notifications, sidebar, agent, tools, shell, diff) Additional Features: - Conversation content pruning (prune_low_mark/prune_excess thresholds) - Double-tap safety (ctrl+c 5s quit window, escape 400ms terminal exit) - Loading states (rainbow throbber + rotating quotes alternative) - Conversation export (JSON, Markdown, per-block SVG) - Column width and scrollbar configuration Per-Window Hotkey Tables (16 tables replacing 1 flat table): - Global, MainScreen prompt, MainScreen conversation/cursor, block context menu, terminal focused, sidebar visible, sidebar fullscreen, reference picker (search + tree modes), slash command overlay, plan detail modal, project detail modal, persona editor modal, permissions screen, settings screen, sessions screen, question widget, help panel	2026-03-11 00:39:57 -04:00
freemo	56f3b49725	docs(tui): add comprehensive TUI specification with 18 aligned ASCII mockup diagrams ... Add the complete TUI (Terminal User Interface) specification section to docs/specification.md, covering architecture, layout, navigation, persona system, reference picker, slash commands, shell mode, session management, and keyboard shortcuts. The section includes 18 HTML-styled ASCII mockup diagrams using the Dracula color palette that render with actual colors in MkDocs. Key specification areas: - MainScreen layout with right-side collapsible sidebar (3 states: hidden, visible, fullscreen cycled by shift+tab) - Direct-to-chat launch with first-run actor selection overlay - Persona system bundling actor + arguments + project/plan scope, cycled with tab; argument presets cycled with ctrl+tab - @ reference picker with fuzzy search for projects/plans/resources - / slash commands mirroring CLI noun:verb patterns (session:new, plan:list, project:show, actor:switch, etc.) - ! shell mode for direct command execution - Multi-session tabs with independent personas and conversations - Escape-cascading navigation back to main screen - Plan detail view with decision tree navigation - Project detail view with resource DAG - Permission approval workflow with diff view - Complete keyboard shortcut reference table New ADR files: - ADR-044: TUI Architecture and Framework (Textual >= 1.0) - ADR-045: TUI Persona System - ADR-046: TUI Reference and Command System (CLI-aligned commands) Also adds TUI mockup CSS classes to docs/stylesheets/extra.css for Dracula-palette diagram rendering (.tui-primary, .tui-secondary, .tui-success, .tui-warning, .tui-error, .tui-dim, .tui-bold, .tui-bold-primary, .tui-bold-warning, .tui-primary-u, .tui-rainbow).	2026-03-11 00:39:57 -04:00
CoreRasurae	cf67ba0a86	feat(devcontainer): add lazy activation and lifecycle management ... Implemented lazy container activation for devcontainer-instance resources with ContainerLifecycleState enum tracking six states (inactive, starting, active, stopping, stopped, error) with validated transitions. Extended DevcontainerHandler with devcontainer up CLI integration and JSON output parsing for container start. Added periodic health checking via devcontainer exec ping with configurable interval. Added agents resource stop and agents resource rebuild CLI commands for manual lifecycle control. Wired session close and plan completion hooks to automatic container cleanup. Includes lifecycle state persistence in resource registry with timestamped transitions. Added Behave BDD tests, Robot integration tests, and ASV activation latency benchmarks. - Added remoteWorkspaceFolder absolute-path validation - Aligned spec: handler name, rebuild types, --yes flag on stop/rebuild - Added registry re-read in stop_container success path for consistency - Added session_id field to ContainerLifecycleTracker for scoped cleanup - Scoped stop_all_active_containers to session_id when provided - Wired _cleanup_devcontainers into fail_apply and fail_execute - Wired start_health_check into activate_container success path - Restructured facade session close to always run container cleanup even without session service (F4) - Re-read tracker from registry in activate_container success path - Added evict_terminal_trackers to cap registry growth - Updated devcontainer_resources.md: health check auto-start, scoped cleanup hooks, known limitations for eviction and sandbox_strategy - Wired evict_terminal_trackers into stop_all_active_containers so terminal-state trackers are actually evicted in production - Made stop_container idempotent: returns early when container is already in a terminal state instead of raising ValueError - Fixed benchmark health check thread leak in TimeActivationLatency by clearing registry after each timing loop - Added rebuild pass-through (--reset-container flag to devcontainer up) - Added host_workspace_path field on ContainerLifecycleTracker so health probes use the host-side path for devcontainer exec - Wired lazy activation into DevcontainerHandler.resolve() for devcontainer-instance resources in non-running states - Changed _default_strategy from SNAPSHOT to NONE (container itself provides isolation; SandboxFactory raises NotImplementedError for snapshot) - Restricted _STOPPABLE_TYPES to devcontainer-instance only (container-instance is not directly stoppable via CLI) ISSUES CLOSED: #514	2026-03-10 12:17:51 +00:00
CoreRasurae	23803f14ec	feat(lsp): add LSP server stub ... Added minimal LSP server entrypoint supporting initialize/shutdown/exit handshake over JSON-RPC stdin/stdout transport with Content-Length framing. Unsupported methods return MethodNotFound error with descriptive message. Wired LSP requests through ACP facade in local mode. Added agents lsp serve CLI command with --log-level flag, PID output, and startup banner. Created reference documentation for the stub server. Includes Behave BDD tests for protocol handshake, Robot smoke test, and ASV startup latency benchmark. ISSUES CLOSED: #203	2026-03-06 18:16:47 +00:00
freemo	05310391c1	docs(spec): add devcontainer integration and resource type inheritance ... Created ADR-042 (Resource Type Inheritance) defining single-inheritance `inherits` field on resource type definitions with field resolution, collection merging, handler inheritance, polymorphic tool binding, auto-discovery, and DAG query matching. Max depth 5, single inheritance. Created ADR-043 (Devcontainer Integration) defining devcontainer-instance as a subtype of container-instance with lazy activation lifecycle, devcontainer.json parsing, three container-project association patterns (auto-detect, explicit mount, clone-into), and execution environment routing with a 6-level precedence chain. Specification updates across 20+ sections: - Glossary: Resource Type Inheritance, Devcontainer, Execution Environment - Resource type YAML schema: `inherits` field with structure reference - Handler, sandbox strategy, and coherence tables: devcontainer-instance - Auto-discovery: devcontainer detection subsection with WBS diagram - Tool capability metadata: structured environment subfields - Technology stack: devcontainer CLI row - Project model: execution environment subsection with YAML example - CLI agents resource add: --mount, --clone-into flags + 4 new examples - CLI agents plan use: --execution-environment, --execution-env-priority - CLI agents project context set: same execution environment flags - Command synopsis block: updated for all new flags - Execution environment routing section with precedence table + algorithm - Resource type YAML Example 6: Devcontainer Instance (inherited type) - End-to-end Example 16: Devcontainer-Driven Development - End-to-end Example 17: Explicit Container with Directory Mount - End-to-end Example 18: Container with Remote Repo Clone Also fixed ADR index: added missing ADR-036 through ADR-040 entries, updated next ADR number to 044. CONTRIBUTING.md fixes backported from sister project: - Fixed State label capitalization (State/In Progress -> State/In progress, State/In Review -> State/In review) to match label definitions. - Subtasks section: changed from optional to required, with exception clause for trivially simple issues. - Parent links: updated to use Forgejo dependency system instead of textual references in issue descriptions. - Fixed nox session flag typos: nox -e -> nox -s (7 occurrences). - Replaced "Epics and Legendaries" section with comprehensive "Ticket Type Hierarchy" defining the three-tier hierarchy (Issue -> Epic -> Legendary) with formal criteria tables, cross-cutting rules for hierarchy enforcement, completion semantics, promotion/demotion, and milestone relationship rules. - Fixed broken internal links referencing old "Epics and Legendaries" anchor to use "Ticket Type Hierarchy" (3 occurrences). - Traceability example: replaced project-specific code reference with generic example. - Removed stray horizontal rule before Project-Specific Guidelines. ISSUES CLOSED: #491	2026-03-01 20:04:10 +00:00
freemo	c825935309	docs(spec): recognize SafetyProfile as composed sub-model of AutomationProfile ... Add SafetyProfile as a first-class concept in the specification, composed within AutomationProfile via a 'safety' field. This eliminates the dual-authority problem where both AutomationProfile and a separate SafetyProfile defined the same three safety booleans (require_sandbox, require_checkpoints, allow_unsafe_tools) with no spec-defined resolution. Changes: - specification.md: Add Safety Profile glossary entry, split Automatable Tasks into thresholds + Safety Profile sub-section, update built-in profile matrix with safety.* prefix, update YAML examples - ADR-041 (new): Document composition decision, field schema, relationship to Guards, constraints, consequences, rejected alternatives (inheritance, mixin, flat) - ADR-017: Update profile fields table, built-in profiles, constraints, risks, and cross-reference to ADR-041 - reference/automation_profiles.md: Rename Safety Fields to Safety Profile sub-section, expand built-in matrix, update YAML examples - schema/automation_profile.schema.yaml: Nest safety fields under safety object with all SafetyProfile fields - adr/index.md: Add ADR-041 to Tier 3 inventory Resolves spec gap identified in issue #332.	2026-02-28 01:02:55 +00:00
CoreRasurae	8604bc66b6	fix(security): enforce explicit exception handling ... ISSUES CLOSED: #320	2026-02-25 10:05:57 +00:00
freemo	09c2567d60	docs: Moved the last elements from implementation plan to their respective locations and deleted the plan from the repo ... Refs: #408	2026-02-23 17:53:26 -05:00
freemo	69b99d49e6	docs: Moved the implementation timeline out to its own document ... Refs: #408	2026-02-23 17:52:59 -05:00
freemo	bb7612c0d3	Docs: Daily update to implementation plan	2026-02-23 12:31:07 -05:00
freemo	55f83771b9	Docs: Added gantt charts to Implementation Timeline section	2026-02-23 01:11:36 -05:00
freemo	18b7cf8107	Docs: daily update to implementation plan	2026-02-22 17:12:54 -05:00
freemo	431f827ac4	Docs: Added implementation timeline to specification, seperate from the implementation plan itself.	2026-02-22 01:15:03 -05:00
freemo	e28f9a8597	Docs: Add resource DAG operational semantics, tool reachability, cross-mechanism coordination, container, and LSP resource type ADRs (036-040) ... - ADR-036: Resource DAG Operational Semantics (10 purposes, sandbox boundary algebra) - ADR-037: Tool Reachability and Access Projection (transitive reach, read/write routing) - ADR-038: Cross-Mechanism Sandbox Coordination (coherence, write-then-sync, lazy materialization) - ADR-039: Container and Execution Environment Resource Types (9 engine-agnostic types) - ADR-040: Language Server Protocol Resource Types (lsp-server, lsp-workspace, lsp-document) - Updated specification.md with 7 new subsections for operational semantics - Updated resource_dag.md reference doc with operational semantics section - Updated ADR-008, ADR-011, ADR-015, ADR-027 with cross-references - Resolved merge conflicts from cherry-pick renumbering (033-037 -> 036-040) - Fixed all stale display-text references across all files	2026-02-21 19:51:28 -05:00
freemo	b4c73505d8	Docs: Fixed some contradictions and ambiguity in the specification document	2026-02-21 18:04:15 -05:00