export declare const GSLOTH_DIR = ".gsloth";
export declare const GSLOTH_SETTINGS_DIR = ".gsloth-settings";
export declare const GSLOTH_AUTH = ".gsloth-auth";
export declare const USER_PROJECT_CONFIG_JS = ".gsloth.config.js";
export declare const USER_PROJECT_CONFIG_JSON = ".gsloth.config.json";
/**
 * GS2-69 — the `.jsonc` filename variant. Both JSON names are parsed by the same lenient
 * {@link @gaunt-sloth/core!config/jsonc.parseJsonc | parseJsonc}; this one just carries the conventional
 * extension so editors/review tools expect the comments. `.json` wins when both exist.
 */
export declare const USER_PROJECT_CONFIG_JSONC = ".gsloth.config.jsonc";
export declare const USER_PROJECT_CONFIG_MJS = ".gsloth.config.mjs";
export declare const USER_PROJECT_CONFIG_TS = ".gsloth.config.ts";
export declare const GSLOTH_BACKSTORY = ".gsloth.backstory.md";
export declare const PROJECT_GUIDELINES = ".gsloth.guidelines.md";
export declare const PROJECT_REVIEW_INSTRUCTIONS = ".gsloth.review.md";
export declare const GSLOTH_SYSTEM_PROMPT = ".gsloth.system.md";
export declare const GSLOTH_CHAT_PROMPT = ".gsloth.chat.md";
export declare const GSLOTH_CODE_PROMPT = ".gsloth.code.md";
export declare const GSLOTH_EXEC_PROMPT = ".gsloth.exec.md";
export declare const AIIGNORE_FILE = ".aiignore";
/**
 * `$schema` pointer written into a generated `.gsloth.config.json` (GS2-1) so editors offer
 * autocomplete + validation. The **hosted, major-pinned** URL is used rather than a relative
 * `node_modules` path because the relative path only resolves when `@gaunt-sloth/core` sits in a
 * `node_modules` beside the config, which is NOT the case for a globally-installed CLI
 * (`npm i -g`): the schema lands in the global prefix, not next to the user's project config, so
 * a relative pointer would silently fail to resolve. A hosted URL resolves for every install mode
 * (global, npx, local, or a hand-written config with nothing installed) and is the standard
 * convention editors fetch + cache.
 *
 * The channel is **major-pinned** (`/schema/v2/…`, not `latest` or `alpha`) so a config never
 * revalidates against a future major it was not written for. The hosted copy is kept in sync with
 * this package's generated schema by the deploy runbook in
 * `websites/gauntsloth-site/schema/README.md` (interim, hand-run) and, in time, PLAT-9's automated
 * release step. The schema still ships inside the package (`files: ["./schema/*"]`) as an offline
 * artifact and golden-snapshot source of truth; it is just no longer what the pointer references.
 */
export declare const CONFIG_SCHEMA_POINTER = "https://gauntsloth.app/schema/v2/gsloth-config.schema.json";
/**
 * EXT-9 Tier-2: project-scoped persisted shell allow-list (`always` approvals).
 * Lives under `.gsloth/.gsloth-settings/` like other project settings.
 */
export declare const SHELL_ALLOWLIST_FILE = "shell-allowlist.json";
/**
 * [[EXT-107]]: project-scoped persisted shell deny-list — the escalation menu's *always reject*
 * choice. Its mirror on the refusal side, in the same directory and the same EXT-71 entry grammar,
 * so the two files read identically to anyone who opens them.
 *
 * A separate file rather than a second array in {@link SHELL_ALLOWLIST_FILE}: the two lists have
 * opposite failure modes, and a parse error that took the refusals down with the approvals would
 * fail in the one direction this design never lets anything fail in.
 */
export declare const SHELL_DENYLIST_FILE = "shell-denylist.json";
/**
 * The `additionalToolNamePrefix` handed to `MultiServerMCPClient` so every MCP tool name is
 * namespaced. Combined with `prefixToolNameWithServerName`, the adapter emits tool names shaped
 * `${MCP_TOOL_NAME_PREFIX}__<serverName>__<toolName>` (the `__` separator is the mcp-adapters
 * convention). Single-sourced here so the resolver that sets the prefix (EXT-32) and any consumer
 * that groups tools back by server (the [[TUI-C20]] MCP debug tab) can never silently drift apart.
 */
export declare const MCP_TOOL_NAME_PREFIX = "mcp";
/**
 * GS2-35 — the canonical Git co-author identity for agent-authored commits. When Gaunt Sloth writes
 * a commit (via `run_shell_command` `git commit`) the co-author is *Gaunt Sloth itself*, NOT the
 * underlying model: the commit was produced by the assistant, so attributing it to the model that
 * served the session is factually wrong. The email is what makes the trailer resolve to the real
 * Gaunt Sloth account, so it is the half that must not move. This name is the BASE the composed
 * trailer is built from, not the whole emitted value: the resolved active model decorates it as
 * `Gaunt Sloth (provider:model)` (EXT-83). Config (`commit.coAuthor`) overrides
 * this; single-sourced so the config default and the prompt-guidance fallback
 * ({@link @gaunt-sloth/core!utils/systemPromptNotes.appendCommitCoAuthorNote | appendCommitCoAuthorNote}) can never drift.
 */
export declare const DEFAULT_COMMIT_CO_AUTHOR_NAME = "Gaunt Sloth";
export declare const DEFAULT_COMMIT_CO_AUTHOR_EMAIL = "code@gauntsloth.app";