chore(public): retire historical docs, estate references and compat framing

.github/workflows/ci.yml

@@ -600,7 +600,7 @@ jobs:
       # repo/environment variable `VOGT_ANDROID_SERVER_URL` and only falls back
       # to loopback when that is unset. Unset, the artifact stays a build-proof
       # that points at nothing (installing it shows the offline page). Set the
-      # variable to a real front door — e.g. `https://vogt-dev.sprooty.com` —
+      # variable to a real front door — e.g. `https://vogt.example.com` —
       # and the same job publishes an APK that is actually installable and
       # loads that Vogt. It stays debug-signed (below), so it is a sideload
       # channel, not a store/release artifact; a signed release APK is still a

AI_POLICY.md

@@ -0,0 +1,51 @@
+# AI policy
+
+This stack was written by AI agents, for AI-forward developers.
+
+That sentence is a statement of fact, not a disclaimer. Vogt's code,
+documentation, and tests were produced by AI coding agents working under the
+direction and review of the human maintainer, who is accountable for every
+line the repository ships. It is also a statement of intent: Vogt exists to
+run product work that people and agents do together, so agent surfaces —
+MCP, the operation registry, `docs/AGENT_GUIDE.md`, terminal sessions an
+agent can drive — are first-class product, not integrations bolted onto a
+human tool.
+
+## What that means for using Vogt
+
+- The documentation is written to be read by people and agents alike.
+  `AGENTS.md` is the repository's working contract for agents;
+  `docs/AGENT_GUIDE.md` is the guide for agents running work *through* a
+  deployed Vogt.
+- Transport parity is a design rule: anything the CLI or REST surface can
+  do, MCP can do, with tests asserting they agree. An agent is never a
+  second-class client.
+
+## What that means for contributing
+
+AI-assisted and AI-authored contributions are welcome and expected — most of
+this repository was built that way. The bar does not move either direction
+because an agent was involved:
+
+- **You are accountable for what you submit.** Run the checks in
+  `docs/CONTRIBUTING.md`, understand the change, and be able to answer
+  review questions about it. "The agent wrote it" is not an answer.
+- **Unreviewed agent output is not a contribution.** Bulk or speculative
+  pull requests, issues generated without reading the code, and changes
+  their author cannot explain will be closed without detailed review.
+- **The same quality rules apply.** Tests, transport parity, the audited
+  write path, and the documented layer order bind agents and people
+  equally.
+- **You must hold the rights to what you submit.** Contributions are
+  accepted under the repository's MIT licence; submitting output you are
+  not entitled to license is your responsibility, not the project's.
+
+Disclosure of AI involvement in a contribution is not required. It is the
+default assumption here.
+
+## What that means for maintenance
+
+Agents triage, review, and land work in this repository as a matter of
+routine. Decisions about scope, releases, and security remain with the human
+maintainer, and security reports go to the channel named in `SECURITY.md` —
+not to an automated surface.

CHANGELOG.md

@@ -5,7 +5,7 @@ All notable changes to Vogt are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
 once released — pre-1.0, a minor version bump may still carry a breaking
-change, per the compatibility policy in [`opensource.md`](opensource.md).
+change.
 
 This file starts from the public 0.2.0 baseline; earlier history lives in the
 git log rather than being reconstructed here.
@@ -56,7 +56,7 @@ migration is required.
 The first release since the merged core+engine stack reached production. No
 operation was renamed or removed; no schema migration is required (the declared
 schema stays at 0015, the observed schema at 0004). Pre-1.0, this remains a
-minor bump per the compatibility policy in [`opensource.md`](opensource.md).
+minor bump.
 
 ### Added
 

README.md

@@ -155,8 +155,7 @@ points: configuration, Compose overlays, image extension, running behind your
 own front door, and the optional integrations above. The Rust engine and
 Capacitor mobile shell (`engine/`, `web/`, `mobile/`) are the largest worked
 example of those extension points; the engine is the stack's front half, and
-the mobile shell wraps its PWA. See [`opensource.md`](opensource.md) for the
-public/private boundary and compatibility policy.
+the mobile shell wraps its PWA.
 
 ## Development
 
@@ -198,8 +197,8 @@ workflow and [`docs/CONFIG.md`](docs/CONFIG.md) for every setting.
   what it owns, how to build and run it, its wire contract, the assistant.
 - [Design outline](docs/DESIGN.md) — architecture and domain decisions.
 - [Contributing](docs/CONTRIBUTING.md) — workflow and checks.
-- [Public boundary and compatibility](opensource.md) — what is supported,
-  what is optional, which legacy names remain as aliases.
+- [AI policy](AI_POLICY.md) — how this stack is built: by AI agents, for
+  AI-forward developers, and what that means for contributions.
 
 ## Licence