plugin-scanner 3.0.0a212__tar.gz → 3.0.0a214__tar.gz

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: plugin-scanner
-Version: 3.0.0a212
+Version: 3.0.0a214
 Summary: Lint, verify, and gate plugin ecosystems for maintainers, CI, and publish workflows.
 Project-URL: Homepage, https://hol.org/guard
 Project-URL: Security, https://hol.org/guard/security

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/ci/code-quality-baseline.json

@@ -43,7 +43,7 @@
     "src/codex_plugin_scanner/guard/consumer/service.py::evaluate_detection": 132,
     "src/codex_plugin_scanner/guard/daemon/hook_process_runner.py::HookProcessRunner.review": 45,
     "src/codex_plugin_scanner/guard/daemon/manager.py::_guard_daemon_process_inventory_for_guard_home": 31,
-    "src/codex_plugin_scanner/guard/daemon/manager.py::ensure_guard_daemon": 34,
+    "src/codex_plugin_scanner/guard/daemon/manager.py::ensure_guard_daemon": 35,
     "src/codex_plugin_scanner/guard/daemon/manager.py::retire_all_guard_daemons_for_home": 38,
     "src/codex_plugin_scanner/guard/daemon/server.py::GuardDaemonServer._finish_service_locked": 32,
     "src/codex_plugin_scanner/guard/daemon/server.py::_GuardDaemonHandler._handle_headless_remote_once": 31,
@@ -252,7 +252,7 @@
     "src/codex_plugin_scanner/guard/consumer/service.py::evaluate_detection": 743,
     "src/codex_plugin_scanner/guard/daemon/extension_control_semantic_preview.py::build_extension_control_semantic_preview": 152,
     "src/codex_plugin_scanner/guard/daemon/hook_process_runner.py::HookProcessRunner.review": 171,
-    "src/codex_plugin_scanner/guard/daemon/manager.py::ensure_guard_daemon": 133,
+    "src/codex_plugin_scanner/guard/daemon/manager.py::ensure_guard_daemon": 135,
     "src/codex_plugin_scanner/guard/daemon/manager.py::retire_all_guard_daemons_for_home": 103,
     "src/codex_plugin_scanner/guard/daemon/server.py::_GuardDaemonHandler._handle_guard_cloud_connect_start": 172,
     "src/codex_plugin_scanner/guard/daemon/server.py::_GuardDaemonHandler._handle_headless_policy_sync": 133,
@@ -518,7 +518,7 @@
     "src/codex_plugin_scanner/guard/consumer/service.py": 1859,
     "src/codex_plugin_scanner/guard/daemon/dashboard_update.py": 663,
     "src/codex_plugin_scanner/guard/daemon/hook_process_runner.py": 707,
-    "src/codex_plugin_scanner/guard/daemon/manager.py": 2999,
+    "src/codex_plugin_scanner/guard/daemon/manager.py": 3071,
     "src/codex_plugin_scanner/guard/daemon/runtime_hook_scheduler.py": 527,
     "src/codex_plugin_scanner/guard/daemon/server.py": 8883,
     "src/codex_plugin_scanner/guard/inventory_contract.py": 1818,
@@ -613,7 +613,7 @@
     "tests/test_guard_approval_reuse.py": 1793,
     "tests/test_guard_approval_scope_contract.py": 998,
     "tests/test_guard_approval_store_scale.py": 737,
-    "tests/test_guard_approvals.py": 3921,
+    "tests/test_guard_approvals.py": 3968,
     "tests/test_guard_authoritative_decision.py": 1045,
     "tests/test_guard_auto_first_sync.py": 797,
     "tests/test_guard_browser_mcp_intent.py": 1065,
@@ -637,7 +637,7 @@
     "tests/test_guard_consumer_approval_precedence.py": 2762,
     "tests/test_guard_copilot_adapter.py": 970,
     "tests/test_guard_daemon_decision_boundary.py": 912,
-    "tests/test_guard_daemon_manager.py": 2952,
+    "tests/test_guard_daemon_manager.py": 3086,
     "tests/test_guard_dashboard_launcher.py": 516,
     "tests/test_guard_direct_vitest.py": 832,
     "tests/test_guard_events.py": 1279,
