Make main the lean product a site receives

main was 16 days and 259 commits behind the line the product is actually built
on, at contract 0.30.0 against 0.35.0, with no per-PC credential code at all. It
was neither current nor curated - just stale. This brings it forward and, at the
same time, makes it mean something: main is what a receiving site installs, and
nothing else.

WHAT IT CARRIES. Twelve plugins - backups, computers, endpoints, guides,
knowledgebase, machines, network, notifications, printers, slides, tools,
warranty - plus applications, which is manifest-less core and always ships. The
only manifest dependency inside that set is endpoints on computers, and both are
in it, so the closure is self-contained.

WHAT IT DOES NOT. employees, geenforce, measuringtools, printedparts and usb
stay on the site line. So do the Windows installer tree, the VM rehearsal
helpers, the agent tooling config, one site's data loader, the internal audit
and findings records, and the planner spreadsheet. 1,135 tracked files against
1,438.

A REMOVAL THAT BREAKS THE APP IS NOT A REMOVAL, and two nearly shipped:

deploy/site-profile-universal.json still named all seventeen plugins. It is the
file docs/DEPLOY.md tells a site to provision from, so a fresh install would
have failed at `flask plugin apply-profile` with PluginError - the first thing a
receiving site does, broken by the branch meant to serve them. It now names the
twelve that exist, and its comment says the two must agree.

agent/ was never refreshed. Whoever populated this branch copied shopdb/,
plugins/, frontend/ and tests/ from the site line and left the agent tree at its
September state: 22 C# and PowerShell sources missing, including AgentCredentials,
EnrollmentService, AgentHttpFactory and the fleet-alert client, plus one file the
site line had deleted still present. The old tree is internally consistent, so it
compiles, and nothing in CI builds it - every gate was green over a server that
speaks enrollment and per-PC credentials to a bundled agent source that cannot.
Resynced whole.

DECISIONS THIS ENCODES, rather than defers:

- The plugin-authoring lab builds printedparts, whose manifest depends on
  employees, so it could not stay. The lab remains on the site line and main
  ships no build-along tutorial. That is a real loss for an adopting developer
  and is recorded here rather than discovered later.
- Recognition, Training and Recertification notifications are no longer seeded.
  Each splits one notification into a card per employee and renders a photo,
  which needs a plugin this branch does not bundle. Seeding them would offer an
  author a type that cannot resolve anybody. A site that installs employees gets
  them from that plugin's own seed.
- Windows/IIS is documented as the legacy path throughout, and the README leads
  with Docker, because that is what a receiving site gets.

The API description is regenerated for THIS branch - 347 paths and 483
operations, down from 415 and 573 - so the published contract describes what is
here rather than what the site line serves. docs/CONFIG.md lost the two
measuring-tool label keys the code no longer declares, which two lanes had
decided opposite ways.

Suite: 3124 passed, 6 skipped. Naming and style gates pass. The docs gates run
rather than skip, and every index line count is derived from the file it names.

plugins/computers/models/__init__.py

