Platform Updates

Repository: rego.furries.ph-v2. Status: Local verification, not released.

The combined frontend changes passed twelve controlled workflow regression suites. Local authenticated route checks now use a tested write guard so viewing test pages cannot submit business changes. After restoring the local API, 76 desktop/mobile route and detail checks passed. An additional source comparison verified 1,170 question-branch cases and 130 branch paths against V1.

These checks do not certify real payment completion, reservation concurrency or a hosted release. Event operators need take no action; backend integration and release checks remain outstanding.

Repository: social.furries.ph. Status: Local implementation, not released.

What’s Changed: Added coordinate conversion for recent UWB directions using native fused device-orientation inputs, with stale/uncertain-reading safeguards.

Impact: This is shared calculation code, not an active sensor or tracking feature. Native integration and real-device accuracy validation remain open.

Upgrade Notes: No action required. No new location or camera permissions.

Validation: Typecheck, 246 tests and production web build pass locally; hardware sensor fusion and precision remain unverified.

Repository: social.furries.ph; future dynamic work owned by partners-api. Status: Implementation started locally; not released.

What’s Changed: Recorded an opt-in friend map and GPS meetup-compass plan with followers, mutuals, or selected-person audiences, time limits, revocation, and free-plan traffic safeguards. Capacitor is selected for the planned mobile app, reusing the React UI with native precision-finding plugins. UWB remains hardware-gated and requires real-device validation, not just a browser build.

Impact: No location is collected or shared by this planning change.

The initial Capacitor Android/iOS projects and shared GPS estimate math now exist locally. They do not yet provide map sharing or UWB tracking. Native authentication, permissions, ranging plugins and real-device testing remain required before a mobile release.

Validation: Local typecheck, 236 tests, production web build and native asset sync pass. This is not native compilation, store release or UWB accuracy certification; no location data was collected for these checks.

Upgrade Notes: No action required. Implementation requires privacy, map-provider, capacity and device validation; current source evidence is research/task documentation only, not a runtime certification.

UI follow-up: The local preview now uses a Bluesky-inspired, search-first central column with compact profile rows, inline deliberate Follow actions, persistent desktop navigation, and mobile bottom navigation. Furries PH colors and light/dark preferences are retained; no new backend requests occur merely from typing or clearing search text. This refinement remains a local preview.

Repositories: social.furries.ph, partners-api

Status: Locally verified; not deployed.

What’s Changed

• A dedicated /discover page brings together People/user search, community Pages, private Friends, and Events. Home links to this page; old /events addresses redirect to its Events category.
• Search submits deliberately instead of sending requests as members type. Friend filtering stays within the current private snapshot. Public Page search returns at most 25 active summaries without private membership data.
• Existing Furries PH colors and a four-category mobile layout are retained.

Impact

Members will have one place to find people and community activity after release. No friendship, attendance, registration, verification, or follow consent changes. Social remains a static Pages SPA using the existing API Worker.

Upgrade Notes

Social typecheck, 195 tests, production build, and dedicated desktop/mobile browser fixtures pass. Isolated Page-search handler tests pass. The API’s pre-existing main-branch integration and baseline typecheck failures must be resolved before the API addition and Git-connected Pages release. These results are local evidence, not confirmation of a production rollout.

Repositories: partners.furries.ph-v2

Status: Local implementation and controlled preview verification; not deployed.

What’s Changed

• Roster timelines separate overlapping shifts and align time markers, slots and assignments. Availability recommendations include usable free segments.
• Volunteer and submission forms share ordered cards and choice-image controls.
• Rego’s actual Role, Questions, Conditions and Review components now power the unsaved volunteer application preview, including rich Markdown, branching, document acceptance and local failure/retry. Preview receipts clearly state that no application was sent.
• The canvas includes the actual roster editor and volunteer form builder with local records, draft recovery and simulated failures. Images selected in these and existing form-builder previews stay in browser memory.

Impact

Event teams can inspect authoring workflows without changing event records. Full attendee application parity remains under audit; this does not replace V1.

Upgrade Notes

No production changes, migrations or API source changes from this work. Type-checking, production build and shared auth-source checks passed. Controlled canvas checks covered roster geometry and interactions plus volunteer builder duplication, ordering, image recovery, draft retention and mobile layout without API requests. Seven additional volunteer journey check groups passed without API requests or real writes. Accurate iframe viewport and nested-dialog checks, remaining page parity and production-provider evidence are separate requirements in the task ledgers; no live release is implied.

Repositories: rego.furries.ph-v2

Status: Local implementation and controlled verification; not deployed.

What’s Changed

• Zero-total regos skip payment; failed or superseded quotes cannot advance checkout. Free-event and absorbed-fee summaries follow the existing source behavior.
• Group drafts recover after failed reads, preserve member choices and failed invitations, and show per-attendee discounts and fees. Mobile search fields, progress and review spacing are corrected through reusable components.
• Shop validates current item questions, filters couriers by country and isolates carts across account changes. Dealers Den revisions retain payment evidence and reset correctly between forms.
• Fursona reference uploads restore the source’s 20 MB limit. Failed account preference and reference changes show error feedback instead of success styling.
• Waitlist forms no longer block on hidden rego-only questions. Offer buttons sit above their backdrop, expired holds recover correctly, and late hold responses cannot reopen a disabled reservation state.
• Group add-on sizes are cleared with removed or ineligible choices. Historical refunds/transfers restore source details and recorded-price estimates; the same upgrade receipt can be retried after an upload failure.

Impact

