docs(store): point store-facing refs at 1132-Fixer/chrome, correct publisher

[JG2547]

What

Five references to the dead pre-transfer identity PrimeUpYourLife/1132-Fixer-Chrome survived the move to the 1132-Fixer org. All five are store-facing, so anyone following them gets a 404.

File	Before	After
STORE_LISTING.md:112	https://github.com/PrimeUpYourLife/1132-Fixer-Chrome	https://github.com/1132-Fixer/chrome
STORE_LISTING.md:113	.../1132-Fixer-Chrome/issues	https://github.com/1132-Fixer/chrome/issues
PRIVACY_POLICY.md:92	"published by PrimeUpYourLife"	"published on the Chrome Web Store by High-Texas"
ds-bundle/README.md:52	PrimeUpYourLife/1132-Fixer-Chrome	1132-Fixer/chrome
STORE_PREP.md:379	DONE proved by https://primeupyourlife.github.io/1132-Fixer-Chrome/privacy.html	DONE proved by https://1132-fixer.github.io/chrome/privacy.html, old URL recorded as dead

grep -rni "primeupyourlife" over the tree now returns nothing.

Every claim was measured, not assumed

Publisher. Fetching store item fccnmckeeddpkhocebnbfnlapcjllljh returns:

<div class="QDHp8e">Offered by</div><div>High-Texas</div>

This matches the publisher already recorded at STORE_PREP.md:386 ("publisher High-Texas"), so the corrected privacy-policy line is consistent with the rest of the repo.

Pages URLs, re-measured 2026-08-23:

200  https://1132-fixer.github.io/chrome/privacy.html
404  https://primeupyourlife.github.io/1132-Fixer-Chrome/privacy.html

The STORE_PREP.md:379 row asserts "content matches PRIVACY_POLICY.md", so the live page was checked by content and not just by status code — distinctive sentences from the Affiliation and trademark paragraphs are present in the served HTML. That row's claim now rests on a URL that actually resolves, and it lines up with STORE_PREP.md:117, which already documented the old URL as dead.

Verification

Both required checks were run on this branch after every commit and exited 0:

• npm test — Passed: 55, Failed: 0 (validate-extension + popup e2e + package tests)
• node scripts/verify-store-listing.js — all 8 listing fields within the store's limits

The listing verifier only measures the ```text field blocks under ### headings; the edited lines all live in plain Markdown tables and prose, so no field character count moved.

Constraints honored

• Documentation only — no code, no manifest.json change (still 1.2.7).
• No Chrome Web Store upload or publish.
• No release, no tag.
• No force-push; branch + PR.
• feat/20-core-extraction untouched.

🤖 Generated with Claude Code