Add the manifest entry that puts the marker backup on the fleet

Scoped to gea-shopfloor-partmarker so it reaches marker bays only. The script
checks the DNC\Mark registry itself as well, so a mis-scoped entry exits
quietly on an ordinary PC rather than erroring every five minutes.

The entry records what the share layout has to provide, because the script
resolves its two modules relative to its own location and one of them,
ShopdbBackupClient.psm1, is shared with the NTLARS backup and has changed. It
also records the schedule and the settings a bay needs, since all three are
places where a deployment can look successful and quietly do nothing.

Also counts a failed capture as a missed backup, not just a busy port. Port
contention resolves itself; a controller that will not answer does not, and
the two are worth telling apart in the count that reaches ShopDB.

playbook/shopfloor-setup/gea-shopfloor-partmarker/manifest-entry-partmarker-backup.json

@@ -0,0 +1,15 @@
+{
+  "_comment": "Drop this entry into the SFLD share's gea-shopfloor-partmarker manifest.json (Applications array). Type=PS1 + DetectionMethod=Always means GE-Enforce runs it straight off the share every cycle under SYSTEM, with no local copy - so updating the script on the share changes fleet behaviour on the next cycle and there is nothing to heal locally. PCTypes scopes it to marker bays; the script also checks the DNC\\Mark registry itself and exits quietly on a PC that drives no marker, so a mis-scoped entry is harmless rather than noisy.",
+
+  "_layout": "REQUIRES THREE FILES ON THE SHARE, and the script resolves its modules relative to its own location ($PSScriptRoot\\..\\lib\\): scripts\\Backup-PartMarker.ps1, lib\\TelesisMarker.psm1, lib\\ShopdbBackupClient.psm1. ShopdbBackupClient is SHARED with Backup-NtlarsSettings.ps1 and is UPDATED by this work (it gained manifest posting, the created-vs-noop reader and skipped-cycle accounting), so deploy the new copy - the NTLARS backup uses none of the additions and is unaffected. If the share puts scripts in apps\\ rather than scripts\\, the lib\\ directory must be its sibling or the imports fail.",
+
+  "_schedule": "Captures run ONLY at shift changes - 14:00 normally, because someone is on site then to fix a problem; 06:00 and 22:00 engage only once the backup is 3+ days overdue. Outside those hours the script exits without touching the port. The marker's COM port is shared with eDNC and is exclusive-open, so a capture at a random hour would fail an operator's mark. The capture also yields the port within about a second if the marker application starts mid-run, and ShopDB's backups_intervalhours throttle still applies on top.",
+
+  "_settings": "ShopDB must have backups_shareroot set, and the bay needs a collector key in HKLM\\SOFTWARE\\GE\\ShopDB\\CollectorKey (or C:\\Enrollment\\shopdb-key.txt) plus a machine number in C:\\Enrollment\\pc-config.txt. Missing any of these is logged once and the cycle skips - it does not error.",
+
+  "Name": "Back up the Telesis part marker (patterns, fonts, settings) to ShopDB",
+  "PCTypes": ["gea-shopfloor-partmarker"],
+  "Script": "scripts/Backup-PartMarker.ps1",
+  "Type": "PS1",
+  "DetectionMethod": "Always"
+}