Opportunities pages - Platform release 2 September 2026

.circleci/config.yml

@@ -108,6 +108,9 @@ deploy_steps: &deploy_steps
               ./psvar-processor.sh -t appenv -p /config/${APPNAME}/deployvar
               source deployvar_env
               ./master_deploy.sh -d CFRONT -e $DEPLOY_ENV -c $ENABLE_CACHE
+              # Switch the uncached Gigs shell only after all referenced assets are deployed.
+              aws s3 cp "${AWS_S3_SOURCE_SYNC_PATH%/}/index.html" "s3://${AWS_S3_BUCKET%/}/gigs/index.html" \
+                --content-type text/html --cache-control 'no-cache,no-store,max-age=0'
 
 jobs:
     lint-dev:
@@ -229,8 +232,8 @@ workflows:
                           only:
                               - dev
                               - copilot_reviewer
-                              - support-app
                               - PM-5460
+                              - aws_analytics
                       tags:
                           only: /^dev-.*/
 

.environments/.env.dev

@@ -1,5 +1,10 @@
 REACT_APP_HOST_ENV=dev
 
+# First-party AWS Clickstream analytics
+REACT_APP_ANALYTICS_API_URL=https://api.topcoder-dev.com/v1/analytics
+REACT_APP_AWS_ANALYTICS_APP_ID=topcoder_web
+REACT_APP_AWS_ANALYTICS_ENDPOINT=https://events.topcoder-dev.com/collect
+
 REACT_APP_ENABLE_TCA_CERT_MONETIZATION=false
 
 # Stripe configs
@@ -11,8 +16,6 @@ REACT_APP_DATADOG_PUBLIC_TOKEN=puba0825671e469d16f940c5a30dc738f11
 
 REACT_APP_MEMBER_VERIFY_LOOKER=3322
 
-REACT_APP_SPRIG_ENV_ID=bUcousVQ0-yF
-
 # Filestack configuration for uploading Submissions
 REACT_APP_FILESTACK_API_KEY='AzFINuQoqTmqw0QEoaw9az'
 REACT_APP_FILESTACK_REGION='us-east-1'

.environments/.env.prod

@@ -1,5 +1,10 @@
 REACT_APP_HOST_ENV=prod
 
+# First-party AWS Clickstream analytics
+REACT_APP_ANALYTICS_API_URL=
+REACT_APP_AWS_ANALYTICS_APP_ID=
+REACT_APP_AWS_ANALYTICS_ENDPOINT=
+
 REACT_APP_ENABLE_TCA_CERT_MONETIZATION=false
 
 # Stripe configs
@@ -11,8 +16,6 @@ REACT_APP_DATADOG_PUBLIC_TOKEN=puba0825671e469d16f940c5a30dc738f11
 
 REACT_APP_MEMBER_VERIFY_LOOKER=3322
 
-REACT_APP_SPRIG_ENV_ID=a-IZBZ6-r7bU
-
 # Filestack configuration for uploading Submissions
 REACT_APP_FILESTACK_API_KEY='AzFINuQoqTmqw0QEoaw9az'
 REACT_APP_FILESTACK_REGION=us-east-1

.environments/.env.qa

@@ -1,5 +1,10 @@
 REACT_APP_HOST_ENV=qa
 
+# First-party AWS Clickstream analytics
+REACT_APP_ANALYTICS_API_URL=
+REACT_APP_AWS_ANALYTICS_APP_ID=
+REACT_APP_AWS_ANALYTICS_ENDPOINT=
+
 REACT_APP_ENABLE_TCA_CERT_MONETIZATION=false
 
 # Stripe configs
@@ -11,8 +16,6 @@ REACT_APP_DATADOG_PUBLIC_TOKEN=puba0825671e469d16f940c5a30dc738f11
 
 REACT_APP_MEMBER_VERIFY_LOOKER=3322
 
-REACT_APP_SPRIG_ENV_ID=bUcousVQ0-yF
-
 # Filestack configuration for uploading Submissions
 REACT_APP_FILESTACK_API_KEY=
 REACT_APP_FILESTACK_REGION=

.gitignore

@@ -27,3 +27,7 @@ yarn-debug.log*
 yarn-error.log*
 
 storybook-static
+
+# Python build artifacts
+__pycache__/
+*.py[cod]

docs/PM-6100-footer-verification.md

