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.

shopdb/utils/badges.py

@@ -1,11 +1,11 @@
 """What a scanned badge looks like, in one place.
 
-Two kiosks read the same physical badges and disagreed about them. The parts
-kiosk understood both shapes a scanner emits; the USB kiosk took the string
-raw and compared it to an SSO, so the wrapped form was simply "not recognized".
-An operator whose keyboard-wedge scanner emits `0270015376BZ` could take a
-3D-printed part and could not check out a drive - with the same badge, at two
-cabinets a few metres apart.
+Two callers read the same physical badges and disagreed about them. One
+understood both shapes a scanner emits; the other took the string raw and
+compared it to an SSO, so the wrapped form was simply "not recognized". The
+same operator, with the same badge, was recognised at one screen and not at the
+next. Anything that turns a scan into a person uses this module, so there is
+one answer to the question.
 
 The shapes:
 
@@ -17,9 +17,9 @@ of NON-ASCII digits is not, however much it looks like one: Arabic-Indic digits
 pass Python's str.isdigit(), and a badge written in them was accepted, stored as
 the employee's SSO, and joined to nothing afterwards.
 
-This lives in core rather than in either plugin because a plugin may not import
-another plugin, and because a badge is a property of the site, not of a
-cabinet.
+This lives in core rather than in a plugin because a plugin may not import
+another plugin, and because a badge is a property of the site. Its consumer
+today is the notifications plugin, which resolves an employee by SSO.
 """
 
 import re