[STAGING, PLEASE IGNORE] feat: move Outpost Ticket to a dedicated Outpost shop category#550
Draft
qcoral wants to merge 4 commits into
Draft
[STAGING, PLEASE IGNORE] feat: move Outpost Ticket to a dedicated Outpost shop category#550qcoral wants to merge 4 commits into
qcoral wants to merge 4 commits into
Conversation
Add an "outpost" shop category and assign the Outpost Ticket to it instead of "hardware". The category is assigned (not appended) so re-seeding moves the ticket out of its previous category. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
qcoral
changed the title
…d-dollar The Outpost Ticket discount is now a flat percentage of the ticket price set by the approved funding tier (B 30% / A 50% / S & X 100%), accrued cumulatively on approval, replacing the "2 Stardust per unrequested dollar" logic. Overflow past the ticket price still becomes a flight stipend. - funding_request: tier discount_percent, TIER_DISCOUNT_PERCENT, tier_discount_stardust, and a tier_discount_summary for the modal; accrual now awards the flat tier amount. - Update all user-facing copy that described the per-dollar mechanic: funding modal preview + JS, tiers guide, admin reviewer hint, shop order summary, and the Outpost Ticket seed description. - Update existing discount tests to the flat per-tier amounts. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Keep tests out of the PR per request; the discount logic/copy change remains. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The accrual is now a flat per-tier discount (S = 100% of the 300✦ base), so all three tier-3 cases yield 300 regardless of approved amount. Also retitled the "approve for less" test, which now verifies the discount is unchanged by the approved amount rather than increased by it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds an Outpost shop category and moves the Outpost Ticket into it, instead of living under Hardware.
Changes
db/seeds.rb— newoutpostshop category (slug: "outpost", "Outpost Shop", hub title "Outpost", position 5), alongside the existing grants/hardware/digital/merch/games categories.db/seeds/outpost_ticket.rb— assigns the ticket to theoutpostcategory instead ofhardware. Usesshop_categories = [...](replace, not append) so a re-seed moves the ticket out of any prior category rather than leaving it in both. Thehqsource assignment is unchanged.Notes
=assignment is idempotent and self-correcting: on the next seed run, any already-seeded ticket inhardwareis moved tooutpost. No data migration needed.hardwarecategory slug, so nothing else needed updating. (The separateexperiences-category teaser card incategory.html.erbis unrelated and left as-is.)["outpost"]only, withhardwaredetached and thehqsource intact.🤖 Generated with Claude Code