diff --git a/CHANGELOG.md b/CHANGELOG.md
index 09fd2be6..ceb8b9a1 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,30 @@ The dashboard's **What's New** rail reads this file at request time
 entries. Keep entries terse — one line per item under each version
 date, grouped by `Added` / `Changed` / `Fixed` / `Removed`.
 
+## [2026-10-15] — v0.36.0 · Daily workflows and agent ownership
+
+### Added
+
+- Clearer issue/task capture, persistent drafts, and private reminders with snooze and dismissal.
+- Visible issue attachments and relationships, filtered activity, and an expandable automation menu with separate request and assignment actions.
+- Personal and service-owned agent identities, configurable personal-agent creation policy, and guarded runtime transfer/removal.
+
+### Changed
+
+- Home focuses on personal work; Mission Control focuses on operations. Agents, workspace access, account settings, and instance administration have distinct entry points.
+- Issue headers show the full key/title, due date, and reminder while app pins remain centered.
+- Runtime ownership and workspace access stay separate; existing owners are preserved and ownerless legacy runtimes become explicitly unassigned.
+
+### Fixed
+
+- Mobile issue controls remain scrollable above the floating activity dock.
+- Workspace experience changes update the form baseline and navigation together.
+- Windows local checks support npm-generated pnpm launchers and CRLF checkouts; browser CI includes real attachment storage.
+
+### Upgrade
+
+- The ownership migration requires a coordinated app/worker rollout. Stop old writers, verify a database backup, apply migrations explicitly, and start matching new app/worker images. Follow `RELEASE.md`; do not run an old binary against the new ownership constraints.
+
 ## [2026-09-01] — v0.35.0 · Actionable issue blockers
 
 ### Added
diff --git a/DEVLOG.md b/DEVLOG.md
index 407b6757..8e574598 100644
--- a/DEVLOG.md
+++ b/DEVLOG.md
@@ -2,6 +2,19 @@
 
 > Append-only session log. Read at session start. Update at session end.
 
+## 2026-10-15 — AXI-210 v0.36.0 release assembly
+
+- Assembled the operator-approved release from implementation PR #104,
+  squash-merged as 1363fe88f1dadb930050a1dd7169a798c50ec21d. Its final head
+  97c8d3dd83503aee74543c1d1dfd31b9d0f85d4c passed hosted lint/typecheck,
+  1,786 tests (one intentional skip), production builds and both browser shards.
+  Inspected the mobile automation capture and passing touch-assignment flow.
+- Bumped the package version and curated release notes for integrated AXI-203,
+  AXI-204 and AXI-206. AXI-191 remains separate. Documented the coordinated
+  ownership migration and explicit fail-closed migration command in RELEASE.md.
+- Release-head CI, immutable tag and production verification are recorded in
+  the release PR and Forge delivery history; publication alone is not deployment.
+
 ## 2026-10-15 — AXI-206 release preparation
 
 - Operator approved publication and deployment of the integrated AXI-203,
diff --git a/RELEASE.md b/RELEASE.md
index a7de4d1d..cee19c68 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -127,6 +127,22 @@ once Actions billing is restored.)
 
 ### 3. Deploy (Docker-Server)
 
+**v0.36.0 ownership upgrade:** build both new images before downtime, preserve
+the previous image identities, then stop `forge` and `forge-worker`. Create and
+verify a protected database backup before applying the ownership migration.
+Run the migration explicitly and require exit 0:
+
+```bash
+docker compose run --rm --no-deps --entrypoint prisma forge migrate deploy --schema=prisma/schema.prisma
+```
+
+Only then start the matching new app and worker with
+`docker compose up -d --no-deps forge forge-worker`. Do not rely on an entrypoint
+that logs migration failures and continues. If migration fails, keep old
+writers stopped and inspect the result; restarting an old image against the
+new ownership constraints is not a safe rollback. This coordinated procedure
+replaces the ordinary uninterrupted `up -d` step below for this upgrade.
+
 Prod builds an exact tag/commit from a dedicated clean checkout, stamped with
 the commit. The deployment lock permits one release at a time:
 
diff --git a/docs/guide/issues.md b/docs/guide/issues.md
index 06bcff66..cd754967 100644
--- a/docs/guide/issues.md
+++ b/docs/guide/issues.md
@@ -18,7 +18,7 @@ An assigned agent remains a separate control from human assignment.
   blocks, duplicates and related issues, including linked titles and statuses.
   Expand a group or the dependency map without replacing the list.
 - **Automation & delivery** is always discoverable. Add agent or delivery opens
-  Ask an agent, Link implementation PR, and Start delivery session. Existing
+  Ask an agent, Assign an agent, Link implementation PR, and Start delivery session. Existing
   agent outcomes, delivery ownership/stage, PR relations and warnings remain
   visible; only supporting evidence expands. Mobile header links jump directly
   to related work and automation.
diff --git a/package.json b/package.json
index d3e632b0..9d48bc88 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "forge",
-  "version": "0.35.0",
+  "version": "0.36.0",
   "private": true,
   "description": "Forge — a fast, minimalist, keyboard-driven project management platform with pluggable agents.",
   "license": "MIT",