Canonicalize CycleKeep on GDS and redirect legacy herphase.app

[lightcloud00]

Outcome

Make https://gusdigitalsolutions.com/herphase/ the only canonical HerPhase website and make https://herphase.app/:path* a path-preserving permanent redirect to it. Keep GitHub Pages as a non-indexed compatibility mirror until the redirect is accepted.

Current live truth — 2026-08-20

• Canonical source/deploy owner: lightcloud00/gusdigitalsolutions, public/herphase/**.
• Canonical URL: https://gusdigitalsolutions.com/herphase/.
• Live ASC privacy, marketing, and support URLs already use the GDS canonical family.
• lightcloud00.github.io/herphase-pages/ is already noindex with a GDS canonical.
• herphase.app still serves a Vercel Coming Soon page; /privacy/ terminates at 404.
• No authenticated Vercel session is available and the zone is outside the currently reachable Cloudflare accounts.

Acceptance

• Connect the owning Vercel project/account and confirm whether the owning Cloudflare zone is also required.
• Capture the current managed robots policy before cutover.
• Deploy a path-preserving permanent redirect for root, legal, support, blog, robots, and sitemap paths.
• Prove every redirect terminates at a 200 GDS URL and a nonexistent control remains a genuine 404.
• Prove one canonical family and one sitemap authority with no indexed duplicate host.
• Link the exact deployment/readback receipt to lightcloud00/herphase#100 and the canonical Obsidian HerPhase state.

Blocker and boundaries

Operator credential/account connection is required. No DNS, Vercel, Cloudflare, billing, or ASC mutation is authorized without the corresponding live account and readback gate. Historical investigation is preserved in the comments below.

Related

• Website umbrella: Umbrella: HerPhase website, SEO, and AEO (GDS canonical) #13
• Research child: Apply cross-portfolio keyword research (SEO/AEO/ASO) to herphase-pages #20
• Product roadmap: lightcloud00/herphase#100
• Google/Bing Engine: lightcloud00/gusdigitalsolutions#114

---

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Dependencies

No unresolved dependency is explicitly stated in the current body. If implementation exposes one, record its stable roadmap ID here before dependent work starts.

Plan

1. Revalidate the current evidence above against exact current source or live state.
2. Complete the scoped work and unchecked items above in dependency order, preserving every non-goal and stop gate.
3. Run the focused tests and proof already named; add regression coverage for any corrected defect.
4. Record the exact revision, receipt, and applicable live readback before closure.

Evidence and closure

Close only from exact current-source evidence plus the applicable independent readback. Keep local, GitHub/CI, provider, deployment, device, store, commerce, indexing, traffic, and revenue evidence distinct; one does not imply another.

Owner / lane

The repository delivery lane owns ordinary implementation and verification. The operator owns only actions explicitly marked as operator-only or protected.

Resolution plan

• Verified: 2026-08-25T05:32:40Z against main@47a1a6550d9c0c2316e9ec51fb4105b4209041e1 (commit time 2026-08-23T15:20:14Z).
• Source basis: Original issue body, all 12 comment(s), current default-branch tree, disposition-appropriate source-path checks, and referenced pull-request states.
• Disposition: Code or verification work - not complete on the verified default branch.
• Outcome: Make https://gusdigitalsolutions.com/herphase/ the only canonical HerPhase website and make https://herphase.app/:path* a path-preserving permanent redirect to it. Keep GitHub Pages as a non-indexed compatibility mirror until the redirect is accepted.

Current evidence and corrected premise

Parked outside the current operator queue. Preserve the CycleKeep canonical-source and redirect work, but do not ask Gus to recover Vercel ownership or authorize a domain/provider cutover in this cycle.

Agents may finish and verify source-only prerequisites. Re-admit only with the exact owning account/project, source SHA, path-preserving redirect matrix, rollback, time estimate, and zero-surprise provider request.

No Vercel, Cloudflare, DNS, or deployment mutation occurred.
All 12 issue comment(s) were read. The newest is by @lightcloud00 at 2026-08-25T03:30:50Z.
Newest comment excerpt: Parked outside the current operator queue. Preserve the CycleKeep canonical-source and redirect work, but do not ask Gus to recover Vercel ownership or authorize a domain/provider cutover in this cycle. Agents may finish and verify source-only prerequisites. Re-admit only with the exact owning account/project, source SHA, path-preserving redirect matrix, rollback, time estimate, and zero-surprise provider request. No Vercel, Cloudflare, DNS, or deployment mutation occurred.
Verified source paths on this head:

• robots.txt
  Filed or dossier path references not present on this head; treat them as stale until relocated:
• ASC-IAP-PROBE-20260811.md
• Claudecode/state/marketing-sweep-20260811/SITE-PROBE-20260811.md
• astro.config.mjs
• proof/herphase-pages-12/acceptance.json
• tests/verify-seo-aeo.mjs
• vercel.json

Resolution steps

1. Reproduce the filed condition against the exact default-branch SHA and corrected premise above.
2. Trace the issue-authored files and interfaces below, then implement only the smallest verified remainder.
3. Add or update a focused regression that fails on the verified baseline and passes on the candidate.
4. Run the repository-native focused checks and its broader required gate on the exact candidate head.
5. Revert the bounded change and park the issue if the premise, dependency, or acceptance contract cannot be reproduced.

Grounded issue-authored detail

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Tests and acceptance

Acceptance

• Connect the owning Vercel project/account and confirm whether the owning Cloudflare zone is also required.
• Capture the current managed robots policy before cutover.
• Deploy a path-preserving permanent redirect for root, legal, support, blog, robots, and sitemap paths.
• Prove every redirect terminates at a 200 GDS URL and a nonexistent control remains a genuine 404.
• Prove one canonical family and one sitemap authority with no indexed duplicate host.
• Link the exact deployment/readback receipt to lightcloud00/herphase#100 and the canonical Obsidian HerPhase state.

Dependencies and stop gates

Dependencies

No unresolved dependency is explicitly stated in the current body. If implementation exposes one, record its stable roadmap ID here before dependent work starts.

• Do not close this issue until every acceptance item is mapped to exact merged-head evidence.

Next AI first action

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

[lightcloud00]

⚠️ Correction: the App Review risk in this issue is REFUTED

I wrote that herphase.app serving "Coming Soon" is "a live review risk if it is used as an App Store support or marketing URL." A parallel session checked App Store Connect directly and found ASC points at lightcloud00.github.io/herphase-pages/, not herphase.app.

Independently re-verified just now:

https://lightcloud00.github.io/herphase-pages/          200
https://lightcloud00.github.io/herphase-pages/privacy/  200
https://lightcloud00.github.io/herphase-pages/support/  200
https://lightcloud00.github.io/herphase-pages/terms/    200

All legal URLs resolve. There is no App Review exposure here. Strike that from the issue.

What still stands

The SEO half is unchanged and still real:

• herphase.app serves a stale Vercel "Coming Soon" page with a 1-URL sitemap and no canonical
• the actual content lives at gusdigitalsolutions.com/herphase/ (17 routes, 3 blog posts)
• and now a third copy is live at lightcloud00.github.io/herphase-pages/

So HerPhase content exists on three hosts, and the branded product domain is the one showing a placeholder. That is a duplicate-content and split-authority problem worth deciding — just not an urgent compliance one. Severity drops from release-blocker to housekeeping.

Lesson for whoever picks this up: I inferred the ASC risk from the domain rather than reading the ASC field. ~/.claude/rules/legal-url-lookalike-domains.md says exactly this — read the live ASC field first, because repo and inference both go stale.

[lightcloud00]

Saturday, August 8, 2026 at 12:07 AM ET — claude-code — session 92f5caa7-a0b7-46ce-85aa-4d16c71d9a65

time_utc: 2026-08-08T04:07:00Z
surface: claude-code
session_id: 92f5caa7-a0b7-46ce-85aa-4d16c71d9a65
proof: /Users/gus/Desktop/Claudecode/state/herphase-asc-audit-20260807/RECEIPT.md

Audited the open conditional in this issue against live App Store Connect. Everything measured
above holds — I re-confirmed all seven 404s. Four corrections to the framing and the decision.

---

1. The review-risk conditional is RESOLVED — there is none

"If herphase.app is used as an App Store support or marketing URL, that is a live review risk."

It is not used. Live ASC read (app 6787806352, com.gusdigitalsolutions.herphase):

ASC field	Live value	HTTP
privacyPolicyUrl	https://lightcloud00.github.io/herphase-pages/privacy/	200
supportUrl	https://lightcloud00.github.io/herphase-pages/support/	200
marketingUrl	https://lightcloud00.github.io/herphase-pages/	200

ASC references herphase.app in no field. All seven github.io paths return 200; the control
path /zzz-does-not-exist/ returns a genuine 404, proving hard 200s rather than soft-404s. Content
verified ours (Privacy Policy - HerPhase, gus@gusdigitalsolutions.com), per the
lookalike-domain rule — a 200 alone is not proof of ownership.

Review submission 2e42551b-b1f3-40a8-8cfb-b5989dea307f is WAITING_FOR_REVIEW since
2026-08-03T21:07:07Z, so the app is in review — Apple simply never fetches herphase.app.

This stays a real marketing/SEO defect. It is not a Guideline 5.1.1 risk, and it is not urgent.

2. ⚠️ Option B is dangerous right now, and self-contradictory

"Alternative: deploy herphase-pages to its own domain, make it canonical…"

GitHub Pages serves the ASC URLs from main of this repo (source:{branch:"main",path:"/"},
status:built, public:true, https_enforced:true). main is a live App-Review surface while
review is open. Deploying this repo elsewhere, changing main, or reconfiguring Pages could
break the exact URLs Apple is queued to fetch.

It is also internally inconsistent: the repo root already contains both _redirects and
vercel.json, and both 301 every path off-site to gusdigitalsolutions.com/herphase/*. So
deploying this repo "as canonical" would immediately redirect itself away. Option B requires
deleting/replacing both files first — that is not a small lift, and not one to attempt mid-review.

Freeze baseline: origin/main = 50eee2c0484d9bd9cb6a543e243fa47a9d525f6d.

3. Option A is already written — but it is vercel.json, not _redirects

herphase.app is Cloudflare DNS/proxy in front of a Vercel origin
(x-vercel-cache: HIT, x-nextjs-prerender: 1, NS robin/ishaan.ns.cloudflare.com).

• ✅ vercel.json is the operative file, and it is already correct:
  /:path* → https://gusdigitalsolutions.com/herphase/:path*, permanent: true
• ❌ _redirects is Cloudflare-Pages/Netlify format and is inert on Vercel. Editing it and
  expecting a change would be a silent no-op.

All 8 redirect targets verified 200. So Option A is near-zero code — it needs a deploy, not a fix.

4. Why no agent can do it: the credentials do not exist

• herphase.app is absent from both Cloudflare accounts reachable by the vault token
  (Lightcloud007@gmail.com, Gus@gusdigitalsolutions.com b72a5edf1e…; 15 zones visible).
  GET /zones?name=herphase.app → []. It sits under a third Cloudflare account.
• Zero Vercel credentials in CredVault — verified against the full 436-name inventory, not a
  glob.

This is operator-only regardless of which option is chosen.

5. robots.txt trap — this zone is NOT like appliedtoday.com

herphase.app/robots.txt does carry Cloudflare managed-robots injection:
Content-Signal: search=yes,ai-train=no,use=reference plus Disallow: / for Amazonbot,
Applebot-Extended, Bytespider, CCBot, ClaudeBot, CloudflareBrowserRenderingCrawler,
Google-Extended, GPTBot, meta-externalagent.

This repo's own robots.txt is a bare 3-liner with no AI policy, pointing at
gusdigitalsolutions.com/sitemap-index.xml. Publishing it as-is would destroy that policy — the
exact regression that hit appliedtoday.com. Capture robots.txt before the deploy and diff after.

Also note a catch-all 301 will redirect /robots.txt and /sitemap.xml too; decide deliberately
whether to exclude them in vercel.json.

---

Recommendation

Keep this issue open — the defect is real. But de-prioritize it until review resolves, and
when it is done, take Option A (it is already written; it needs a deploy, not a change).

Full runbook with the freeze baseline, robots diff step, and status-code proof:
/Users/gus/Desktop/Claudecode/state/herphase-asc-audit-20260807/DEPLOY-RUNBOOK-AFTER-REVIEW.md

Proof of the fix must be live status codes on all eight paths (expect 301 → 200), never a
deploy command exiting 0 — a prior appliedtoday.com session believed it had deployed, the command
exited 0, and the pages were still 404 four days later because it went to a preview branch.

_{Related: lightcloud00/herphase#34 (closed) — its "repo private / Pages disabled" root cause
is no longer true; the repo is public and Pages is built.}

[lightcloud00]

Marketing sweep status — 2026-08-11 — claude-code — session d5e1adea

Verdict: COMMENT-AND-KEEP. Confirmed still true, and it now blocks more than SEO.

Re-probed live just now:

$ curl -sSL https://herphase.app/ | grep -aioE '<title>[^<]*</title>|coming soon'
<title>HerPhase - Coming Soon</title>
Coming Soon

$ curl -sSL -o /dev/null -w '%{http_code}' https://herphase.app/llms.txt
404      (same-host control also 404 — genuine absence, not a soft-404)

$ dig +short NS herphase.app
ishaan.ns.cloudflare.com.  robin.ns.cloudflare.com.
$ dig +short A herphase.app
172.67.217.56  104.21.75.76

The domain is delegated and serving — it is serving the wrong thing.

Why this is now urgent rather than cosmetic: HerPhase is in App Review right now. Live ASC probe this session:

HerPhase   IAPs=0
   subscriptionGroups=1 subscriptions=3
     com.gusdigitalsolutions.herphase.sixmonth   MISSING_METADATA
     com.gusdigitalsolutions.herphase.annual     READY_TO_SUBMIT
     com.gusdigitalsolutions.herphase.monthly    READY_TO_SUBMIT

App Store Connect records HerPhase's support / privacy / terms URLs as 404, and the app registry flags that as a v1 blocker. A reviewer following those links lands on a Coming Soon page or a 404 — that is a Guideline 1.5 / 2.1 rejection surface, not just an SEO gap. Any campaign that drives traffic here also lands on the same page.

Single next action: decide the canonical host for HerPhase — either cut herphase.app over to the real content, or make gusdigitalsolutions.com/herphase/ canonical everywhere and repoint the ASC URLs at it. Note the second option is currently not viable as written: the GDS Astro repo has no herphase/ page directory, so that path has nothing to serve.

Downstream of this issue: gusdigitalsolutions#24 (missing llms.txt) lists swingiq.app; herphase.app has the same gap and is a symptom of this cutover never happening. Fixing this fixes that for free — sequence this one first.

Proof: Claudecode/state/marketing-sweep-20260811/SITE-PROBE-20260811.md and ASC-IAP-PROBE-20260811.md

_{Read-only sweep. No DNS, deploy, or ASC field was touched.}

[lightcloud00]

Tuesday, August 11, 2026 at 12:44 AM EDT — claude-code — session 1f143cd0

time_utc: 2026-08-11T04:44:19Z
surface: claude-code
session_id: 1f143cd0-a54c-4e22-bcb0-88e7cb2d3bf5

Endorsing the 301 — with one hard pre-check that must happen first

Re-probed live just now; the finding still stands unchanged:

https://herphase.app/                        200  <title>HerPhase - Coming Soon</title>
https://gusdigitalsolutions.com/herphase/    200  <title>HerPhase — Private Cycle and Energy Planner for iPhone</title>

A branded product domain is still serving a placeholder while the real site is live elsewhere.

I agree with the recommended option: 301 herphase.app → gusdigitalsolutions.com/herphase/

The reasoning in the body holds and I have nothing to add against it. The deciding factor is
asymmetric risk: the GDS copy is 17 routes that are hand-registered in astro.config.mjs
customPages and asserted by tests/verify-seo-aeo.mjs — it has a gate protecting it. The
herphase-pages copy is 3 blog posts in a repo with no .github/workflows/, so nothing
deploys it. Making the ungated, undeployed side canonical would be moving authority onto the
weaker of the two.

The alternative (deploy herphase-pages to its own domain and 301 GDS's routes to it) is the
better branding answer and worth revisiting after the app ships and there is traffic worth
branding. It is the wrong thing to do to an unreleased app with no existing domain authority.

The pre-check that must happen before anything is redirected

Read the live App Store Connect fields for HerPhase (app 6787806352) first — specifically
privacyPolicyUrl on appInfoLocalizations, and supportUrl / marketingUrl on
appStoreVersionLocalizations.

If any of them is registered against herphase.app, then the 301 changes what a reviewer lands
on, and the ASC fields must be updated in the same window. Apple follows redirects, so this is
unlikely to break review — but "unlikely" is not the standard for a legal URL on an app awaiting
review, and repo metadata goes stale while ASC is authoritative
(~/.claude/rules/legal-url-lookalike-domains.md).

Related and already tracked: lightcloud00/herphase#50 records the HerPhase legal-URL 404s as
an independent App Review blocker. These two should be resolved together — deciding the
canonical host and fixing the legal URLs are the same decision touching the same fields, and
doing them in separate passes risks setting ASC to a host that then changes.

Sequence, once you decide

1. Read the three live ASC URL fields; record what they currently point at.
2. Put the 301 in place (herphase.app → gusdigitalsolutions.com/herphase/), path-preserving,
   and add llms.txt.
3. Update any ASC field naming herphase.app to the canonical GDS URL.
4. Verify: herphase.app returns the intended status, no URL is 200 on both hosts, canonical
   tags agree, and only the winning host appears in a sitemap.

Still your call — both options change live public routing, and the body is right to say so.
Nothing here has been executed; this comment records a recommendation and a pre-check, not an
action.

No mutations performed; probes were read-only curl.

[lightcloud00]

Verified issue disposition — parked

This is the current managed disposition for lightcloud00/herphase-pages#12 at default-branch 47a1a6550d9c.

Current evidence

• Current stable snapshot for Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 at 47a1a6550d9c keeps the issue open with body hash 2863c62483d7; the validated grounded planner classified it as diagnostic_ready.

Files or owner actions

• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12, bind symbol ASC-IAP-PROBE-20260811.md to an existing source path before implementation.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12, bind symbol astro.config.mjs to an existing source path before implementation.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12, bind symbol robots.txt to an existing source path before implementation.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12, bind symbol vercel.json to an existing source path before implementation.

Bounded plan

• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: Treat each recorded child issue as the owner of its implementation and source-bound verification.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: Track the child proof targets and reconcile shared interfaces without duplicating their code changes here.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: Define aggregate closure criteria requiring every child to be resolved, superseded with evidence, or explicitly deferred by its owner.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: Prepare an umbrella-only status update after child receipts exist; do not close or mutate GitHub in this run.

Commands

• Run rg -n -F ASC-IAP-PROBE-20260811.md . for Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 and retain sanitized output.
• Run rg -n -F astro.config.mjs . for Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 and retain sanitized output.
• Run rg -n -F robots.txt . for Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 and retain sanitized output.
• Run rg -n -F vercel.json . for Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 and retain sanitized output.
• Run rg -n -F Canonicalize . for Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 and retain sanitized output.
• Run Record and run the repository-native focused check, then its broader regression gate for Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 and retain sanitized output.

Acceptance tests

• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Connect the owning Vercel project/account and confirm whether the owning Cloudflare zone is also required.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Capture the current managed robots policy before cutover.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Deploy a path-preserving permanent redirect for root, legal, support, blog, robots, and sitemap paths.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Prove every redirect terminates at a 200 GDS URL and a nonexistent control remains a genuine 404.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Prove one canonical family and one sitemap authority with no indexed duplicate host.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Link the exact deployment/readback receipt to lightcloud00/herphase#100 and the canonical Obsidian HerPhase state.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Connect the owning Vercel project/account and confirm whether the owning Cloudflare zone is also required.
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: [ ] Capture the current managed robots policy before cutover.

Risks

• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12, a false source binding could widen the change or invalidate this plan; Revert only the exact task-branch change after capturing source and runtime identity; never reset or restore an owner worktree.

Stop gates

• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: no issue close, reopen, body edit, pull-request, branch, or merge mutation while implementing this plan
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: the managed plan comment and disposition-specific readiness labels are the only authorized issue mutations in the planning lane
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: no push, protected-branch update, force-push, or merge
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: no deploy, upload, App Store Connect, TestFlight, or public release
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: no credential value disclosure, rotation, billing, or provider change
• For Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12: no owner-worktree restore, reset, checkout, process signal, or queue reorder

Why this is parked

• Grounded dependency analysis marks Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 duplicate or superseded by a named canonical successor, but closure proof is not yet sufficient.

Recheck condition

• Recheck Canonicalize CycleKeep on GDS and redirect legacy herphase.app #12 when a named canonical successor has an explicit same-defect comparison and current acceptance proof.

---

Ledger schema: aos.github-issue-plan-coverage.v1 · issue body: 2863c62483d7