gitignore + untrack extracted/ (kept on disk); master-server GetExpedition op

- .gitignore: ignore /extracted/ (regenerable game data) and /tmp/ (scratch)
- git rm --cached the 38 extracted/ files: untracked but left on disk, not deleted
- master_scrape.py: add GetExpedition=7 to ACTIONS (was missing; pulls ExpeditionDto.Trampler)
- docs: mark master-server /connect blocker cleared 2026-06-16 (server back up);
  server-side upsert hash validation remains untested (live re-test not yet run)

docs/TRAMPLER.md

@@ -95,7 +95,8 @@ won't match the stored hash and the walker is flagged stale (`VERSION:False`,
 are **integrity / version-staleness markers, not security** — plain unsalted MD5 we reproduce offline;
 the client just regenerates them. From the *client editor's* view the **Definition** hashes appear inert
 (no effect on `ERRORS` or `VERSION`); whether the **server** validates them on upsert is still untested
-(blocked by master-server `/connect` NREs during this playtest).
+(the master-server `/connect` blocker is cleared as of 2026-06-16 — server back up — but the live
+re-test has not been run yet).
 
 Practical upshot for offline editing: edit the `.wbt`, then either recompute the two structural hashes
 yourself (`walker/walker_hashes.py`, exact) or just let **one in-editor save** regenerate all five.
@@ -141,6 +142,8 @@ with ±90° firing wedges, rams, cargo numbered **C1–C8** in JSON order. Outpu
   hashes (loads, opens, edits, and regenerates all 5 on save). Whether the **master server** validates
   the hashes (esp. the server-sourced `DefinitionsHash` / per-part `DefinitionHash`) when a blueprint is
   `UpsertTrampler`'d — i.e. whether it recomputes, rejects, or stores blanks — is not yet known. It was
-  blocked this playtest by the master server throwing `System.NullReferenceException` and closing the
-  socket on `/connect` (no successful login). Re-test once `/connect` is healthy: upsert a walker with
-  Definition hashes blank, then `GetTrampler` it back and diff. See [MASTER_SERVER.md](MASTER_SERVER.md).
+  previously blocked by the master server throwing `System.NullReferenceException` and closing the socket
+  on `/connect` (no successful login); **that blocker is cleared as of 2026-06-16 — the master server is
+  back up**, so the re-test is now unblocked but **has not been run** (awaiting explicit go-ahead for the
+  live op). Re-test: upsert a walker with Definition hashes blank, then `GetTrampler` it back and diff.
+  See [MASTER_SERVER.md](MASTER_SERVER.md).