Platform Updates

Repository: partners.furries.ph

Status: Ready for deployment

What’s Changed

• Rego and Dealers Den form configuration now lists every standard question, including questions currently disabled or only shown conditionally.
• Each card explains whether it is in use, required, optional, conditional, or not in use, and provides a direct action to enable, disable, or edit its related configuration where available.
• Standard Activity and Volunteer questions continue to use the shared editable form builder.
• Form-builder questions and sections now begin collapsed with their prompt, answer type, and required state visible in the header; expanded editors retain clearer spacing between individual cards.

Impact

Partners can inspect the complete attendee-facing form without guessing which default fields are hidden by current event settings.

Repositories: partners.furries.ph, partners-api, rego.furries.ph

Status: Ready for deployment

What’s Changed

• Added an optional full Markdown description to every shared custom question while retaining compatibility with existing question help text.
• Improved form-builder hierarchy with visible question and section numbering, stronger prompt typography, and compact icon actions.
• Rendered question descriptions through the sanitized extended Markdown pipeline in registration, Event Shop, Dealers Den, volunteer applications, and organizer answer-review views.

Impact

Event organizers can add formatted instructions, links, lists, tables, and other contextual content directly beneath a question without making the compact builder harder to scan.

Upgrade Notes

• Deploy partners-api, partners.furries.ph, and rego.furries.ph; no database migration is required because question schemas remain JSON-backed.
• Dashboard Astro diagnostics and API TypeScript checks pass. The regosite repository still has unrelated existing diagnostics outside these question-description changes.

Repository: partners.furries.ph

Status: Ready for deployment

What’s Changed

• Moved the registration flow preview directly below the Rego form builder, where operators can check the questions they just configured.
• Moved shared attendee workflow preview cards below their own Dealers Den, Shop, Volunteer, Waitlist, and Activity configuration blocks instead of placing them above the page’s primary controls.
• Kept current unsaved-value previews, workflow selection, device controls, and non-submitting preview behavior unchanged.

Impact

Event operators now encounter preview actions at the point they finish configuring a form, while the top of each page stays focused on its primary settings and content.

Upgrade Notes

• Deploy partners.furries.ph; no API or database migration is required.
• The 113-page production build passes. Astro diagnostics report one unrelated existing FieldRow prop error in the shared form-builder template.

Repositories: fph-lan-ems, partners-api

Status: Ready for deployment

What’s Changed

• Added a dedicated Walk-in Rego page for authenticated LAN staff, including assisted registration, a searchable pending queue, editing, non-destructive voiding, and kiosk access controls.
• Added a responsive self-service kiosk wizard protected by a rotatable event link. Kiosks can submit only to that event and cannot list other attendees or local filings.
• Self-service kiosk pages and APIs now require a signed-in EMS LAN admin or operator account in addition to the event kiosk key. The kiosk header identifies the unlocking account and provides a lock action.
• Walk-in queue rows and the dedicated activity log identify the signed-in staff account responsible for assisted filings; audit entries retain the account ID and an identity snapshot for later review.
• Self-service digital payments now require a provider reference number and a receipt photo. The kiosk checks resolution, lighting, and focus, rejects blurry evidence with a retake prompt, and the LAN server independently verifies the image before saving it.
• Cash is unavailable on self-service kiosks by default. Staff can use an audited event-level override when needed; staff-assisted registration continues to support configured cash payments.
• Accepted receipt images remain durable in local SQLite, are included in the LAN result export, and become the online registration’s payment proof during reconciliation.
• Refined both walk-in modes with a connected progress rail, clearer account choices, grouped profile and event fields, a denser staff queue workspace, and touch-friendly mobile controls.
• Fresh offline snapshots now carry the active event registration tiers, add-ons, sizes, default and custom questions, assigned conditions, payment destinations, fees, and current tier counts.
• Attendees can claim an existing Furries PH username/email without copying the platform attendee directory onto the LAN. New attendees complete the required profile and event registration fields offline.
• Result imports resolve account claims privately, create unlinked profiles for new attendees, recheck capacity and requirements, recalculate current totals, and generate the normal event-prefixed registration reference.
• Repeated imports are idempotent by LAN filing ID. Invalid or changed data becomes a visible conflict instead of creating a duplicate or mispriced registration.