@@ -740,9 +740,9 @@
     "src/codex_plugin_scanner/guard/cli/commands_support_service.py::_handle_daemon_status::Exception::221",
     "src/codex_plugin_scanner/guard/daemon/diagnostics.py::DaemonDiagnostics.__init__::Exception::100",
     "src/codex_plugin_scanner/guard/daemon/diagnostics.py::DaemonDiagnostics._run::Exception::170",
-    "src/codex_plugin_scanner/guard/daemon/manager.py::_runtime_state_age_seconds::Exception::2053",
-    "src/codex_plugin_scanner/guard/daemon/manager.py::_schedule_duplicate_guard_daemon_retirement.retire::Exception::1141",
-    "src/codex_plugin_scanner/guard/daemon/manager.py::_schedule_stale_ephemeral_guard_daemon_reap.reap::Exception::1884",
+    "src/codex_plugin_scanner/guard/daemon/manager.py::_runtime_state_age_seconds::Exception::2073",
+    "src/codex_plugin_scanner/guard/daemon/manager.py::_schedule_duplicate_guard_daemon_retirement.retire::Exception::1161",
+    "src/codex_plugin_scanner/guard/daemon/manager.py::_schedule_stale_ephemeral_guard_daemon_reap.reap::Exception::1904",
     "src/codex_plugin_scanner/guard/daemon/server.py::_maybe_queue_first_cloud_sync::Exception::1349",
     "src/codex_plugin_scanner/guard/daemon/server.py::_maybe_queue_first_cloud_sync::Exception::1357",
     "src/codex_plugin_scanner/guard/desktop_notifications.py::_ensure_desktop_notification_setup_worker::Exception::290",

plugin_scanner-3.0.0a214/ci/test-suite-ratchet-baseline.json

@@ -0,0 +1,5 @@
+{
+  "maximum_collected_cases": 15239,
+  "maximum_test_source_lines": 328602,
+  "schema_version": 1
+}

plugin_scanner-3.0.0a214/contracts/managed-controls/v1/product-decision.json

@@ -0,0 +1,43 @@
+{
+  "authority_modes": [
+    "personal-shared",
+    "workspace-shared",
+    "managed-restrictive"
+  ],
+  "compatibility": {
+    "internal_policy_bundle_names_retained": true,
+    "policy_route_aliases_retained": true,
+    "technical_guard_policy_names_retained": true
+  },
+  "decision_id": "hol-guard.extension-first-managed-controls.v1",
+  "definitions": {
+    "control_set": "A versioned, scoped, simulated, reviewed, signed, deployed, acknowledged, and auditable collection of Extension controls and contextual rules in Guard Cloud.",
+    "deployment": "A signed Control Set version delivered to an eligible runtime cohort with acknowledgement, drift, pause, rollback, and audit state.",
+    "detector_rule": "A Local runtime implementation detail that recognizes security-relevant evidence for an Extension permission. Detector rules do not grant authority and are not authored by Cloud by default.",
+    "exception": "A time-bounded, reviewed contextual deviation. In release 3.0, an exception cannot weaken a managed-restrictive Extension or permission block.",
+    "extension": "A stable Local capability boundary for a protected tool or capability domain, such as Git, Docker, Kubernetes, GitHub, npm, or MCP.",
+    "local_setting": "A device-specific Extension or permission preference that can preserve or strengthen protection but cannot weaken a managed restriction or required floor.",
+    "managed_restriction": "A signed workspace restriction that can disable an Extension, disable a permission, or activate global lockdown and cannot be weakened locally.",
+    "permission": "A stable, independently configurable capability inside an Extension. Permissions own the detector rules needed to recognize that capability.",
+    "remembered_rule": "A contextual local decision remembered from an approval. It is not an Extension setting and cannot bypass a managed restriction or required floor."
+  },
+  "enforcement": {
+    "cloud_must_not_redefine_detector_matchers": true,
+    "contextual_policy_precedence_preserved": true,
+    "local_registry_authoritative": true,
+    "managed_restrictive_actions": [
+      "disable-extension",
+      "disable-permission",
+      "global-lockdown"
+    ],
+    "non_weakenable_authority_requires_negotiation": true,
+    "package_manager_delegate": "package-firewall"
+  },
+  "product_language": {
+    "cloud_primary_object": "Control Set",
+    "cloud_surface": "Managed controls",
+    "local_extension_surface": "Extensions",
+    "local_rule_surface": "Rules & exceptions"
+  },
+  "schema_version": 1
+}

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/dashboard/src/app.tsx

