STRIKE SYNC, powered by Alley Tally — v0.13
Windows 10/11 · diagnostic discovery release · no live-score decoder yet

START HERE
1. On Alley Tally /bridge/connect, create an automatic-discovery connection code.
2. Download and extract ALL files in this ZIP into a folder.
3. Double-click Start Strike Sync.cmd. Enter the AT code and click
   Connect Strike Sync. Approve the Windows administrator prompt.
4. Send one photo of the connection result. Check Alley Tally's
   connection dashboard. No scoring filename is required.

WHAT IT DOES
Runs as the Windows service AlleyTallyStrikeSync (LocalService account).
Starts automatically with Windows, including when no one is signed in.
Checks common BLS/CDE/Vector/Qubica/Conqueror/QSERVER/Secy folders, scoring
shortcuts and installed application locations. It checks bounded locations,
not the entire disk. It scans up to 24 roots, up to 50 subfolders per root, depth 4, and
100 candidate files shared across roots. It automatically captures .s00 files by default. The owner
can remotely select other data files (up to 24 files, 1 byte–20 MiB each)
and add file patterns without a new installation.

It reads stable copies only: never edits the center's scoring files.
File notifications and periodic checks detect changes. A file must remain
stable for 5 seconds and be unchanged before/after copying. Initial samples
and later changed samples are automatically uploaded for format validation.
Candidate detection does NOT mean scores have been decoded or verified.
Cloud uploads use TLS, a revocable center code, and per-file SHA-256 IDs.
The private diagnostic report includes filenames, relative locations,
size/time and scoring root paths with access status. Connection codes are encrypted locally and
are never written to logs or placed in command-line arguments.

OUTAGES / RETENTION
Retries uploads after an outage. Keeps at most the latest two local copies
per file within a 128 MiB disk budget. It is a bounded diagnostic collector,
not a permanent archive: long outages can replace older unsent samples.
Cloud retains a bounded number of files/samples according to the dashboard.
A deleted/revoked connection code stops successful uploads; reinstall with
a new code to reconnect. Running the installer again updates configuration.

SLEEP AND NETWORK SHARES
Keep computer awake is checked by default. It requests system wakefulness;
the screen can turn off. Actual sleep, shutdown, hibernation or a Windows
policy can still stop monitoring. After wake/start it checks files again.
Mapped drive letters are user-specific. Setup records their UNC locations
before requesting administrator approval. LocalService normally cannot
read authenticated network shares. A center administrator must grant the
service account suitable access or run the service under an approved
restricted center account via Windows Services. Do not give staff passwords
to Alley Tally. If discovery reports no readable files, an administrator can
add a known scoring folder using the installer's optional folder button.
We cannot guarantee discovery for unknown paths or scoring file formats.

FALLBACK
The sign-in fallback is hidden until an always-on install is attempted and
fails or UAC is cancelled. It asks for acknowledgement, then starts at this
Windows user's sign-in. This mode stops on sign-out and does not operate
while no one is signed in. The dashboard labels it as user mode.

WINDOWS SECURITY / REQUIREMENTS
Administrator rights are needed once for the always-on service. Windows
PowerShell 5.1 and .NET Framework 4's built-in compiler are used; no paid
packages, runtime downloads or cloud video/AI services are required.
This ZIP is not code-signed. Windows or center security software may block
unsigned scripts/service creation; the administrator must review/approve
according to the center's policy. Do not bypass center security policies.
Service/sample data: C:\ProgramData\AlleyTallyStrikeSync (restricted ACL).
Installed service code: Program Files\Alley Tally\Strike Sync.
Fallback data/code: this user's LocalAppData\AlleyTallyStrikeSync.
Use Windows Services to inspect, stop, or restart AlleyTallyStrikeSync.

REMOVE
Administrator PowerShell:
  Stop-Service AlleyTallyStrikeSync
  sc.exe delete AlleyTallyStrikeSync
Then remove the installed folder and protected data folder if no longer
needed. For fallback, remove Strike Sync.lnk from the user's Startup folder
and stop its Monitor.ps1 PowerShell process before deleting its data.
Revoke the center connection code in Alley Tally as well.

TEST STATUS
Built and statically checked in a Linux development environment. Actual
installation, signed-out service operation, permissions, sleep prevention
and live .s00 capture still require a Windows center acceptance test.

REMOTE MANAGEMENT
After installation and pairing, the service checks Alley Tally every 30 seconds for owner-controlled search settings. The owner can change scoring folders and approved file patterns, pause capture, select up to 24 files, request rescans and request snapshots. It reports up to 100 candidate files and root accessibility. Default capture remains .s00 files; other formats are inventory only until selected. Scoring files are read only. No shell commands or executable updates are accepted. Windows folder permissions still apply. Configuration is cached across restarts. The center computer needs an Internet connection and must be awake. This package is diagnostics, not yet a verified live-score decoder.

