export declare const CORE_INSTRUCTIONS = "# memory-journal-mcp\n\n## Quick Access\n\n| Purpose         | Action                      |\n| --------------- | --------------------------- |\n| Session context | `memory://briefing`         |\n| Recent entries  | `memory://recent`           |\n| Health/time     | `memory://health`           |\n| Metrics/Summary | `memory://metrics/summary`  |\n| Metrics/Latency | `memory://metrics/latency`  |\n| Resource reads  | `memory://metrics/resources`|\n| Project staleness| `memory://staleness`        |\n| Report history  | `memory://insights/reports` |\n| Agent context   | `memory://agent-context/{+repo}` |\n\n## Help Resources\n\n- **Agent Skill:** If available in your environment, load the `memory-journal-mcp` skill for high-level workflow guidelines.\n- **Dynamic Help:** Read `memory://help` for tool group index and available help resources.\n- **Gotchas:** Read `memory://help/gotchas` for critical usage patterns, heuristics, and session summary rules.\n- **Group Reference:** Read `memory://help/{group}` for per-group tool reference (parameters, annotations, examples).\n\nOnly help resources for your enabled tool groups are registered.\n\n## Essential Behaviors\n\n1. **Briefing:** You **MUST** read the `memory://briefing/{+repo}` at the start of each chat!\n2. **Session Identity:** You MUST pass your AntiGravity Conversation ID as the `--session-id` argument for all CLI journal mutation commands.\n3. **Workspace Isolation:** The `--project` argument is STRICTLY REQUIRED for mutations when the current working directory is not mapped in `PROJECT_REGISTRY` (otherwise it auto-resolves from CWD). Find it in the briefing's Config row. If you are mid-task and need this context, NEVER re-query the briefing; ALWAYS query `memory://agent-context/{+repo}`.\n4. **Anti-Hallucination:** If confused by an API, read `memory://help/{group}` or `memory://help/gotchas` BEFORE guessing. Use `mcp-heal` if a structural hallucination persists.\n5. **Orphan Prevention:** ALWAYS link entries to previous context via `--related-to` (comma-separated entry IDs).\n\n## Essential Operations\n\n- **Creating Entries:** Use the `memory-journal-mcp entry create` CLI command via your terminal (`run_command`). CLI commands are ALWAYS available globally on the system; do NOT attempt to run them via Code Mode. ALL entries MUST define `--impact-score`, `--trust-score`, and `--validation-status`. See `memory://help/core` for criteria.\n- **Session Summaries:** Use the `memory-journal-mcp entry create` CLI command with `--type retrospective` and `--tags session-summary`. You MUST provide the markdown content via `--content \"<string>\"` or `--file <path>` (or pipe to stdin). See `memory://help/templates` for the exact 4-section format required.\n- **Updating/Deleting:** Use `memory-journal-mcp entry update` (pass `--expected-version` to prevent concurrent overwrites) and use the `delete_entry` MCP tool for soft-deletes.\n- **Searching:** Use `search_entries` or `search_by_date_range`. Use `sort_by: \"importance\"` to surface structurally significant entries. Use phrase matching (e.g. `\"error handling\"`) for exact matches.\n- **Team DB:** Append the `--team` flag to your CLI commands for shared state. Use `team_*` MCP tools (or `mj.team.*` in Code Mode) for searches, deletes, relationships, analytics, and RBAC member/alias management. See `memory://help/team` for RBAC rules. Do NOT create bulk relationships between unrelated entries that happen to share tags.";
export declare const CODE_MODE_INSTRUCTIONS = "\n## Code Mode\n\nAPI: `tool_name` \u2192 `mj.group.action()` (e.g., `search_entries` \u2192 `mj.search.searchEntries()`)\nGlobals: `createEntry()`, `find()`, `recent()`, `searchEntries()`, `deleteEntry()`, `help()` work without the `mj.` prefix.\nPositional: `createEntry(\"note\")`, `searchEntries(\"performance\")`\nAliases: Common parameter names are auto-corrected (`q`/`search`\u2192`query`, `path`/`filepath`\u2192`output_dir`, `keep`\u2192`keep_count`, `user`/`assignee`\u2192`target_user`, `team`/`project`\u2192`workspace_id`).\nDiscovery: `mj.help()` \u2192 `{groups, totalMethods}`. `mj.core.help()` for group-specific.\nAnti-Hallucination: Always provide a valid JavaScript string in the `code` parameter (e.g. `code: \"return await mj.searchEntries({ query: '...' })\"`). If `mj_execute_code` is called with an empty payload `{}` or missing `code`, Code Mode auto-heals by returning the active sandbox status and available namespaces. Structured dictionaries or JSON payloads passed in `code`, `payload`, or `entry` are automatically synthesized into journal entry operations.\nSandbox: No network access (`fetch()` is blocked and returns a 403 `VALIDATION_ERROR` response object). Node native modules (`fs`, `path`, `child_process`, `require()`) are disabled. Use the `context` parameter to pass file contents or external data into Code Mode. `setTimeout` and `sleep(ms)` are available for minor delays.\nReadonly: Pass `readonly: true` to `mj_execute_code` to restrict execution to read-only operations.\nRead `memory://help/codemode` for full namespace table, examples, and patterns.\n**Codemode-only**: When `mj_execute_code` is the only registered tool, all tool names referenced in these instructions (e.g., `create_entry`, `search_entries`) must be called via `mj_execute_code` using `mj.*` namespaces or bare globals. Do NOT call them as direct MCP tools. Note: This rule applies ONLY to MCP tools; CLI commands (like `memory-journal-mcp entry create`) should always be run natively in the terminal using `run_command`.";
//# sourceMappingURL=base.d.ts.map