docs: delete unmaintained docs

docs/examples/plugin-component-tool/lib.rs

@@ -1,38 +0,0 @@
-//! Minimal Component Model Tool plugin authoring sketch using `yoi-plugin-pdk`.
-//!
-//! Build this as a `wasm32-unknown-unknown` cdylib with Component Model tooling
-//! and package the adapted component as `plugin.component.wasm`.
-
-use serde::{Deserialize, Serialize};
-use yoi_plugin_pdk::wit_bindgen;
-use yoi_plugin_pdk::{ToolContext, ToolError, ToolOutput};
-
-wit_bindgen::generate!({
-    world: "tool",
-    path: "../../../resources/plugin/wit",
-    generate_all,
-    runtime_path: "yoi_plugin_pdk::wit_bindgen::rt",
-});
-
-#[derive(Debug, Deserialize)]
-struct EchoInput {
-    text: String,
-}
-
-#[derive(Debug, Serialize)]
-struct EchoOutput<'a> {
-    tool: &'a str,
-    text: String,
-}
-
-fn handle_echo(ctx: ToolContext, input: EchoInput) -> Result<ToolOutput, ToolError> {
-    ToolOutput::json(
-        format!("{} ok", ctx.tool_name()),
-        EchoOutput {
-            tool: ctx.tool_name(),
-            text: input.text,
-        },
-    )
-}
-
-yoi_plugin_pdk::export_component_tool!(Plugin, handle_echo);

docs/release-notes/repository-local-yoi-removal.md

@@ -1,14 +0,0 @@
-# Repository-local `.yoi` authority removal
-
-This release removes the remaining production readers, writers, discovery helpers, fallbacks, and import paths that treated a repository-local `.yoi` tree as product authority.
-
-Removed surfaces include:
-
-- Ticket filesystem config loading, `LocalTicketBackend`, and local-to-SQLite import helpers;
-- Worker Ticket feature constructors backed by local paths;
-- Memory repository layout/discovery, local resident/query/staging/audit/usage executors, and `yoi memory lint`;
-- the Runtime helper that derived its store from `<workspace>/.yoi/runtime-store`.
-
-Workspace identity, metadata, Ticket, Objective, Memory, and launch configuration remain owned by the Workspace Server control-plane database and typed Workspace APIs. Client routing remains in XDG client configuration. Runtime-owned Workdirs, session logs, artifacts, Server data directories, repository/Git files, explicit Plugin package files, and the legacy home-directory secret-store boundary are unchanged.
-
-There is no automatic migration or compatibility fallback. Before upgrading from a version that stored active Ticket or Memory data in a repository `.yoi` tree, explicitly export data with the old version and import it through a supported Workspace-backed surface. Stale or malformed repository/ancestor `.yoi` trees are ignored by normal operation and may be archived or removed after verification.