Impact

Event teams can register walk-ins during an internet outage from either a staffed desk or attendee-facing kiosk while keeping account data private and online registrations authoritative after reconciliation.

Upgrade Notes

• Deploy partners-api, then export and import a fresh event snapshot before enabling onsite walk-ins.
• Rotate the kiosk link whenever a device or displayed link should lose access; the full key is shown only when generated.
• Leave the self-service cash override off unless the kiosk is being supervised for cash handling.
• LAN Astro diagnostics, the TASK020 runtime/contract certification, API TypeScript, and desktop/mobile browser checks pass without relevant console errors.

Repository: rego.furries.ph

Status: Ready for deployment

What’s Changed

• Standardized attendee-facing submission workflows on the same compact, multi-step layout used by event registration.
• Extended that same form system across Regosite auth, account/profile/communications settings, Friends search, Pawsport enrollment and lost reporting, affiliate payout setup, volunteer questions, and dynamically rendered transaction forms.
• Profile editing now follows an Identity, Address, and Review wizard; compact one-action forms retain a single step while sharing registration fields, cards, spacing, actions, and mobile behavior.
• Profile setup now guides attendees through Identity, Address, Security, and Review, validating each section before continuing.
• Activity forms now separate Questions, Conditions of Entry, and Review while preserving conditional custom questions and uploaded answers.
• Live refund, transfer, and upgrade pages now separate selection, account/payment details, and review, keeping final submission on the last step.
• Dealers Den application now uses Representative, Dealer Details, Products, Terms & Payment, and Review; Dealers Den registration uses Package, Attendees, Rego Options, Payment, and Review.
• Gift a Rego now uses Receiver, Rego Tier, Add-ons, Payment, and Review; Event Shop checkout uses Cart, Your Details, Fulfillment, Payment, and Review; Volunteer uses Position, Questions, Conditions, and Review.
• Dashboard previews for gift, refund, transfer, upgrade, waitlist, shop, volunteer, activity, and both Dealers Den workflows derive their progress steps from those real attendee sections instead of presenting one long Details page.

Impact

Attendees get one predictable form pattern across regosite instead of switching between long single-page forms and registration wizards. Account sign-in and compact settings controls remain intentionally task-specific.

Upgrade Notes

• Deploy rego.furries.ph; no database or API migration is required.
• The 109-page production build passes. Browser QA exercised every preview page through Review at 1180 px and the Gift flow at 390 px with one visible page at a time and no horizontal overflow. Local preview runs only report expected API/auth fetch failures because the test harness does not start the Worker API.

Repositories: fph-lan-ems, partners-api, partners.furries.ph, rego.furries.ph

Status: Ready for deployment

What’s Changed

• Updated the Android startup contract so both Online Dashboard and Local EMS LAN must identify as native contract version 2 or newer before the app opens them.
• Refreshed the embedded online dashboard and regosite compatibility mirrors to include current accounting, forecasting, Pawsport, shop, configurable-form, and other post-July routes.
• Synchronized backend SPA scene coverage for dashboard form previews plus the current forecasting and prefill event-management pages.
• Expanded LAN snapshots to carry account-bound Pawsport identity/status, registration and shop answers, size selections, event check-in/POS settings, and full payment-provider/account metadata.
• LAN POS now uses the event’s imported payment destination, instructions, platform fee tiers, provider fees, surcharge policy, and optional cash rounding. Older snapshots retain safe cash/manual fallbacks.
• LAN check-in can search account-bound Pawsports by document number or NFC UID and displays current Pawsport status, expiry/missing state, and submitted registration answers.

Impact

Event teams can use the current Android app and LAN server without silently losing newer identity, form, shop, or money-routing configuration introduced after 24 July 2026.

Upgrade Notes

• Deploy the dashboard contract and API snapshot changes before distributing the updated Android build.
• Export a fresh event snapshot after changing payment accounts, fees, Pawsport bindings, registration questions, or shop configuration.
• Compatibility, dual-mode Android, shop-order, SPA contract, TypeScript, Astro, Capacitor sync, and debug APK assembly checks pass. The broader hosted-runtime pass completed, while its optional emulator phase timed out waiting for the local AVD to boot.

