[aroff]

Summary

Removes the ailoop integration and its mandatory ailoop-core git dependency.
The upstream goailoop/ailoop repository is no longer publicly fetchable, so
any build that resolves cli-framework failed to fetch ailoop-core
anonymously, even for consumers that never used it.

• Drop ailoop-core from Cargo.toml and delete src/ailoop.
• Remove every reference: lib.rs, AppBuilder / App (with_ailoop_channel,
  with_ailoop_config, ailoop_client), DispatchEnv, the chat command and
  runtime, McpHostToolAdapter, and ConfirmationMode::Ailoop in the tool bridge.
• RiskEnforcer::enforce_preflight loses its ailoop_available parameter.
  Sensitive proceeds when the terminal is interactive or --yes is given;
  Destructive needs ALLOW_DESTRUCTIVE_COMMANDS=1 and an interactive
  terminal. PrefightError docs and the DestructiveNeedsInteractive message
  no longer mention ailoop.
• Delete the with_ailoop example and the ailoop_websocket integration test
  (and their [[example]] / [[test]] entries).
• Docs: README, CONTEXT, CONTRIBUTING, AGENTS, and the skill
  (plugins-and-ailoop.md becomes plugins.md; skill version 0.4.0 → 0.5.0).
  ADRs are left as historical records.
• .cargo/audit.toml: drop the RUSTSEC-2026-0098/0099/0104 ignores. They
  existed only for the rustls-webpki 0.101 that ailoop-core pulled in
  through reqwest 0.11 (chore: bump aikit-sdk and ailoop-core to latest (fix legacy ailoop Question wire format) #51). After this change the lockfile resolves
  rustls-webpki 0.103.16 only.

Release notes

Breaking: the AppBuilder ailoop API is removed (with_ailoop_channel,
with_ailoop_config, App::ailoop_client, the cli_framework::ailoop
module, ChatToolCallOptions::ailoop_client, ConfirmationMode::Ailoop), and
RiskEnforcer::enforce_preflight takes three arguments instead of four. See
CHANGELOG [Unreleased].

Test plan

• cargo fmt --all -- --check
• cargo clippy --all-features -- -D warnings
• cargo test (default, chat, mcp-server, chat,mcp-server)
• cargo test --features telemetry,config,config-service,mcp-server,api-server,testkit,derive: all pass except two config_backend_file permission tests, which fail only because the local run was as root (permission bits are not enforced); that code is untouched here
• cargo build --examples
• cargo build --all-features --release: left to CI
• cargo tree -i ailoop-core --all-features finds nothing; Cargo.lock has no ailoop entry

Follow-up to #51: the advisory ignores it tracked are no longer needed.

---

Generated by Claude Code