ocaya 2.14.0__py3-none-any.whl

.kiro/specs/ocaya/.config.kiro

@@ -0,0 +1 @@
+{"specId": "c355ffb6-2295-4000-b342-f7d0e63324c7", "workflowType": "requirements-first", "specType": "feature"}

.kiro/specs/ocaya/design.md

@@ -0,0 +1,464 @@
+# Design Document: OCAYA
+
+## Overview
+
+OCAYA is a rebrand and repurpose of the open-source `mistral-vibe` Python CLI. This is not a new architecture — it is a targeted transformation across three concerns:
+
+1. **Identity rename** — every package name, class name, path, environment variable, log filename, and TUI string that says "vibe" or "Mistral Vibe" becomes "ocaya" or "OCAYA".
+2. **Persona swap** — the default system prompt changes from a coding-focused instruction document (`cli.md`) to a web-first general-purpose instruction document (`ocaya.md`).
+3. **Tool enablement** — two already-drafted tools (`clipboard.py`, `open_app.py`) are confirmed as active built-ins and any rough edges in their implementation are cleaned up.
+
+Mistral AI remains the sole LLM backend. Browser automation (Playwright, browser-use, Selenium) is explicitly out of scope.
+
+### Key Design Constraints
+
+- No new architectural layers are introduced.
+- The agent loop, session mechanics, MCP/ACP bridge, voice pipeline, skills system, and all existing tool logic are preserved verbatim.
+- The `env_prefix="VIBE_"` in `OcayaConfig` is **preserved** — the requirement only mandates renaming `VIBE_HOME` (which is resolved outside of the pydantic-settings env prefix, in the paths module). Changing `env_prefix` would silently break all existing user `VIBE_*` config env vars; this change is intentionally deferred.
+- The `clipboard.py` and `open_app.py` files already exist in the builtins directory and are auto-discovered by `ToolManager` — no explicit registration code is required beyond verifying the files are valid and their import paths are updated to `ocaya.*`.
+
+---
+
+## Architecture
+
+The transformation is a layer-by-layer rename following dependency order. No new components are added; existing components are updated in place.
+
+```
+┌─────────────────────────────────────────────────────────┐
+│  pyproject.toml  (package name, scripts, tool config)   │
+├─────────────────────────────────────────────────────────┤
+│  ocaya/  (was: vibe/)                                   │
+│  ├── __init__.py          OCAYA_ROOT, __version__       │
+│  ├── acp/                 ACP server (unchanged logic)  │
+│  ├── cli/                 Textual TUI  ← branding here  │
+│  └── core/                                              │
+│       ├── agents/models.py   VibeConfig ref → OcayaConfig│
+│       ├── config/_settings.py  VibeConfig → OcayaConfig │
+│       ├── paths/_ocaya_home.py  was: _vibe_home.py      │
+│       ├── prompts/                                      │
+│       │   ├── __init__.py  SystemPrompt.OCAYA added     │
+│       │   └── ocaya.md     new default system prompt    │
+│       ├── tools/builtins/                               │
+│       │   ├── clipboard.py  import path updated         │
+│       │   └── open_app.py   import path updated         │
+│       └── skills/builtins/ocaya.py  was: vibe.py        │
+├─────────────────────────────────────────────────────────┤
+│  tests/  (import paths updated: vibe. → ocaya.)         │
+└─────────────────────────────────────────────────────────┘
+```
+
+### Migration Order
+
+Changes must be applied in this order to avoid import errors at any intermediate state:
+
+1. Rename `vibe/` → `ocaya/` (the physical directory rename)
+2. Update `ocaya/__init__.py` — rename `VIBE_ROOT` → `OCAYA_ROOT`
+3. Update `ocaya/core/paths/_vibe_home.py` → `_ocaya_home.py`
+4. Update `ocaya/core/prompts/__init__.py` — add `SystemPrompt.OCAYA`, update `PROMPTS_DIR`
+5. Create `ocaya/core/prompts/ocaya.md`
+6. Update `ocaya/core/config/_settings.py` — rename `VibeConfig` → `OcayaConfig`, update `system_prompt_id` default
+7. Update `ocaya/core/agents/models.py` — update all `VibeConfig` references
+8. Update all other `ocaya/**/*.py` files — fix import paths and string constants
+9. Update `ocaya/core/tools/builtins/clipboard.py` and `open_app.py` — fix import paths
+10. Update `ocaya/core/skills/builtins/vibe.py` → `ocaya.py` — content update
+11. Update TUI branding strings in `ocaya/cli/`
+12. Update `pyproject.toml`
+13. Update all `tests/**/*.py` files — fix import paths
+
+---
+
+## Components and Interfaces
+
+### pyproject.toml
+
+| Field | Before | After |
+|---|---|---|
+| `[project] name` | `"mistral-vibe"` | `"ocaya"` |
+| `[project] description` | `"Minimal CLI coding agent by Mistral"` | `"OCAYA — web-first general-purpose AI assistant"` |
+| `[project] keywords` | includes `"coding-assistant"`, `"mistral-vibe"` | replace with `"ocaya"`, `"general-assistant"` |
+| `[project.scripts] vibe` | `"vibe.cli.entrypoint:main"` | removed |
+| `[project.scripts] ocaya` | (absent) | `"ocaya.cli.entrypoint:main"` |
+| `[project.scripts] vibe-acp` | `"vibe.acp.entrypoint:main"` | removed |
+| `[project.scripts] ocaya-acp` | (absent) | `"ocaya.acp.entrypoint:main"` |
+| `[tool.hatch.build.targets.wheel] include` | `["vibe/"]` | `["ocaya/"]` |
+| `[tool.pyright] include` | `["vibe/**/*.py", ...]` | `["ocaya/**/*.py", ...]` |
+| `[tool.ruff] include` | `["vibe/**/*.py", ...]` | `["ocaya/**/*.py", ...]` |
+| `[tool.ruff.lint.isort] known-first-party` | `["vibe"]` | `["ocaya"]` |
+
+Project URLs pointing to GitHub repository path segments (e.g. `mistralai/mistral-vibe`) are left unchanged as they are not human-readable branding fields.
+
+### `ocaya/__init__.py`
+
+```python
+OCAYA_ROOT = Path(__file__).parent
+__version__ = "2.14.0"
+```
+
+`VIBE_ROOT` is removed. All internal references to `VIBE_ROOT` become `OCAYA_ROOT`.
+
+### `ocaya/core/paths/_ocaya_home.py` (was `_vibe_home.py`)
+
+Full replacement:
+
+```python
+from __future__ import annotations
+
+from collections.abc import Callable
+import os
+from pathlib import Path
+
+from ocaya import OCAYA_ROOT
+
+
+class GlobalPath:
+    def __init__(self, resolver: Callable[[], Path]) -> None:
+        self._resolver = resolver
+
+    @property
+    def path(self) -> Path:
+        return self._resolver()
+
+
+_DEFAULT_OCAYA_HOME = Path.home() / ".ocaya"
+
+
+def _get_ocaya_home() -> Path:
+    if ocaya_home := os.getenv("OCAYA_HOME"):
+        return Path(ocaya_home).expanduser().resolve()
+    return _DEFAULT_OCAYA_HOME
+
+
+OCAYA_HOME = GlobalPath(_get_ocaya_home)
+GLOBAL_ENV_FILE = GlobalPath(lambda: OCAYA_HOME.path / ".env")
+SESSION_LOG_DIR = GlobalPath(lambda: OCAYA_HOME.path / "logs" / "session")
+TRUSTED_FOLDERS_FILE = GlobalPath(lambda: OCAYA_HOME.path / "trusted_folders.toml")
+LOG_DIR = GlobalPath(lambda: OCAYA_HOME.path / "logs")
+LOG_FILE = GlobalPath(lambda: OCAYA_HOME.path / "logs" / "ocaya.log")
+CACHE_FILE = GlobalPath(lambda: OCAYA_HOME.path / "cache.toml")
+HISTORY_FILE = GlobalPath(lambda: OCAYA_HOME.path / "ocayahistory")
+PLANS_DIR = GlobalPath(lambda: OCAYA_HOME.path / "plans")
+
+DEFAULT_TOOL_DIR = GlobalPath(lambda: OCAYA_ROOT / "core" / "tools" / "builtins")
+```
+
+The `paths/__init__.py` re-export must be updated: all exported names (`VIBE_HOME`, `LOG_FILE`, `HISTORY_FILE`, etc.) are renamed to match.
+
+### `ocaya/core/config/_settings.py`
+
+Two targeted changes:
+
+**1. Class rename:**
+```python
+# Before
+class VibeConfig(BaseSettings):
+    ...
+
+# After
+class OcayaConfig(BaseSettings):
+    ...
+```
+
+**2. `system_prompt_id` default:**
+```python
+# Before
+system_prompt_id: str = SystemPrompt.CLI
+
+# After
+system_prompt_id: str = SystemPrompt.OCAYA
+```
+
+**3. `env_prefix` stays as `"VIBE_"`** — preserves all existing user `VIBE_*` environment variable overrides. The requirement for renaming `VIBE_HOME` is handled entirely in the paths module (direct `os.getenv("OCAYA_HOME")` call), which is architecturally separate from pydantic-settings' env prefix mechanism.
+
+**4. Internal model validators** referencing `VibeConfig` by name in type annotations (`-> VibeConfig`) are updated to `-> OcayaConfig`.
+
+**5. `DEFAULT_VIBE_BASE_URL` constant:** The variable name `DEFAULT_VIBE_BASE_URL` and `vibe_base_url` field name are internal Python identifiers that map to an external Mistral service URL (`chat.mistral.ai`). Renaming these would require either a field alias or a user-visible config key change. Since the backing URL is a Mistral-owned endpoint and changing the config key would break existing `config.toml` files, these internal identifiers are renamed to `DEFAULT_OCAYA_BASE_URL` / `ocaya_base_url` with a `validation_alias` to accept the legacy `vibe_base_url` key from existing config files.
+
+### `ocaya/core/prompts/__init__.py`
+
+```python
+class SystemPrompt(Prompt):
+    OCAYA = auto()   # new — points to ocaya.md
+    CLI = auto()     # kept for backward compatibility (custom system_prompt_id="cli")
+    EXPLORE = auto()
+    TESTS = auto()
+    LEAN = auto()
+    MINIMAL = auto()
+```
+
+`OCAYA` is added as the first member so it occupies the `"ocaya"` value. `CLI` is kept so that any user who has `system_prompt_id = "cli"` in their `config.toml` continues to work.
+
+`PROMPTS_DIR` changes from `VIBE_ROOT / "core" / "prompts"` to `OCAYA_ROOT / "core" / "prompts"`.
+
+### `ocaya/core/agents/models.py`
+
+- All `TYPE_CHECKING` imports of `VibeConfig` → `OcayaConfig`.
+- The `apply_to_config` method signature: `base: OcayaConfig` and local import `from ocaya.core.config import OcayaConfig as OC`.
+- The `EXPLORE` agent's `overrides` already uses `"system_prompt_id": "explore"` — no change needed there.
+- All `from vibe.*` imports → `from ocaya.*`.
+
+### `ocaya/core/tools/builtins/clipboard.py` and `open_app.py`
+
+Both files exist and are functionally complete. The only required change is updating all `from vibe.core.*` imports to `from ocaya.core.*`. No logic changes.
+
+The `ToolManager` auto-discovers all non-underscore-prefixed `.py` files under `DEFAULT_TOOL_DIR` (which now resolves to `ocaya/core/tools/builtins/`). Both files are already there — no registration code change is needed.
+
+The `_compute_module_name` function in `manager.py` uses `parts.index("vibe")` to detect canonical module names. After renaming, this must be updated to detect `"ocaya"` instead.
+
+### `ocaya/core/skills/builtins/ocaya.py` (was `vibe.py`)
+
+The file is renamed and the `SkillInfo` content is updated:
+
+```python
+SKILL = SkillInfo(
+    name="ocaya",
+    description="Understand the OCAYA application internals: configuration, OCAYA_HOME structure, ...",
+    user_invocable=False,
+    prompt="""# OCAYA Self-Awareness
+    ...
+    """,
+)
+```
+
+All occurrences of `~/.vibe`, `VIBE_HOME`, `vibe.log`, `vibehistory`, `Mistral Vibe`, and `vibe` (as product name) in the skill prompt are updated to their OCAYA equivalents. The `.vibe/` project-local config directory references become `.ocaya/`.
+
+### TUI Branding (`ocaya/cli/`)
+
+The Textual TUI uses string constants scattered across several widgets. The following surfaces must be audited and updated:
+
+| Surface | Location | Change |
+|---|---|---|
+| App title | `App` CSS / `TITLE` class var | `"Mistral Vibe"` → `"OCAYA"` |
+| Startup splash/banner | `WelcomeWidget` or equivalent | Remove ASCII art; replace with `"OCAYA"` heading |
+| Status bar agent name | `StatusBar` widget | Label text → `"OCAYA"` |
+| Help panel heading | `HelpPanel` widget | `"Mistral Vibe Help"` → `"OCAYA Help"` |
+| Error dialogs | Any `ModalScreen` / `Dialog` with branding | Replace legacy branding with `"OCAYA"` |
+| Version string | `--version` flag handler, startup banner | Format: `f"OCAYA {__version__}"` |
+
+No CSS color variables, layout, or animation logic is changed.
+
+### `tests/` directory
+
+Every test file that imports from `vibe.*` is updated to import from `ocaya.*`. The `tests/conftest.py` autouse fixtures (`config_dir`, `tmp_working_directory`) that reference `VIBE_HOME` / `~/.vibe` are updated to reference `OCAYA_HOME` / `~/.ocaya`.
+
+---
+
+## Data Models
+
+### `OcayaConfig` (was `VibeConfig`)
+
+```python
+class OcayaConfig(BaseSettings):
+    system_prompt_id: str = SystemPrompt.OCAYA   # was: SystemPrompt.CLI = "cli"
+    # All other fields: unchanged
+    model_config = SettingsConfigDict(
+        env_prefix="VIBE_",   # preserved — see rationale above
+        case_sensitive=False,
+        extra="ignore",
+    )
+```
+
+No fields are added or removed. The only data model change is the `system_prompt_id` default.
+
+### `SystemPrompt` enum
+
+```python
+class SystemPrompt(Prompt):
+    OCAYA = auto()    # value: "ocaya"  — new default
+    CLI = auto()      # value: "cli"    — preserved for compatibility
+    EXPLORE = auto()
+    TESTS = auto()
+    LEAN = auto()
+    MINIMAL = auto()
+```
+
+The `OCAYA` member must be ordered first so its `auto()` value is `"ocaya"`. Because `StrEnum` with `auto()` derives the string value from the member name lowercased, member order relative to each other does not matter for value correctness — what matters is the name.
+
+### Path constants
+
+| Old constant | New constant | Old value | New value |
+|---|---|---|---|
+| `VIBE_HOME` | `OCAYA_HOME` | `~/.vibe` | `~/.ocaya` |
+| `LOG_FILE` | `LOG_FILE` | `~/.vibe/logs/vibe.log` | `~/.ocaya/logs/ocaya.log` |
+| `HISTORY_FILE` | `HISTORY_FILE` | `~/.vibe/vibehistory` | `~/.ocaya/ocayahistory` |
+| `VIBE_ROOT` | `OCAYA_ROOT` | `Path(__file__).parent` | `Path(__file__).parent` |
+
+---
+
+## System Prompt Design (`ocaya/core/prompts/ocaya.md`)
+
+The `ocaya.md` file replaces `cli.md` as the default system prompt. It must cover all seven required areas. The structure below is the authoritative outline:
+
+### Required Sections
+
+**1. Identity**
+```
+You are OCAYA, a capable general-purpose AI assistant. Today's date is $current_date.
+```
+Must not contain "Mistral Vibe", "Jarvis", or "Hermes". Must contain "OCAYA".
+
+**2. Capabilities**
+Explicit list (per Requirements 5.5, 9.4):
+- Web research and summarisation
+- Document writing and editing
+- File and folder management
+- System automation and scripting
+- Opening applications and URLs
+- Clipboard operations
+- General knowledge Q&A
+
+This section must NOT restrict the agent to coding tasks (per Requirement 9.3).
+
+**3. Web-First Instructions**
+Explicit instruction (per Requirements 5.6, 6.1, 6.3):
+- Before answering any query involving current events, live prices, external documentation, news, or user-provided URLs, invoke `websearch` or `webfetch` first — never rely on training-data memory alone for these categories.
+- When a user message contains a URL, invoke `webfetch` with that URL before responding.
+- Include at least one source citation (title + URL) whenever information was obtained via `websearch`.
+
+**4. Action-First Principle**
+Instruction (per Requirement 5.4):
+- Take action first, explain after. Do not ask clarifying questions when the task is clear enough to attempt.
+- For file operations, scripting, or software installation, use the `bash` tool to perform the operation rather than only describing it.
+
+**5. Hard Limits**
+Explicit prohibitions (per Requirement 5.7):
+- Do not run `git commit`, `git push`, or any remote-push variant without explicit user instruction.
+- Do not delete files without asking for confirmation.
+- Do not send emails, post to social media, or initiate financial transactions without explicit user instruction.
+- Before executing any shell command with blast radius outside the current machine, state the risk in one sentence and wait for confirmation.
+
+**6. Tone**
+Instruction (per Requirement 5.4):
+- Be direct and warm. Skip filler phrases: no "Certainly", "Of course", "Happy to", "Great question".
+- Keep responses focused. Code and structured output before prose.
+
+**7. Source Citation**
+Instruction (per Requirement 6.3):
+- Whenever information was retrieved via `websearch`, include at least one inline citation with the source title and URL.
+
+---
+
+## Correctness Properties
+
+*A property is a characteristic or behavior that should hold true across all valid executions of a system — essentially, a formal statement about what the system should do. Properties serve as the bridge between human-readable specifications and machine-verifiable correctness guarantees.*
+
+Most of this feature's changes are identity/rename operations verified by static assertions or example-based tests. Three areas yield genuine universal properties suitable for property-based testing.
+
+### Property 1: OCAYA_HOME Path Resolution
+
+*For any* non-empty string `p`, when the `OCAYA_HOME` environment variable is set to `p`, calling `_get_ocaya_home()` should return `Path(p).expanduser().resolve()` — that is, the path is always fully normalized regardless of the form of the input string (relative, absolute, `~`-prefixed, with redundant separators, etc.).
+**Validates: Requirements 2.2**
+
+### Property 2: Version String Prefix
+
+*For any* valid version string `v` (e.g. `"2.14.0"`, `"3.0.0-alpha"`, `"1.0"`), the formatted version display string should start with `"OCAYA "` followed by `v`, regardless of the version value.
+**Validates: Requirements 4.3**
+
+### Property 3: OpenApp Rejects All Blank Targets
+
+*For any* string composed entirely of whitespace characters (including the empty string, strings of spaces, tabs, newlines, or any combination), invoking `OpenApp.run` with that string as the `target` argument should raise a `ToolError` with the message `"target cannot be empty"`.
+**Validates: Requirements 8.6**
+
+---
+
+## Error Handling
+
+### Home Directory Resolution
+
+- If `OCAYA_HOME` is set to an empty string: `os.getenv("OCAYA_HOME")` returns `""` which is falsy; the walrus operator branch is not taken and the default `~/.ocaya` is used. No warning is required for the empty-string case because the env var being unset is semantically equivalent.
+- If `OCAYA_HOME` points to a non-existent but resolvable path: `Path(...).expanduser().resolve()` succeeds; the directory is created on first access by the setup layer.
+- If `OCAYA_HOME` is set to an unresolvable path (e.g. contains null bytes): `Path()` construction raises `ValueError`; this propagates as a startup error with a message printed to stderr.
+
+### Prompt Loading Fallback
+
+`load_system_prompt` already implements a fallback chain: custom project/user prompt dirs → built-in enum prompt → fallback `.md` file in `PROMPTS_DIR`. If a user has a custom `system_prompt_id` that resolves to a missing file, `MissingPromptFileError` is raised. Requirement 5.8 specifies a softer fallback (fall back to `ocaya.md`, log warning, continue). This requires wrapping the `load_system_prompt` call in the config property:
+
+```python
+@property
+def system_prompt(self) -> str:
+    try:
+        return load_system_prompt(self.system_prompt_id)
+    except MissingPromptFileError:
+        logger.warning(
+            "system_prompt_id=%s not found; falling back to ocaya",
+            self.system_prompt_id,
+        )
+        return load_system_prompt(SystemPrompt.OCAYA)
+```
+
+### Tool Discovery After Rename
+
+`ToolManager._compute_module_name` uses `parts.index("vibe")` to detect canonical module names for deduplication. After the package rename this must become `parts.index("ocaya")`. If it is left as `"vibe"`, every builtin tool gets a hash-based synthetic module name instead of its canonical `ocaya.core.tools.builtins.*` name, causing Pydantic class identity mismatches (two copies of `ClipboardArgs` etc.). This is a subtle correctness issue that must be fixed as part of the rename.
+
+### Clipboard and OpenApp on Linux Without Desktop Utilities
+
+Both tools have explicit `ToolError` paths for missing `xclip`/`xsel` (clipboard) and `xdg-open`/`gio` (open_app). These are already implemented in the drafted files — no additional error handling is needed. The error messages already name the missing utility and provide the `apt install` instruction as required by Requirements 7.4 and 8.7.
+
+---
+
+## Testing Strategy
+
+### Unit Tests (example-based)
+
+Focus on concrete behavioral assertions:
+
+- `test_ocaya_home_default`: assert `_get_ocaya_home()` with no env var returns `Path.home() / ".ocaya"`.
+- `test_ocaya_config_defaults`: assert `OcayaConfig()` has `system_prompt_id == "ocaya"`.
+- `test_system_prompt_loads_ocaya_md`: assert `OcayaConfig().system_prompt` contains `"OCAYA"` and does not contain `"Mistral Vibe"`.
+- `test_system_prompt_fallback`: assert that a missing custom `system_prompt_id` falls back to `ocaya.md` and logs a warning.
+- `test_clipboard_config_permission`: assert `ClipboardConfig().permission == ToolPermission.ASK`.
+- `test_open_app_config_permission`: assert `OpenAppConfig().permission == ToolPermission.ASK`.
+- `test_clipboard_read_empty`: mock `_read_clipboard` to return `""`; assert result is `ClipboardResult(action="read", text="")`.
+- `test_open_app_linux_no_opener`: mock platform as `"linux"`, mock all subprocess calls to raise `FileNotFoundError`; assert `ToolError` with message naming `xdg-open`.
+- `test_ocaya_md_contains_required_sections`: read `ocaya.md`; assert presence of keywords for each of the 7 required sections.
+- `test_pyproject_no_legacy_branding`: parse `pyproject.toml`; assert name, description, keywords, scripts contain no `"mistral-vibe"`, `"Mistral Vibe"`, or `"vibe"` (as a standalone word in user-facing fields).
+- `test_no_browser_automation_deps`: parse `pyproject.toml` dependencies; assert none match `playwright|browser-use|selenium|puppeteer|pyppeteer`.
+
+### Property-Based Tests
+
+Use `hypothesis` (already a transitive dev dependency via `pytest`). Each test runs minimum 100 examples.
+
+**Property 1: OCAYA_HOME path resolution**
+```python
+# Feature: ocaya, Property 1: OCAYA_HOME path resolution
+@given(st.text(min_size=1).filter(lambda s: s.strip()))
+@settings(max_examples=100)
+def test_ocaya_home_resolution(tmp_path, path_str):
+    resolved = Path(path_str).expanduser().resolve()
+    with mock.patch.dict(os.environ, {"OCAYA_HOME": path_str}):
+        assert _get_ocaya_home() == resolved
+```
+
+**Property 2: Version string prefix**
+```python
+# Feature: ocaya, Property 2: Version string prefix
+@given(st.from_regex(r"[0-9]+\.[0-9]+\.[0-9]+(\.[a-z0-9]+)?", fullmatch=True))
+@settings(max_examples=100)
+def test_version_string_prefix(version_str):
+    result = format_version_string(version_str)
+    assert result.startswith("OCAYA ")
+    assert version_str in result
+```
+
+**Property 3: OpenApp rejects all blank targets**
+```python
+# Feature: ocaya, Property 3: OpenApp rejects all blank targets
+@given(st.text(alphabet=st.characters(whitelist_categories=("Zs", "Cc"))))
+@settings(max_examples=100)
+async def test_open_app_blank_target_raises(whitespace_str):
+    tool = OpenApp.from_config(lambda: OpenAppConfig())
+    args = OpenAppArgs(target=whitespace_str)
+    with pytest.raises(ToolError, match="target cannot be empty"):
+        async for _ in tool.run(args):
+            pass
+```
+
+### Integration Tests
+
+- Verify `ToolManager` discovers `clipboard` and `open_app` in `available_tools` after rename (real filesystem, no mocks).
+- Verify the ACP server starts and returns a valid `initialized` response via `ocaya-acp`.
+- Verify all built-in agent profiles load without error from `OcayaConfig` and produce correct tool permission sets.
+- Verify session resume (`--resume`) works with sessions stored under `~/.ocaya`.
+
+### Snapshot Tests
+
+Existing `pytest-textual-snapshot` tests for TUI components are updated: expected snapshots are regenerated after branding changes to capture the new "OCAYA" labels.