Repositories: partners.furries.ph, partners-api

Status: Database migrations published; application changes ready for deployment

What’s Changed

• Replaced the deduction-only Accounting screen with a full event cash ledger covering confirmed registrations, gifts, Dealers Den, POS, paid shop orders, completed upgrades, approved refunds, platform settlements, and manual movements.
• Pending or merely submitted activity is excluded from money totals. Receiving-account and unallocated balances now reconcile from the same ledger entries.
• Partners can record manual income or expenses, attach evidence, add invoice, TIN, address, VAT, withholding, account-code, and internal-note details, and correct manual entries without erasing history.
• Required fields are visibly marked. Purchases from informal sellers can use an Informal purchase record with optional TIN, registered address, and document number while retaining the seller name and available supporting evidence.
• Every manual reference includes the event prefix and records its signed-in author plus filing date and time.
• Added a complete ledger CSV export and document-review flags. Gross values are VAT-inclusive, so VAT is reported as a component instead of being added twice.
• Automatic source snapshots and editable annotations are RLS-enabled, service-owned, and unavailable through browser database roles.

Impact

Event partners can follow all operational cash movements, reconcile receiving accounts, and prepare a complete document review trail from one responsive workspace.

Upgrade Notes

• Migrations 20260812120000_event_accounting_ledger_bir_fields.sql and 20260812130000_accounting_manual_tax_annotations.sql are published.
• Deploy both partners-api and partners.furries.ph to expose the new ledger and interface.
• API TypeScript and the dashboard production build pass. Repository-wide checks retain unrelated existing route-manifest gaps plus two nullable-array errors in the configurable form builder; neither affects the Accounting implementation.

Repositories: partners.furries.ph, partners-api

Status: Ready for deployment

What’s Changed

• Registration, cash-flow, and production forecasts now live together on one Event Management Forecasting page.
• A shared horizon rail covers the next 4 weeks, next 30 days, next quarter, and event day. Operators can switch every outlook between weekly and monthly values.
• Registration graphs show expected cumulative attendance with 80% and 95% ranges. Cash-flow graphs separate expected registration receipts, recorded scheduled inflows/outflows, and cumulative ledger-derived cash position. Production tables show period demand, stock targets, shortfalls, and at-risk item ranges.
• The page adds responsive trajectory graphs, downside/base/upside cash-position scenarios, operational facts, and detailed tier/payment/item disclosures.
• The consolidated outlook refreshes all three domains together every 15 seconds while visible and keeps early-evidence warnings, exact as-of times, and limitations close to the charts.
• Rego Analytics, Finance Analytics, and Inventory Analytics remain available for authoritative operational facts without duplicated forecast panels.

Impact

Event organizers can pace sales, cash availability, and convention production across practical planning windows while keeping forecasts visibly separate from actual registrations, ledger entries, and inventory records. Unrecorded future costs, provider payout timing, supplier lead-time uncertainty, and future walk-up/shop revenue remain explicitly excluded rather than guessed.

Upgrade Notes

• No migration is required; deploy both application repositories for the event-forecast-v2 response and dashboard together.
• Focused API and dashboard forecasting certifications cover multi-horizon reconciliation, cash scenarios, production outlooks, and the consolidated UI. Repository-wide Astro diagnostics retain two unrelated nullable-array errors in the configurable form builder.

Repositories: partners.furries.ph, partners-api

Status: Ready for deployment

What’s Changed

• Furries PH admins can remove an individual incorrect Pawsport note, issue note, or sticker from the registry after confirmation.
• This is intentionally limited to FPH admins; issuer and partner roles retain their existing access.

Impact

FPH staff can correct accidental registry history entries without deleting the entire Pawsport.

Repositories: docs.furries.ph

Status: Ready for deployment

What’s Changed

• Reused parsed documentation navigation and release-note data across static pages.
• Made expensive full Git-history reconstruction opt-in for page-history generation; normal builds use local file timestamps.

Impact

Documentation deployments and local builds start rendering sooner while preserving the same published content and navigation.

Upgrade Notes

• Set DOCS_PAGE_HISTORY_GIT=1 only when a rebuild needs Git-derived page creation and update dates.