SKU 3 custom agent

Custom prompts are ops-led until a later CMS. Do not build a per-customer prompt manager for this slice. FAC /admin/aimee/prompt remains the Aimee (FAC) editor.

Recipe

  1. Copy src/aimee/chat/agents/aimee-partner.json to a new file, e.g. acme-coder.json, and set a unique slug.
  2. Keep FindACode links on unless the contract says otherwise. Do not enable gated AMA / JAMA / vendor tools for external actors.
  3. Optional: point prompt_base_file / prompt_manifest_file at a private prompt directory. Or set prompt_profile_slug if you overlay a published DB profile.
  4. If using DB prompts: import/publish that profile (php ops/import_prompt_mirror.php for the agent you created), then restart is still required for JSON slug discovery.
  5. Add the slug to [chatbot] ENABLED_AGENTS on workers and the API host.
  6. Bind the customer’s ai_api_clients.allowed_agent_slugs to the new slug (FAC API-clients admin or php ops/provision_api_client.php --slug=… --agent=…).
  7. Restart workers: /srv/aimee/ops/restart-aimee-service-workers.sh.

Do not add SKU 3 slugs to prompt_block_sync.json (that file is Aimee vs HccCoder only).