@@ -14,8 +14,11 @@ from .policy import (
     BusinessPolicyItem,
     POLICY_SOURCE_LOCAL,
     POLICY_SOURCE_SHIPPED,
+    POLICY_SOURCE_AUTOAPP,
     ACTION_MODE_DESIRED,
     ACTION_MODE_GATE,
+    PolicyActionHold,
+    DEFAULT_HOLD_MINUTES,
 )
 
 __all__ = [
@@ -30,6 +33,9 @@ __all__ = [
     'BusinessPolicyItem',
     'POLICY_SOURCE_LOCAL',
     'POLICY_SOURCE_SHIPPED',
+    'POLICY_SOURCE_AUTOAPP',
     'ACTION_MODE_DESIRED',
     'ACTION_MODE_GATE',
+    'PolicyActionHold',
+    'DEFAULT_HOLD_MINUTES',
 ]

plugins/computers/models/jsontext.py

@@ -3,7 +3,7 @@
 MySQL 5.6 has no JSON type - it arrived in 5.7 - and a site is still running
 5.6, where `sa.JSON()` fails at migration time with a bare syntax error near the
 word JSON. Every other JSON-bearing column in this product is already TEXT for
-that reason: guides' `blocksjson`, GE-Enforce's `manifestjson`.
+that reason: guides' `blocksjson`, backups' payload column.
 
 This keeps the Python side identical. A model attribute still holds a dict or a
 list, still assigns and reads like one; only the storage changes. The

plugins/computers/models/policy.py

@@ -27,12 +27,35 @@ from .jsontext import JSONText
 # owner. Kept a plain string, not an enum column, so adding a source is data.
 POLICY_SOURCE_LOCAL = 'local'
 
-# Product-owned rows we ship (the shopfloor app monitor bundle). Same read-only
-# treatment as any non-local source: the CRUD API refuses to edit or delete
-# them, the seeder reconciles them. Distinct from 'local' so a site's own
-# policies are never confused with what the product shipped.
+# Rows the product seeds (the shopfloor monitor policies, one per monitor).
+# Distinct from 'local' so a site's own policies are never confused with what
+# the product shipped, and so the UI can badge the origin.
+#
+# A shipped row is EDITABLE and DELETABLE, unlike a genuinely external source.
+# The product ships a starting point, not an opinion about one site's floor: a
+# plant that runs no MTConnect must be able to drop that policy. source stays
+# 'shipped' through an edit, so provenance is a fact about where the row came
+# from rather than a claim about who controls it now.
+#
+# Nothing reconciles these rows. The seeding migrations are insert-if-absent
+# (they SELECT by name and return early if it exists), so an upgrade cannot
+# stomp a site's edits. That property is load-bearing now that the rows are
+# editable - do not replace it with a reconciling seeder without adding a
+# dirty flag first.
 POLICY_SOURCE_SHIPPED = 'shipped'
 
+# Rows generated FOR US by another surface rather than authored by hand: today
+# the "Required on all PCs" checkbox on an Application. Distinct from 'local' so
+# unchecking the box knows which policy it owns and may safely remove.
+#
+# It doubles as the "untouched" test. An autoapp row is one nobody has
+# customised, so it is safe to delete when the box is unchecked. The moment an
+# admin edits it through the policy CRUD API it becomes 'local' - their work
+# now, not ours - and unchecking warns instead of deleting. That keeps the
+# generated policy convenient without letting it silently destroy hand-authored
+# changes.
+POLICY_SOURCE_AUTOAPP = 'autoapp'
+
 
 class ConfigurationPolicy(BaseModel):
     """A single reusable policy: a scope plus the actions it applies.
@@ -202,3 +225,82 @@ class BusinessPolicyItem(BaseModel):
     def __repr__(self):
         return (f"<BusinessPolicyItem bp={self.businesspolicyid} "
                 f"cp={self.configurationpolicyid}>")
+
+
+# Default life of a break-glass suppression hold, used when the caller names no
+# window. Long enough to comfortably outlast one maintenance window, short
+# enough that nobody has to remember to clear it: policy resumes on its own.
+#
+# A caller MAY name any window instead, including none at all (expiresat NULL,
+# an indefinite hold). That is a deliberate escape hatch for work that cannot be
+# bounded up front, and it forfeits the self-healing this default exists to
+# provide - see the class docstring.
+DEFAULT_HOLD_MINUTES = 240
+
+
+class PolicyActionHold(BaseModel):
+    """A time-boxed suspension of desired-state reconciliation for one action.
+
+    An admin break-glass override on a `gate`-mode action is a one-shot - policy
+    only said "not exposed", and nothing reverses it. An override on a
+    `desired`-mode action is a fight: the admin stops a service and the
+    reconciliation loop restarts it on the next check-in, so the override looks
+    broken in production. A hold records that fight's outcome server-side, and
+    the resolver drops the held action out of the desired set until it expires.
+
+    Expiry is evaluated at RESOLVE time against expiresat, never by a sweeper
+    job. A sweeper that stalls would silently extend every hold it failed to
+    clear, which is policy disabled by accident - the failure mode this design
+    exists to avoid. Rows are left behind after expiry deliberately: an expired
+    hold is the audit record of what was suppressed, by whom, and why.
+
+    expiresat is NULLABLE, and null means indefinite: the hold applies until an
+    admin releases it by hand. This is the one case where the self-healing
+    property above does not hold, so treat it as the sharp edge it is - an
+    indefinite hold silently disables reconciliation of that action forever, and
+    the endpoint will keep reporting healthy while it drifts. Nothing in the
+    system surfaces a stale hold; the only guard is the admin who placed it.
+
+    Every read of this table must therefore test `expiresat IS NULL OR
+    expiresat > now`. Testing only the comparison drops indefinite holds, which
+    would let policy quietly resume against an admin who asked it not to.
+    """
+    __tablename__ = 'policyactionholds'
+
+    policyactionholdid = db.Column(db.Integer, primary_key=True)
+
+    assetid = db.Column(
+        db.Integer,
+        db.ForeignKey('assets.assetid', ondelete='CASCADE'),
+        nullable=False,
+    )
+
+    # Allowlisted action name, same vocabulary as ConfigurationPolicyAction.
+    action = db.Column(db.String(100), nullable=False)
+
+    # Naive UTC, matching BaseModel timestamps. Null means indefinite - the
+    # hold stands until released by hand.
+    expiresat = db.Column(db.DateTime, nullable=True)
+
+    # Who placed it. The id goes null if the user is deleted, but the username
+    # snapshot survives: a break-glass record that forgets who used it when the
+    # account is removed is worthless at review time.
+    createdbyuserid = db.Column(
+        db.Integer,
+        db.ForeignKey('users.userid', ondelete='SET NULL'),
+        nullable=True,
+    )
+    createdbyusername = db.Column(db.String(100), nullable=True)
+
+    reason = db.Column(db.Text, nullable=False)
+
+    __table_args__ = (
+        db.Index('idx_policyactionhold_asset', 'assetid'),
+        db.Index('idx_policyactionhold_expiry', 'expiresat'),
+    )
+
+    def __repr__(self):
+        until = self.expiresat or 'indefinite'
+        return (f"<PolicyActionHold asset={self.assetid} {self.action} "
+                f"until={until}>")
+