<?php
/**
 * Constants shared by the plugin bootstrap and by uninstall.php.
 *
 * WordPress runs uninstall.php on its own — it includes that file directly and never loads
 * mybot.php. A constant that exists only in the bootstrap is therefore undefined while the
 * plugin is being deleted, which is a fatal error on PHP 8 and stops the deletion entirely.
 * Both entry points load this file, so every name has exactly one definition.
 *
 * Keep this file free of WordPress API calls: it must load in the stripped-down context that
 * uninstall.php runs in.
 *
 * @package AI House
 */

defined( 'ABSPATH' ) || exit;

// ===== Version =====

/** Plugin version. Read by tools/build-i18n.mjs for the translation headers. */
define( 'MYBOT_VERSION', '1.22.0' );

/**
 * Database schema version. Bump it when the tables change.
 *
 * 1.3.0 added `attachments` to `mybot_messages` (1.14.0); **1.4.0 adds the `mybot_contacts` table**
 * (1.17.0). The bump is not bookkeeping: `maybe_upgrade()` returns early while this value matches the
 * stored option, so a site that already had the tables would keep the OLD schema — and since 1.14.0 the
 * logger writes fourteen columns, so on such a site **every log INSERT fails**, not just the new feature's.
 * A table or column that exists only on a fresh install is a feature that works in testing and nowhere
 * else (docs/08 muc 6.53).
 */
define( 'MYBOT_DB_VERSION', '1.4.0' );

// ===== Names in the WordPress API =====

/** REST namespace, matching the scheme: /wp-json/mybot/v1/... */
define( 'MYBOT_REST_NAMESPACE', 'mybot/v1' );

/** Option key holding every setting (a single array, autoload = yes). */
define( 'MYBOT_OPTION_KEY', 'mybot_settings' );

/**
 * Admin page slug of the screen that manages questions left for a human.
 *
 * A constant rather than a class constant because two layers need the same name: the admin class
 * registers the screen, and MYBOT_Requests::where() links to it from the Status card. Two copies
 * of a slug is one copy that stops matching, and a link to a page that does not exist looks exactly
 * like a link that works until somebody clicks it.
 */
define( 'MYBOT_REQUESTS_SLUG', 'mybot-requests' );

/**
 * Admin page slug of the screen that lists the visitors who left their details (1.17.0).
 *
 * A constant for the same reason as the one above, and it is not a formality: this screen links to itself
 * after a delete and prints a download link, and both of those are strings in two files.
 */
define( 'MYBOT_CONTACTS_SLUG', 'mybot-contacts' );

/*
 * There is no add-ons slug any more (1.11.0).
 *
 * `MYBOT_ADDONS_SLUG` named a top-level screen, "AI House → Add-ons". That screen became a section of
 * Settings — section `addons`, reachable at `admin.php?page=mybot&view=settings#tab-addons` — so the
 * slug has no screen to point at. The constant was removed rather than left behind: a name that
 * promises a screen is exactly the drift this project keeps paying for (`docs/08` muc 6.31), and it
 * had one caller, the menu code, which is gone with it. (An earlier release also recorded the cost of
 * a slug that existed in two places and only one of them was written — muc 6.50.)
 */

/** Table prefix; prepend $wpdb->prefix when using it. */
define( 'MYBOT_TABLE_SUFFIX', 'mybot_' );

/** Option recording the database schema version. */
define( 'MYBOT_DB_VERSION_OPTION', 'mybot_db_version' );

/** Option recording which plugin version last upgraded the content defaults. */
define( 'MYBOT_CONTENT_DEFAULTS_OPTION', 'mybot_content_defaults_version' );

/** Option holding the knowledge indexing progress. */
define( 'MYBOT_INDEX_STATE_OPTION', 'mybot_index_state' );

/** Option holding the last reason a fallback reply was served, shown on the dashboard. */
define( 'MYBOT_DEGRADED_OPTION', 'mybot_last_degraded' );

/**
 * Option holding what the knowledge base did on the last answered question, shown on the
 * dashboard and on the settings screen next to the RAG controls.
 */
define( 'MYBOT_RAG_TRACE_OPTION', 'mybot_last_rag' );

/**
 * Option holding what happened to the last "question for a human" submission.
 *
 * The widget tells the visitor when a send fails, but the administrator never learned about it —
 * so "I filled the form and nothing appeared in the plugin" had no answer anywhere in WordPress.
 * This option is that answer: when the last request was saved, and why the last attempt failed.
 */
define( 'MYBOT_SUPPORT_TRACE_OPTION', 'mybot_support_trace' );

/** Transient holding indexing progress for the admin screen. */
define( 'MYBOT_INDEX_PROGRESS_TRANSIENT', 'mybot_index_progress' );

/** Transient holding the OpenRouter credit budget. */
define( 'MYBOT_BUDGET_TRANSIENT', 'mybot_openrouter_budget' );

/**
 * Transient prefix for the cached model lists.
 *
 * The provider ID and the filter are appended, so every provider caches its own catalogue:
 * mybot_models_openrouter_free, mybot_models_openai_all, mybot_models_gemini_all.
 */
define( 'MYBOT_MODELS_TRANSIENT', 'mybot_models_' );

/** Post meta key holding the indexing fingerprint of a post. */
define( 'MYBOT_INDEX_HASH_META', '_mybot_index_hash' );

/*
 * Add-on API version — the contract an add-on is written against, and NOT the plugin version.
 *
 * An add-on declares `requires_core` in plugin versions, because that is what its author can check. This
 * constant exists for the other direction: when the shape of the registry or of a seam changes, the number
 * here changes, and an add-on can refuse to boot instead of half-working. Bumping it is a promise that
 * something an add-on relies on has changed meaning, so it is a decision rather than a side effect of a
 * release.
 *
 * It starts at 1.0 because until this release nothing was ever promised to an add-on.
 */
define( 'MYBOT_ADDON_API', '1.0' );