@@ -0,0 +1,49 @@
+# PM-6100: universal navigation footer colors
+
+Verified against `dev` at `9d879b43d` on 2026-09-13.
+
+The reported green footer links are already corrected in this revision. The
+ticket screenshot shows `/challenges` in the Work app. Both Work and Opportunities
+load the shared 2026 foundations, so the investigation covers both layouts.
+
+## Cause and existing fixes
+
+The 2026 foundations originally applied `body.work-app a { color: #00797a; }`.
+Because the universal footer is also inside `body`, that rule overrode the white
+color inherited from the footer navigation sections.
+
+- `cb108c147a` (2026-09-09, PM-6091) added the scoped
+  `#footer-nav-el a:not([class*='cta'])` override for normal, hover, and keyboard
+  focus states. It leaves the white CTA's dark text intact.
+- `9321313974` (2026-08-15) placed Opportunities' theme on its content wrapper,
+  `.opportunities-app.tc-2026`, and changed its body marker to
+  `opportunities-page`. `AppFooter` is a sibling of the platform route container,
+  so Opportunities' teal anchor default cannot select footer links.
+- The explicit theme allowlist remains scoped when its stylesheet persists
+  during client-side navigation. Removing only an import would not be sufficient.
+
+No additional CSS override is needed on current `dev`.
+
+## Verification
+
+An isolated Chromium fixture compiled the actual shared reset, 2026 foundation,
+and installed universal-navigation footer Sass. It retained the content/footer
+sibling layout and the footer component's selectors. Checks at 1440 px and
+390 px widths covered normal, hover, and focus states while changing the body
+class from Opportunities to Work and back. All 18 checks passed:
+
+| Element | Computed color |
+| --- | --- |
+| Opportunity content link | `rgb(0, 121, 122)` |
+| Footer navigation link | `rgb(255, 255, 255)` |
+| Footer CTA text | `rgb(11, 61, 86)` |
+
+`yarn lint` and `NODE_OPTIONS=--max-old-space-size=16384 yarn run build`
+also passed under Node 22.13.0. The initial build exhausted Node's default heap;
+the larger heap completed the unchanged production build.
+
+This verifies the CSS cascade and app scoping; it is not a live deployment test.
+For release QA, open Work's challenge listing and Opportunities at desktop and
+mobile widths, hover and keyboard-focus footer links, then navigate between the
+apps without reloading. Footer links should remain white, content links teal,
+and the "Talk to an expert" CTA should retain readable dark text.

docs/PM-6285-waitlist-verification.md

@@ -0,0 +1,42 @@
+# PM-6285: review waitlist and badge verification
+
+Verified platform-ui `origin/dev` at `9d879b43d` and review-api-v6
+`origin/develop` at `41d6853`. The ticket's changes are already present: platform
+commit `5aed5245b` (merged PR #2255) added the waitlist clock and corrected track
+colors. Later QA copy changes retain the capacity and status behavior. This new
+PR records verification without duplicating the existing implementation.
+
+## Coverage
+
+| Requirement | Current implementation |
+| --- | --- |
+| Full opportunity can accept a waitlist application | Eligible reviewers receive `canApply: true`; the POST persists `PENDING` even when approved reviewers fill capacity. |
+| Capacity excludes pending applications | Review API reports approved count and clamps remaining positions at zero on both list and detail responses. |
+| Waitlisted status | Caller-owned `PENDING` plus zero remaining positions becomes `Waitlisted` in Browse, My Work, and the detail CTA. An explicit future `WAITLISTED` status is also understood. |
+| Later application decisions | Approval and rejection keep their distinct statuses. If capacity reopens, a pending application's derived label returns to `Applied`. |
+| Clear application flow | The full-capacity CTA reads “Apply to be a reviewer (waitlist)” and explains Support's replacement-reviewer process before and after submission. |
+| Eligibility remains enforced | Closed/expired opportunities, inactive/inaccessible challenges, invalid roles, and duplicate applications remain rejected. The unique database key also prevents concurrent duplicates. |
+| Waitlist administration | Existing approval/rejection endpoints operate on pending applications. Approval creates the reviewer resource, publishes its event, and sends the notification. Selection remains manual. |
+| Status appearance | Open is neutral; Applied/Waitlisted use green outlines with check/clock icons; Approved uses the solid green accepted style; Rejected uses red and an X. |
+| Track backgrounds | Design `#d0e2ff`, Development `#a7f0ba`, AI `#e8daff`, Data Science `#ffd9be`, consistently selected through the shared track class mapping. |
+
+The backend intentionally has no persisted `WAITLISTED` enum: pending
+applications are the waitlist, and live approved capacity determines the label.
+An old API response explicitly denying capacity remains disabled, because that
+server cannot honor a waitlist POST. The deployed API and UI must both contain
+the already-merged contract.
+
+## Validation
+
+- 57 frontend tests pass across review opportunity utilities, cards, My Work,
+  and details, including full-capacity submission, disabled legacy responses,
+  caller waitlist state, and track class mapping.
+- 31 backend tests pass across opportunity service, application service, and
+  application controller, including aggregated capacity, lifecycle/privacy,
+  full-capacity pending creation, and concurrent duplicate rejection.
+- 18 Chromium checks of the compiled repository Sass pass at 1440px and 390px,
+  covering the five status appearances and four requested track backgrounds.
+
+The browser checks use a reduced fixture with the actual stylesheet and waitlist
+SVG; they are not a live authenticated application test. The verification found
+no additional runtime change required by PM-6285.