feat(protected-content): one authority, the Runtime, and no 10% disk floor (ELACITY-2299)

AGENTS.md

@@ -183,9 +183,6 @@ them creates a cleanup obligation; "temporary" is not a lifecycle.
   condition, and must be removed when that gate closes. Do not recursively copy
   a live data root without an explicit size estimate and exclusion list for
   existing backups, VM images, caches, identity state, and user data.
-- Maintain at least 10% free space on development and staging volumes. If free
-  space falls below that threshold, stop creating worktrees, builds, VM images,
-  and backups until the ledger is reconciled and safe reclaim has completed.
 - Before handoff, rerun the branch/worktree inventory, check every touched
   worktree for dirt, report local/remote divergence, and update the local
   ledger. Do not describe a cleanup as complete while an unexplained ref,

TASKS.md

@@ -12,7 +12,7 @@ Model work in J3, MA, AI, CR and SEC1 is the implementation priority. Codex owns
 
 ## Now
 
-Each row requires a receipt with source/tree, dirty patch, built and installed hashes, target identity, operation, result and next proof. Ports are observations, not installation IDs. Preserve human Homes, keys, pins, data and the 10% disk floor. Publication and public mutation require separate exact-candidate approval.
+Each row requires a receipt with source/tree, dirty patch, built and installed hashes, target identity, operation, result and next proof. Ports are observations, not installation IDs. Preserve human Homes, keys, pins and data. Publication and public mutation require separate exact-candidate approval.
 
 | Order | Open gate and owner | Next proof and stop condition |
 | --- | --- | --- |
@@ -49,7 +49,7 @@ The [Browser acceptance contract](docs/BROWSER_ACCEPTANCE.md) defines B01–B16.
 
 ## Open verification controls
 
-The checks below stay open with their owning journey. They are not additional product scope. Use `scripts/public-install-operator-smoke.sh`, `scripts/public-install-identity-smoke.sh`, `scripts/audit-linux-runtime-portability.sh` and the provisional `scripts/protected-content-provider-contract-smoke.sh` at their applicable installed/release boundaries. Keep source/local Carrier setup proof green with `scripts/local-carrier-setup-smoke.sh`; publish the approved version's binary/artifact set so no-override public installed-path smokes use current code.
+The checks below stay open with their owning journey. They are not additional product scope. Use `scripts/public-install-operator-smoke.sh`, `scripts/public-install-identity-smoke.sh` and `scripts/audit-linux-runtime-portability.sh` at their applicable installed/release boundaries. Keep source/local Carrier setup proof green with `scripts/local-carrier-setup-smoke.sh`; publish the approved version's binary/artifact set so no-override public installed-path smokes use current code.
 
 For J4, retain `scripts/browser-native-supervisor-smoke.sh`, `scripts/browser-native-proxy-engine-smoke.sh`, `scripts/browser-native-supervisor-proxy-smoke.sh`, `scripts/browser-native-operator-config.mjs`, `scripts/browser-native-target-preflight.sh` and `scripts/wallet-connector-transaction-smoke.mjs` for their target proofs. Use artifact-aware `scripts/browser-provider-runbook.mjs --hosted-bakeoff/--native-preflight --manual-ux` and `scripts/browser-provider-runbook-smoke.sh`; `scripts/browser-objective-audit.mjs` remains the completion gate. Freeze new Browser provider implementation until the current blockers are cleared. The deferred provider comparison and current-host stop condition remain in [future work](docs/DEFERRED_WORK.md).
 

capsules/custody-provider/src/main.rs

@@ -1,8 +1,8 @@
 //! ElastOS protected-content custody node provider capsule.
 //!
-//! This source-only provider may be registered by Runtime as the inactive
-//! `custody` route. It does not replace the still-active provisional
-//! key-provider product path.
+//! Runtime registers this provider on the Runtime-only `custody` target. It is
+//! the only key-custody authority: each node evaluates rights locally and
+//! releases one recipient-encrypted contribution per authenticated operation.
 
 use std::env;
 use std::io::{self, BufRead, Write};