V0.13 CONNECTION AND UPDATES
All traffic first tries HTTPS to alleytally.com, then the hosted address
alley-tally.jppierce1981.chatgpt.site if a request fails or is not acknowledged.
Both addresses use the same app, connection code and sample store.
Fallback stays preferred for five minutes, then alleytally.com is retried.
Configuration, heartbeats and samples all use this fallback. Requests are
bounded to two attempts; redirects are refused and TLS remains enabled.
A lost sample acknowledgment may trigger a retry with the same file hash;
the server deduplicates that sample. If both fail, local collection continues
with cached settings and the bounded sample queue.
Status reports show the last successful address and fallback count.
Use only with the center's approval. This does not alter its firewall settings.
Setup tests the authenticated configuration endpoint before changing an installation.
An existing signed-in installation can be updated using Use sign-in fallback;
leave the code blank to reuse its locally encrypted connection code.
Existing local queue files are retained. The old fallback monitor is stopped
before the replacement starts, avoiding a stale process keeping the old endpoint.
To install the Windows service, click Connect Strike Sync and approve UAC.
Automatic collection is still diagnostic; score decoding is not enabled.
The known Paradise share is \\QSERVER\Secy, not the local C:\Secy folder.
Add it with Optional: add scoring folder, or the owner can configure it remotely.
Service accounts need appropriate network-share permissions.
Windows installation and connectivity from the center still require verification.

AUTOMATIC RECONNECTION
If both addresses fail, retries back off from 15 seconds to five minutes,
with a small random delay. The monitor keeps reading files with cached settings
and retains its bounded queue. Recovery does not need a browser login.
Protected connection-status.json remembers the last working address and retry
time across monitor restarts. Once online, diagnostics describe endpoint
failures, last success and which address worked. HTTP 403 is a denial, not
proof of a particular firewall. The monitor cannot repair revoked codes,
Windows permissions, blocked destinations or a stopped/powered-off computer.
It does not try proxies, VPNs, arbitrary domains or disable TLS/firewalls.
Windows service restart-on-failure remains enabled; local data is preserved.

V0.13 HONEST CONNECTION CONFIRMATION
Setup waits up to 90 seconds after startup for this monitor run to receive
a server acknowledgment of its heartbeat. Browser access or a configuration
GET does not satisfy this check. A saved heartbeat from a previous run does
not satisfy it. Server connected confirms communication, not scoring-file
access or verified live scoring. If the timeout expires, setup says installed
and running, connection pending; the service stays active and retries.
Only an installation/startup failure offers sign-in fallback.


UPDATING AN EXISTING SIGNED-IN INSTALLATION (v0.13)
Download and extract this release. Open Start Strike Sync.cmd using the same
Windows account as the existing monitor. Leave the setup code blank and click
Update / restart existing. Setup reuses the encrypted connection, checks server
access before stopping anything, identifies the old monitor by its exact script
and data-directory command-line arguments, and replaces it. A stale process.json
PID is not trusted. Other PowerShell sessions and scoring programs are untouched.
Existing queue files and cached settings are retained. The previous Monitor.ps1,
Connection.ps1 and startup shortcut are kept in the protected previous-version
folder; setup attempts to restore/restart them if the replacement fails to start.
A running replacement with a pending server heartbeat is kept running to retry.
The setup code remains hidden. No new setup code is needed for an active pairing.
The old monitor cannot receive a remote stop/update instruction. Someone must
run this downloaded setup once; downloading alone does not stop or change it.
Remote searches, pause/resume and capture refresh remain available after startup.
This is a local application upgrade, not remote desktop access or a remote shell.
Windows process takeover still needs validation on the center computer.


LOCAL WATCHDOG (v0.13)
Both the Windows service and signed-in Startup shortcut now launch Watchdog.ps1.
That separate process supervises Monitor.ps1 and checks every 15 seconds. The
monitor writes a local progress tick from its main loop. Five minutes without
progress causes the watchdog to terminate only its own monitor child and restart
it. Exited children are also restarted. Network heartbeat success is not used as
the health signal: ordinary network failures keep retrying without restart loops.
Startup gets a two-minute grace period; a long scheduling/sleep/clock gap gets a
new two-minute grace period. Retry delays grow from 15 seconds to five minutes
when failures repeat, and reset after ten minutes of healthy operation.
A Windows kill-on-close Job Object stops the owned child if its watchdog is
stopped or crashes, preventing an abandoned monitor during upgrades/service stop.
Queue files and encrypted connection settings are never cleared by recovery.
Local watchdog.json reports process IDs, restart count and controlled reason
codes; no connection code or raw exception text is included. These diagnostics
are included in the regular monitor report when that loop can communicate.
Actual sleep/shutdown still stops processing; user mode needs a signed-in account.
The watchdog cannot repair a permanently inaccessible scoring share or firewall.
Windows runtime acceptance is still required. Run the shipped repository tests
with Windows PowerShell 5.1 to validate policy and upgrade process matching.
