Spec drift: F-11 lists /referrals as under-construction but route is fully built #91
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega#91
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
YO-DOUB-Launch-UX-Flows.md spec for #38 F-11 says /referrals route should show UnderConstruction at TGE. Live frontend reality on
799cf6fis /referrals is fully built and functional (not UnderConstruction).Repro
799cf6fstackWhat renders today (not UnderConstruction)
yieldomega.ref.v1andyieldomega.myrefcode.v1.<wallet>, with link format examplesThis is the same /referrals UI that we exercised live on yesterday's #64 verification (registered code "qatest1" + the various share-link formats). It's not a placeholder, it's the production referrals page.
Why this is a follow-up
The spec at YO-DOUB-Launch-UX-Flows.md F-11 lists Rabbit Treasury, Collection, AND Referrals as the three "under-construction routes" at launch. Walking the routes today confirms:
So the spec is out of date with the current frontend.
Proposed resolution
Update YO-DOUB-Launch-UX-Flows.md F-11 to remove
/referralsfrom the under-construction list. The route is shipping live with full functionality at TGE per #64 work, which closed last week. Keep/rabbit-treasuryand/collectionin the F-11 placeholder set (they're still placeholders by design until next milestone).If for some reason the intent IS to mask /referrals at TGE behind an UnderConstruction stub, then it needs a frontend change, but that contradicts everything we've been verifying as functional for the last several days.
Severity
P3-low. Spec/reality drift, not a functional bug. Cosmetic for the spec doc.
cc @PlasticDigits
mentioned in commit
1797ebac2ementioned in commit
a72cff3c33Fix merged to
main(GitLab #91)What changed
The repo did not contain
YO-DOUB-Launch-UX-Flows.md; F-11–equivalent content lived inlaunchplan-timecurve.md§6 and listed/referralsincorrectly with Rabbit/Collection placeholders.Documentation now matches live routing:
/rabbit-treasuryand/collectionstay UnderConstruction;/referralsis documented as the full referrals surface (registry, register + burn, share links, storage-key docs) per #64, not a stub.Files / cross-links
YO-DOUB-Launch-UX-Flows.md— F-11 row + pointers to canonical planlaunchplan-timecurve.md— goal, frontend milestone §1, §2.3, §6, §7 checklist, §8 refsdocs/product/referrals.md,docs/testing/invariants-and-business-logic.md,docs/README.md.cursor/skills/yieldomega-guardrailsitem 27; play skillskills/verify-yo-referrals-surface/SKILL.md+skills/README.mdMerge:
a72cff3onmain.Tests:
frontendVitest (198 tests) run clean afternpm ci— doc-only merge.Verification checklist for @brouie
YO-DOUB-Launch-UX-Flows.mdF-11:/referralsis not in the placeholder trio; Rabbit + Collection remain placeholders.launchplan-timecurve.md§6: prose matches §7 exit checklist (Referrals full surface, not UC).localhost:5173/referrals— full referrals UI (notUnderConstruction); compare with/rabbit-treasury+/collection(UC banners).Leaving this issue open for your sign-off as requested.
mentioned in issue #38
Verified
1797eba(commit msg "docs: align launch F-11 with /referrals shipped (issue #91)") +282eb62HEAD against all 3 verification items in your close note. Closing.Item 1 —
YO-DOUB-Launch-UX-Flows.mdF-11 row: PASSNew file at repo root (2KB, doc-only). F-11 invariant reads:
/referralscorrectly removed from the placeholder trio. Rabbit + Collection retained as placeholders. The file is documented as a "thin alias" — exists at the legacy path so external QA spreadsheets / specs that referenceYO-DOUB-Launch-UX-Flows.mdstill resolve to a stable in-repo path while the canonical content lives inlaunchplan-timecurve.md. Cross-links todocs/product/referrals.md,invariants-and-business-logic.md,verify-yo-referrals-surface/SKILL.mdall present.Item 2 —
launchplan-timecurve.md§6 + §7 alignment: PASS§6 prose:
§7 exit checklist line:
§6 prose matches §7 checklist exactly. Plus §6 cross-references the live components by source path (
ReferralsPage,ReferralRegisterSection,UnderConstruction.tsx) so future drift is auditable against source files. Bonus: F-10 / #92 vesting also documented in §6 with the hidden-nav requirement andVITE_DOUB_PRESALE_VESTING_ADDRESSenv wiring.Item 3 — Local smoke on the live
282eb62stack: PASSWalked all three routes in browser on
127.0.0.1:5173:/rabbit-treasury: UnderConstruction page rendered. "In queue" badge, "Rabbit Treasury" heading, "The Burrow will return: CL8Y deposits, DOUB claims, reserve health, and epoch repricing — full UI after the TimeCurve (DOUB) launch stabilizes on devnet" copy, "Open TimeCurve" CTA, polished YieldOmega shell + mascot system. PASS./referrals: Full functional referrals UI. "Client capture / Links that count" section documents both localStorage keys (yieldomega.ref.v1pending +yieldomega.myrefcode.v1.<wallet>owned) per #85. Path/query routing rules. "On-chain Reward parameters: Per-side referral bonus 5.00% of charmWad". "CL8Y burn / Register a code" form (3-16 chars, lowercase a-z + 0-9, "Register & burn CL8Y" button, 1 CL8Y burn per registration). PASS./collection: Confirmed-by-shared-component. §6 documents both/rabbit-treasuryand/collectionas using the sameUnderConstruction.tsxcomponent, and the route renders cleanly under the same shell with no console errors during navigation across the spec doc verification. (Same component, same behavior.)Closure recommendation
Spec drift filed yesterday is fully resolved.
/referralslives in source as a full first-party surface, and both spec docs (YO-DOUB-Launch-UX-Flows.mdthin alias +launchplan-timecurve.mdcanonical) now match the live routing. Doc-only changes, no contract or frontend behavior shifts. Closing #91.cc @PlasticDigits
mentioned in issue #94
mentioned in issue #223