@@ -159,7 +159,7 @@ export function viewTitle(view: AppView): string {
   if (view === "settings") return "Settings";
   if (view === "supply-chain") return "Supply Chain";
   if (view === "audit") return "Audit";
-  if (view === "policy") return "Policy";
+  if (view === "policy") return "Rules & exceptions";
   if (view === "feed-health") return "Feed Health";
   if (view === "about") return "About";
   if (view === "extensions") return "Extensions";

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/dashboard/src/policy-cloud-exceptions-ia.test.tsx

@@ -32,9 +32,12 @@ assert(tabSource.includes("PolicyCloudExceptionDetailPanel"), "cloud exceptions
 assert(tabSource.includes("PolicyCloudExceptionsList"), "cloud exceptions tab renders grouped lists");
 assert(chromeSource.includes("Open Guard Cloud"), "policy header exposes Open Guard Cloud on exceptions tab");
 assert(tabSource.includes("Guard Cloud is not connected"), "disconnected Cloud copy present");
-assert(pageSource.includes("Configure protection behavior in Settings."), "page header explains configuration ownership");
+assert(
+  pageSource.includes("Configure tools and capability posture in Extensions."),
+  "page header explains configuration ownership",
+);
 assert(!workspaceSource.includes("bypass"), "policy workspace removes bypass copy");
 const sidebarSource = readFileSync(join(here, "approval-center-primitives.tsx"), "utf8");
-assert(sidebarSource.includes('label: "Policy"'), "sidebar Policy label unchanged");
+assert(sidebarSource.includes('label: "Policy"'), "legacy view label remains compatible");
 
 console.log("policy-cloud-exceptions-ia.test.ts: all assertions passed");

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/dashboard/src/policy-workspace-page.tsx

@@ -60,9 +60,9 @@ export function PolicyWorkspacePage(props: {
   return (
     <div className="space-y-6">
       <WorkspacePageHeader
-        eyebrow="Policy"
-        title="Remembered rules and exceptions"
-        description="Inspect remembered outcomes, cloud exceptions, and the order Guard uses to decide. Configure protection behavior in Settings."
+        eyebrow="Rules & exceptions"
+        title="Remembered decisions and exceptions"
+        description="Review decisions remembered on this device, contextual rules synced from Guard Cloud, exceptions, and the order Guard uses to decide. Configure tools and capability posture in Extensions."
         actions={
           activeView === "exceptions" ? (
             <PolicyExceptionsToolbar

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/dashboard/src/scrg171-172.test.ts

@@ -244,7 +244,7 @@ assert(
 assert(
   viewTitle("supply-chain") === "Supply Chain" &&
     viewTitle("audit") === "Audit" &&
-    viewTitle("policy") === "Policy" &&
+    viewTitle("policy") === "Rules & exceptions" &&
     viewTitle("feed-health") === "Feed Health",
   "SCRG171-H2: route titles stay specific inside Trust Center views",
 );

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/dashboard/src/shell-navigation-model.ts

@@ -97,9 +97,9 @@ export const SHELL_NAV_ITEMS: readonly ShellNavigationItem[] = [
   },
   {
     href: "/policy",
-    label: "Policy",
-    shortLabel: "Policy",
-    description: "Saved decisions and local controls",
+    label: "Rules & exceptions",
+    shortLabel: "Rules",
+    description: "Remembered decisions, Guard Cloud rules, and exceptions",
     view: "policy",
     group: "manage",
     icon: HiMiniClipboardDocumentList,
@@ -108,7 +108,7 @@ export const SHELL_NAV_ITEMS: readonly ShellNavigationItem[] = [
     href: "/extensions",
     label: "Extensions",
     shortLabel: "Extensions",
-    description: "Managed extensions and integrations",
+    description: "Tools and capabilities protected on this device",
     view: "extensions",
     group: "manage",
     icon: HiMiniPuzzlePiece,

plugin_scanner-3.0.0a214/docs/guard/adr/0011-extension-first-managed-controls.md

@@ -0,0 +1,102 @@
+# ADR 0011: Extension-First Managed Controls
+
+- Status: Accepted
+- Date: 2026-08-19
+- Decision ID: `hol-guard.extension-first-managed-controls.v1`
+- Canonical decision: `contracts/managed-controls/v1/product-decision.json`
+
+## Context
+
+HOL Guard 3.0 introduces Extensions and permissions as stable Local capability boundaries over detector rules. Guard Cloud already provides policy versioning, simulation, review, rollout, acknowledgement, rollback, exceptions, routing, and audit evidence. Presenting Extensions and Cloud policies as parallel configuration systems would duplicate concepts, increase cognitive load, and make authority unclear.
+
+The product must preserve complete Local protection while making Guard Cloud materially more valuable for cross-device and workspace governance. It must also preserve existing routes, technical `GuardPolicy` types, policy bundle wire contracts, and contextual policy precedence during the 3.0 release.
+
+## Decision
+
+### Product model
+
+Extensions define what HOL Guard can protect. Guard Cloud Control Sets define how that protection is governed across people, devices, agents, environments, and time.
+
+The shared definitions are:
+
+- **Extension:** a stable Local capability boundary for a protected tool or capability domain.
+- **Permission:** an independently configurable capability inside an Extension.
+- **Detector rule:** a Local implementation detail that recognizes evidence for a permission. It emits evidence, not authority.
+- **Local setting:** a device-specific Extension or permission preference.
+- **Remembered rule:** a contextual decision remembered from an approval.
+- **Control Set:** a versioned, scoped, simulated, reviewed, signed, deployed, acknowledged, and auditable collection of Extension controls and contextual rules in Guard Cloud.
+- **Managed restriction:** a signed workspace restriction that can disable an Extension, disable a permission, or activate global lockdown and cannot be weakened locally.
+- **Deployment:** delivery of a signed Control Set version to an eligible runtime cohort with acknowledgement, drift, pause, rollback, and audit state.
+- **Exception:** a time-bounded, reviewed contextual deviation. In release 3.0, an exception cannot weaken a managed restriction.
+
+### Authority boundaries
+
+1. The Local Extension registry is authoritative for detector facts, stable Extension IDs, stable permission IDs, dependencies, implied permissions, required floors, configurability, replacement metadata, and delegated protection.
+2. Guard Cloud targets Extension and permission identities. It does not recreate or replace Local detector matchers in the default authoring path.
+3. Current contextual policy precedence remains unchanged unless a separately negotiated contract explicitly says otherwise.
+4. Non-weakenable authority is represented by `managed-restrictive`, negotiated independently, signed, and limited in release 3.0 to Extension disable, permission disable, and global lockdown.
+5. Local settings and remembered decisions may tighten protection. They cannot weaken required floors or managed restrictions.
+6. Package-manager Extensions with `delegated_protection: package-firewall` are governed by the package firewall contracts rather than duplicated command-policy rules.
+7. Unsupported clients must not receive a fallback that silently drops Extension enforcement semantics.
+
+### Authority modes
+
+- `personal-shared`: shared posture for a user's authorized devices. Local tightening remains valid.
+- `workspace-shared`: shared workspace posture. Local tightening remains valid.
+- `managed-restrictive`: signed workspace floor that cannot be weakened locally.
+
+### Product language
+
+- Guard Cloud's customer-facing surface is **Managed controls**.
+- The primary Cloud object is a **Control Set**.
+- Local `/extensions` remains **Extensions** and describes tools and capabilities protected on this device.
+- Local `/policy` remains a compatibility route but is labeled **Rules & exceptions**.
+- Technical names such as `GuardPolicy`, policy bundle, policy document, policy version, and compatibility route names remain where they are protocol or implementation contracts.
+
+### Compatibility
+
+Existing `/policy`, `/guard/policy`, policy APIs, `GuardPolicy` types, canonical policy documents, and policy bundle names remain valid. New product labels do not require a breaking route or wire-format migration.
+
+### Shared contract and drift prevention
+
+Both repositories maintain byte-identical copies of:
+
+- `docs/guard/adr/0011-extension-first-managed-controls.md`
+- `docs/guard/managed-controls-glossary.md`
+- `contracts/managed-controls/v1/product-decision.json`
+
+HOL Guard tests validate the local shape and semantics. The Guard Cloud release workflow owns the cross-repository byte comparison against `hol-guard` `release/3.0`. The paired release is conformant only when that workflow is present and green after both paired pull requests land. Until then, cross-repository conformance is pending rather than assumed.
+
+## Consequences
+
+### Positive
+
+- Local protection remains complete and understandable without Cloud.
+- Cloud value moves to fleet governance, review, simulation, rollout, drift, exceptions, and evidence instead of duplicating detector authoring.
+- Users see one clear Extension posture surface and one contextual Rules & exceptions surface locally.
+- Paid plans can provide stronger governance without weakening the free product.
+- Existing policy routes and wire contracts remain compatible.
+
+### Costs
+
+- Runtime capability negotiation, catalog synchronization, compatibility evaluation, and atomic application must be implemented before managed restrictions are enabled.
+- Cloud must maintain a read model of Local catalogs without becoming the detector source of truth.
+- Product copy, accessibility labels, documentation, and analytics require coordinated migration.
+
+## Rejected alternatives
+
+### Replace policy with Extensions
+
+Rejected because contextual decisions, approvals, exceptions, routing, simulation, rollout, and audit are not Extension metadata.
+
+### Keep policy and Extensions as independent editors
+
+Rejected because it duplicates controls, obscures precedence, and asks administrators to recreate detector knowledge already owned by Local.
+
+### Paywall Local Extensions
+
+Rejected because Local safety is the protection floor. Cloud monetization must come from governance and coordination, not intentionally weaker local enforcement.
+
+### Give all Cloud rules absolute precedence
+
+Rejected for release 3.0 because it would silently change contextual policy semantics and could create security and compatibility regressions.

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/docs/guard/command-extension-architecture.md

@@ -56,6 +56,9 @@ All matches survive evaluation. The engine creates one composite artifact contai
 
 The artifact is evidence, not policy. Guard policy resolves configured risk actions, source/workspace scope, managed policy, remembered decisions, approvals, and final `allow`, `warn`, `review`, `sandbox-required`, `require-reapproval`, or `block` behavior. Extension metadata, modes, and safer alternatives cannot grant authority.
 
+The Extension-first authority boundary between Local detector facts, remembered decisions, and Guard Cloud Control Sets is defined by
+[`ADR 0011: Extension-First Managed Controls`](adr/0011-extension-first-managed-controls.md).
+
 Decision composition must be monotonic:
 
 1. Required critical rules establish a minimum action that lower-authority input cannot reduce.

{plugin_scanner-3.0.0a212 → plugin_scanner-3.0.0a214}/docs/guard/local-vs-cloud.md

@@ -1,42 +1,47 @@
 # Local Guard vs Guard Cloud
 
 Guard protects your machine first. Guard Cloud is an optional paid service
-providing cloud history, visibility, sync, and management around that protection.
+providing cloud history, visibility, sync, and governance around that protection.
+
+The product boundary is defined by
+[ADR 0011: Extension-First Managed Controls](./adr/0011-extension-first-managed-controls.md)
+and the [Managed Controls Product Glossary](./managed-controls-glossary.md).
 
 ## Local Guard baseline
 
 Available without a Cloud subscription or sign-in:
 
-- **Launch interception and wrappers** — `hol-guard install` and `hol-guard run`
+- **Launch interception and wrappers** - `hol-guard install` and `hol-guard run`
   sit in front of supported AI harnesses before tools, MCP servers, or skills
   execute.
-- **Local policy decisions** — home config, project overrides, saved allow/deny
-  rules, and built-in recommendations resolve on this machine. Saved local
-  decisions are verified against Guard-managed integrity key material before
-  they become authoritative again.
-- **Local blocking and warnings** — Guard can stop or warn on supported risky
+- **Local Extensions, settings, and remembered decisions** - built-in Extension
+  permissions, home config, project overrides, and remembered allow or deny
+  decisions resolve on this machine. Saved local decisions are verified against
+  Guard-maintained integrity key material before they become authoritative
+  again.
+- **Local blocking and warnings** - Guard can stop or warn on supported risky
   shell commands, file reads, MCP tool calls, skill loads, and prompt-sensitive
   actions before side effects occur.
-- **Package-manager protection where supported** — supported managers (for
-  example npm and PyPI) can be intercepted locally through shims and runtime
-  evaluation. Unsupported or monitor-only managers stay advisory only.
-- **Local receipts and explain output** — `hol-guard receipts`, `hol-guard
+- **Package-manager protection where supported** - supported managers, including
+  npm and PyPI, can be intercepted locally through shims and runtime evaluation.
+  Unsupported or monitor-only managers stay advisory only.
+- **Local receipts and explain output** - `hol-guard receipts`, `hol-guard
   explain`, and the local approval center record what Guard decided and why.
-- **Local approval and review paths** — inline harness approval, the local
+- **Local approval and review paths** - inline harness approval, the local
   approval center on `127.0.0.1`, and `hol-guard approvals` resolve decisions
   without Cloud.
-- **Local policy integrity tooling** — `hol-guard policies verify`,
+- **Local decision-integrity tooling** - `hol-guard policies verify`,
   `integrity-status`, `migrate-local-integrity`, and `repair --clear-invalid`
-  let an operator detect unsigned, unknown-key, or tampered local policy rows
-  and move to enforce mode deliberately.
-- **Cloud-outage independence** — if Guard Cloud is unavailable, you are signed
+  retain their compatibility names and let an operator detect unsigned,
+  unknown-key, or tampered local decision rows.
+- **Cloud-outage independence** - if Guard Cloud is unavailable, you are signed
   out, your trial ends, a subscription is past due or canceled, or you never
-  connected, local interception, policy, blocking, receipts, and approvals
+  connected, local interception, Extensions, blocking, receipts, and approvals
   continue on the machine.
 
 Guard does not meter local safety features. You can detect harnesses, install
-launchers, diff changes, prompt for approval, and inspect receipts without
-signing in.
+launchers, configure Extensions, diff changes, prompt for approval, and inspect
+receipts without signing in.
 
 Safe Decode runs locally too. It inspects encoded payload layers for review
 evidence, but never executes decoded payloads and only syncs redacted summaries
@@ -44,8 +49,8 @@ when optional Cloud receipt sync is enabled.
 
 ## Guard Cloud for individual developers
 
-Guard Cloud is a personal AI safety cockpit and memory layer. It does not gate
-baseline local protection.
+Guard Cloud is a personal AI safety cockpit and governance layer. It does not
+gate baseline local protection.
 
 ### Solo
 
@@ -59,6 +64,7 @@ without changing what Guard can protect locally:
 - a weekly personal security digest
 - matched critical advisory email
 - individual receipt download and a retained-history basic CSV/JSON export
+- read-only Extension posture visibility for connected devices
 
 The two-device limit is a Cloud-sync limit only. A third machine still installs,
 intercepts, prompts, blocks, and writes local receipts normally. If the Portal
@@ -71,9 +77,10 @@ accurately.
 Pro remains the personal power-user tier. Portal-provided entitlements are the
 source of truth, but the product boundary includes longer history and storage,
 all supported personal-device Cloud continuity subject to the current service
-policy, real-time alerting, policy version history, advanced search, and full
-evidence export. The local client does not hardcode plan prices or use plan
-names as enforcement logic.
+policy, real-time alerting, personal Control Sets, simulation, version history,
+rollout, rollback, acknowledgement, advanced search, and full evidence export.
+The local client does not hardcode plan prices or use plan names as enforcement
+logic.
 
 ### Cloud error contract
 
@@ -90,7 +97,7 @@ messages. Known normal plan boundaries include:
 
 These codes describe Cloud state only. A network outage, billing state, trial
 state, retention limit, storage limit, or device limit must never be translated
-into “protection expired,” “device blocked,” or another claim that local Guard
+into "protection expired," "device blocked," or another claim that local Guard
 stopped working.
 
 Optional Cloud pairing commands:
@@ -126,34 +133,46 @@ without disconnecting Cloud sync. See the full
 
 ## Guard Cloud for teams
 
-Team plans add shared ownership, routing, RBAC, billing, and evidence exports
-on top of the individual Cloud value:
+Team plans add shared ownership, managed Control Sets, routing, RBAC, billing,
+and evidence exports on top of the individual Cloud value:
 
 - **Shared workspaces** with members, roles, service principals, and ownership
-- **Shared review workflow** with assignment, SLA, policy memory, cases, and
-  audit history
-- **Integrations** — Slack, GitHub, Jira, PagerDuty, email, and webhooks where
+- **Managed controls** with Extension targeting, simulation, review, staged
+  rollout, acknowledgement, drift, rollback, and audit evidence
+- **Shared review workflow** with assignment, SLA, remembered decisions, cases,
+  exceptions, and audit history
+- **Integrations** - Slack, GitHub, Jira, PagerDuty, email, and webhooks where
   setup and delivery are available
-- **Team package firewall visibility** and exception governance
+- **Team Package Firewall visibility** and exception governance
 - **Billing, plan limits, admin controls, exports, and enterprise materials**
 
+A `managed-restrictive` Control Set is limited in release 3.0 to disabling an
+Extension, disabling a permission, or activating global lockdown. It is
+separately negotiated and cannot be weakened by local remembered decisions.
+Local tightening remains valid.
+
 ## Quick comparison
 
 | Capability | Local Guard | Solo Cloud | Pro Cloud | Team Cloud |
 | --- | --- | --- | --- | --- |
-| Launch interception and local policy | Included | Included | Included | Included |
-| Local blocking/warnings on supported actions | Included | Included | Included | Included |
+| Launch interception and Local Extensions | Included | Included | Included | Included |
+| Local blocking and warnings on supported actions | Included | Included | Included | Included |
 | Local receipts and approvals | Included | Included | Included | Included |
 | Works when Cloud is offline | Yes | Local protection continues; sync pauses | Local protection continues; sync pauses | Local protection continues; sync pauses |
 | Cloud-connected personal devices | None required | 2 | Portal entitlement | Managed by workspace |
 | Cloud history | None required | 30 days | Portal entitlement | Workspace policy |
 | Decision memory across machines | No | Included | Included | Included |
+| Read-only Extension posture | Local only | Included | Included | Included |
+| Personal Control Sets | No | No | Included | Included |
+| Managed-restrictive Control Sets | No | No | No | Included |
 | Real-time Cloud activity alerts | No | Not included | Portal entitlement | Team routing |
 | Full evidence bundles | Local export only | Not included | Portal entitlement | Team evidence |
-| Team RBAC, routing, and shared policy | No | No | No | Included |
+| Team RBAC, routing, and shared governance | No | No | No | Included |
 
 ## Related docs
 
+- [Extension-First Managed Controls ADR](./adr/0011-extension-first-managed-controls.md)
+- [Managed Controls Product Glossary](./managed-controls-glossary.md)
 - [Get started](./get-started.md)
 - [Harness support](./harness-support.md)
 - [Remediation](./remediation.md)

plugin_scanner-3.0.0a214/docs/guard/managed-controls-glossary.md

@@ -0,0 +1,126 @@
+# Managed Controls Product Glossary
+
+This glossary is the shared product-language contract for HOL Guard 3.0 and Guard Cloud. Protocol and compatibility names may remain technical where changing them would break clients or increase release risk.
+
+## Core objects
+
+### Extension
+
+A stable Local capability boundary for a protected tool or capability domain, such as Git, Docker, Kubernetes, GitHub, npm, or MCP. An Extension groups permissions, detector rules, dependencies, safer guidance, and source metadata.
+
+Use **Extension** in customer-facing copy. Do not call an Extension a policy, module, integration, or rule.
+
+### Permission
+
+An independently configurable capability inside an Extension. A permission owns the detector rules and typed capabilities needed to recognize that behavior.
+
+Use **permission** when the user can understand and configure a discrete capability. Keep detector implementation details under Technical details.
+
+### Detector rule
+
+A Local implementation detail that recognizes security-relevant evidence. Detector rules produce evidence. They do not grant authority or make final policy decisions.
+
+Use **detector rule** only in technical documentation, diagnostics, receipts, and advanced authoring.
+
+### Local setting
+
+A device-specific Extension or permission preference. A Local setting may preserve or strengthen protection but cannot weaken a required floor or managed restriction.
+
+Use **On this device**, **Local preference**, or **Local block** in the interface rather than the ambiguous label **managed**.
+
+### Remembered rule
+
+A contextual decision remembered from an approval. A remembered rule answers how Guard should handle an equivalent future request. It is not an Extension setting and cannot bypass a managed restriction.
+
+Use **remembered decision** or **remembered rule** in customer-facing copy. Avoid calling remembered decisions policies.
+
+### Control Set
+
+A versioned, scoped, simulated, reviewed, signed, deployed, acknowledged, and auditable collection of Extension controls and contextual rules in Guard Cloud.
+
+Use **Control Set** as the primary customer-facing Cloud object. Technical `GuardPolicy`, policy document, policy version, and bundle names remain valid implementation terms.
+
+### Managed controls
+
+The Guard Cloud product surface for creating, reviewing, deploying, monitoring, and auditing Control Sets.
+
+Use **Managed controls** as the page and navigation label. Keep `/guard/controls` canonical and `/guard/policy` as a compatibility alias.
+
+### Managed restriction
+
+A signed `managed-restrictive` workspace floor that can disable an Extension, disable a permission, or activate global lockdown. It cannot be weakened locally in release 3.0.
+
+Use **Managed by <workspace>** when the workspace name is available. Use **Workspace restriction** when it is not. Do not use a bare **Managed** badge.
+
+### Deployment
+
+A signed Control Set version delivered to an eligible runtime cohort with acknowledgement, drift, pause, rollback, and audit state.
+
+Use **deployment** for the lifecycle. Use **rollout** for staged delivery within a deployment.
+
+### Exception
+
+A time-bounded, reviewed contextual deviation with reason, evidence, expiry, and reviewer state. In release 3.0, an exception cannot weaken a managed-restrictive Extension or permission block.
+
+## Authority modes
+
+### Personal shared
+
+`personal-shared` applies shared posture to a user's authorized devices. Local tightening remains valid.
+
+### Workspace shared
+
+`workspace-shared` applies shared workspace posture. Local tightening remains valid.
+
+### Managed restrictive
+
+`managed-restrictive` creates a signed workspace floor. Release 3.0 limits this mode to Extension disable, permission disable, and global lockdown.
+
+## Decision outcomes
+
+### Permit
+
+The contextual policy action `allow`. Permit does not override a required floor, a Local block, a shared restrictive control, or a managed restriction.
+
+### Review
+
+The contextual policy action `review`. Guard pauses for an authorized decision according to the existing approval workflow.
+
+### Block
+
+The contextual policy action `block`. Guard denies the contextual request.
+
+### No contextual decision
+
+No contextual policy action is authored for the selected Extension or permission. Extension posture and existing runtime floors still apply.
+
+Do not present **Warn** or **Remember** as canonical Control Set outcomes. Warning is presentation behavior derived from a representable policy action. Remembering is an approval-memory operation, not a policy action.
+
+## Source labels
+
+Use precise labels that explain authority and provenance:
+
+- **Built into HOL Guard**
+- **On this device**
+- **Synced from Guard Cloud**
+- **Managed by <workspace>**
+- **Required by HOL Guard**
+- **Package Firewall**
+- **Custom Extension, local only**
+
+Avoid bare **Managed**, **Inherited**, or **Cloud** labels without an explanation of source and effect.
+
+## Compatibility language
+
+The following remain valid in protocol, API, database, route, and migration contexts:
+
+- `GuardPolicy`
+- policy document
+- policy bundle
+- policy version
+- policy compiler
+- policy route
+- `/policy`
+- `/guard/policy`
+
+Customer-facing headings should use Managed controls, Control Sets, Extensions, permissions, remembered decisions, and Rules & exceptions unless a technical detail is being shown explicitly.