Controlled browser tests cover five account groups, eight added order variants, six existing order groups, and individual/group rego completion and recovery. Requests are intercepted; these checks do not claim actual payment settlement, uploaded-asset storage or live account mutations.

Follow-up browser checks also pass for waitlist join/offer/expiry/hold recovery, nonempty group add-on lifecycles and six historical transaction/retry scenarios. Returned-offer reservation ownership, real provider state and concurrency remain separate gates.

V2 also follows the latest V1 five-minute notice polling cadence while retaining immediate refresh on focus. The local shell regression passes; this reduces repeated reads without changing acknowledgement requirements.

Additional controlled checks cover account switching without stale drafts/offers, isolated reservation tokens, and gifted/saved add-on restoration. Gift recipients can choose required clothing sizes without changing the paid package; review explicitly shows zero due. Eight account-transition and seven gift scenarios plus standard/waitlist regressions pass locally. Existing API reservation ownership and final-slot handling still need separately authorized backend work before complete end-to-end certification.

The account/route suite now has ten passing cases: switching events discards delayed responses from the previous event, and switching form modes resets the draft without resetting it for an in-page anchor. This remains locally verified and not deployed.

The shared page boundary now resets account-owned content when a different attendee signs in, verified with Friends data and an open removal confirmation. Authentication callbacks remain uninterrupted and verify once. Eleven identity/route cases and nine account regression checks pass locally; no real removal or block was submitted.

Upgrade Notes

No live-site action is required yet. V1 and Partners API were not changed. The V2 source-parity report records remaining waitlist, concurrency, provider/device and release checks. Full parity and deployment remain open.

Final typecheck, normal public-catalog build, route/component inventory, extended Markdown, metadata safety and source-drift checks pass. Existing bundle-size/import/timing warnings remain non-blocking.

Repositories: partners.furries.ph-v2

Status: Local implementation and controlled browser verification; not deployed.

What’s Changed

• Roster overnight windows use the existing API contract and local-time fields preserve wall-clock values. Confirmed saves retain drafts after failures.
• Volunteer position imports preserve department-only changes; review errors remain visible inside dialogs. Switching events ignores delayed imports and save responses and stops unsent bulk reviews.
• The design canvas now runs the real read-only live-shift component with published, draft, empty, loading and failure scenarios. Failed refreshes retain coverage with a stale-data warning instead of claiming current data.
• A fresh source audit reopened remaining scheduler and volunteer-builder gaps.

Impact

Event operators can rehearse coverage states without modifying event records. Desktop/mobile preview checks made zero API requests; roster browser checks used intercepted writes only. Full V1 parity and production persistence remain unproven.

Upgrade Notes

No API changes or migrations. Preview locally; no production action is required. Validation includes passing typecheck/build, HR contracts and desktop/mobile controlled browser scenarios. Large-bundle build warnings remain.

Repositories: partners.furries.ph-v2

Status: Local implementation and browser verification; not deployed.

What’s Changed

• The design canvas now runs the full HR editor with local sample records: event policies, subsidies, dates, locations, departments and members, independent imports, Save/Revert and a simulated failure/retry flow.
• Dashboard and preview share confirmed draft actions. Newly added departments open expanded and ready for a name.
• HR saves exclude roster publication/order and account-display metadata, preserving the V1 form’s write boundary.

Impact

Operators can cancel Save or Revert without changing the draft. A failed save keeps edits. Preview interactions do not call the API or store records in the browser.

Upgrade Notes

No API/schema changes or live-site action is required. Typecheck, build, HR contracts and shared-source checks passed. Browser checks cover mobile and desktop, authenticated reads and intercepted save requests; no real HR records were changed. Production deployment and real persistence remain separate verification gates.

Repositories: partners.furries.ph-v2

Status: Local implementation and browser verification; not deployed.

What’s Changed

• Independent settings/department imports and shared collapsed editors restore roles, account portraits, duplicate checks and subsidy/window overrides.
• Failed saves retain edits. Delayed responses cannot replace another event’s draft; Revert remains explicit.

Impact

• Operators review imports before saving. Disabling an override clears its paired fields and restores inherited policy.

Upgrade Notes

• No API/schema changes. Typecheck, build and HR contracts passed. Browser checks covered desktop/mobile drafts, authorized reads and controlled save/search responses. No real HR records were changed.

Repositories: rego.furries.ph-v2

Status: Local implementation and verification; not deployed.

What’s Changed

• Corrected email confirmation and legacy rego links, pending authenticator setup, profile-save recovery, and optional social/Friends failures.
• Improved shared dynamic questions, document acceptance, extended-Markdown notices, price concealment and session-refresh/account-switch handling.
• Restored source-equivalent eligibility, item questions, upgrade and group pricing, gift fee breakdowns, Dealers Den behavior and authorized vollie shift actions. Completed transaction actions cannot be resubmitted from stale review screens.
• Restored event share metadata and branded fallback preview cards as static build output, with no runtime SSR or API proxy. Builds stop if the public catalog cannot be read; rebuild after event content changes to refresh previews.

Impact

These repairs target missing or inconsistent attendee behavior found by comparing the V1 working tree with native V2 features. Browser fixtures exercise real React screens with synthetic API responses; real-local auto-login and read-only route smoke checks are separate evidence. They do not certify live payment settlement or provider ceremonies.

Upgrade Notes

No action is required on the live site yet. V1, the Partner Dashboard repository and Partners API were not changed by this audit. Safe backend mutation fixtures, provider checks and a new production deployment must be verified before full-parity or cutover claims. The V2 repository’s September 9 audit records reproducible checks and remaining gates.