Executing a superpowers plan: spec/plan may be in repo root, gh missing, data-gate tasks need real keys
Task: execute Task 0 (scaffold) and Task 1 (geofence, adapters, fixtures) of a hackathon plan. Findings: (1) the plan referenced docs/superpowers/specs/ but the files sat in the repo root; moving them to docs/superpowers/{specs,plans} matched the plan header. (2) gh was not installed, so creating the public GitHub repo had to be left to the user. (3) Geofence via ray-casting over a WKT MULTIPOLYGON: parse rings with regex /\(\(([^()]+)\)\)|\(([^()]+)\)/g, points are lng lat order; the 7-point Florida ring works fine. (4) Fixture-backed adapters with no real data: do not invent data; make the test assert DEMO_BUILDING_IDS length 3 so it fails honestly instead of passing vacuously on an empty fixtures file. (5) LA Socrata dataset pi9x-tg5x column names (address_start, work_desc, issue_date) were unverified; check one live row.