Platform Updates

Repository: rego.furries.ph

Status: Ready for deployment

What’s Changed

• Event cards and event details now show an amber warning when 20% or fewer of registration places remain or when registration closes within 72 hours.

Impact

Attendees can spot limited availability and approaching registration deadlines before they start the form.

Repositories: partners.furries.ph, partners-api

Status: Ready for deployment

What’s Changed

• The Forecasting page now has Start, Stop, and Reset controls for the event currently open.
• Stop freezes the latest saved outlook and suspends automatic page and background recalculation for that event.
• Start resumes the same forecast generation and recalculates immediately from current event data.
• Reset begins a fresh generation while retaining previous forecast vintages for audit and later evaluation.

Impact

Partner admins and operators can deliberately pause forecast work, resume it when planning restarts, or establish a clean new forecast generation without losing the historical evidence trail.

Upgrade Notes

• Apply 20260812150649_add_event_forecast_controls.sql, then deploy partners-api and partners.furries.ph.
• API TypeScript, dashboard Astro diagnostics, the forecasting model certification, the 32-check dashboard/control contract, and an isolated PostgreSQL-compatible migration smoke test pass. Desktop and mobile screenshots verify the responsive control layout.

Repository: rego.furries.ph

Status: Ready for deployment

What’s Changed

• Event-list and event-detail registration badges now use consistent semantic colours: green for open, blue for prefill, amber for upcoming, and red for sold out or closed.

Impact

Attendees can identify whether they can register, save a prefill, wait for opening, or return later at a glance.

Repository: rego.furries.ph

Status: Ready for deployment

What’s Changed

• Event covers remain above the event description in the public event detail page.
• On phones, the attendee registration and gift action card now appears immediately after the event description and before registration tiers, add-ons, and merchandise.
• Desktop retains the established two-column event-content and attendee-action layout.

Impact

Attendees can understand the event first and reach the primary registration actions without those actions interrupting the page introduction or falling below the full product catalogue.

Upgrade Notes

• The Regosite production build passes with 58 generated pages.
• Production-build fixture QA at 1280 × 900 and 390 × 844 confirms the intended order, event-scoped action links, zero horizontal overflow, and no visible overlays. Repository-wide Astro diagnostics retain five unrelated registration/upgrade typing errors and 29 hints.

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

Status: Ready for deployment

What’s Changed

• Partners can make a registration add-on available to every rego tier or only selected tiers.
• Each add-on can have an optional total purchase limit; leaving it blank keeps the add-on unlimited.
• Standard rego, group rego, gifts, upgrades, offline walk-ins, and Dealers Den rego all use the same tier and capacity rules.
• Attendee forms hide tier-ineligible add-ons, mark exhausted add-ons as sold out, and show a low-stock message when ten or fewer purchases remain.
• Add-on usage is counted in one database call only when an event actually has a limited add-on, keeping the request path compatible with Cloudflare free-plan subrequest constraints.

Impact

Partners can safely reserve merchandise or experiences for specific registration tiers and stop accepting purchases at a shared event-wide limit, regardless of which registration workflow the attendee uses.

Upgrade Notes

• Apply 20260812113540_add_addon_tier_availability_and_capacity.sql, then deploy partners-api, partners.furries.ph, and rego.furries.ph together.
• Dashboard Astro diagnostics and production build pass, API TypeScript passes, and the Supabase publish dry-run accepts the pending migration set. Regosite diagnostics retain five unrelated existing errors while its production build passes. Desktop and 390 px mobile browser QA verified tier-mode switching, select-all behavior, purchase-limit hydration, and responsive layout.

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

Status: Airgapped commercial core, signed recovery, and two-way hybrid projection implemented; deployment and live-event rehearsal remain

What’s Changed

• EMS LAN can link one explicitly selected event and keep operator workflows local-first while a background runner probes, queues, retries, and resumes synchronization as internet connectivity changes.
• POS, logistics, inventory, accounting, finance analytics, cash drawers and denomination counts, and settlement declarations now remain available in fully airgapped LAN mode.
• Commercial records use exact centavos, append-only primary facts, movement-derived stock, explicit cash-drawer attribution, and event-isolated recovery exports.
• Receipt, delivery-note, damage, stocktake, and settlement evidence is stored locally by content hash, included in deterministic Ed25519-signed recovery archives, and independently verifiable without internet access.
• Reconnection verifies evidence bytes before idempotently uploading them through the event-authenticated API to private content-addressed storage; browser roles cannot read the bucket or metadata directly.
• POS refunds/voids, accounting corrections, and supervised closed-drawer cash adjustments use linked compensating records. Original completed facts stay immutable while stock, cash, and finance reverse exactly once.
• Commercial Operations now exposes non-stock supply commitments and expected shipments with supplier/reference, status, quantity, and due-time tracking; planned records do not change physical inventory until a movement is recorded.
• Manual accounting now retains VAT, withholding, VAT treatment, receipt/invoice details, TIN, merchant address, account code, and payment-account references in exact minor units while airgapped.
• Settlement proof is stored locally by content hash before the declaration is committed and remains visibly pending until online validation. Admins can create POS, accounting, and cash compensating records from one correction workspace and review them in one immutable journal.
• Operators get a persistent connectivity/queue indicator plus a Hybrid & Recovery page for link, retry, pause, detach, cursor, domain queue, and conflict visibility.
• Another event can be prepared without activating a second runner. Switching requires the current event to be paused with a verified current signed checkpoint, then an explicit named-event confirmation atomically changes the sole local writer binding while preserving the prior event’s queue, credential, cursor, conflicts, evidence, and downloadable archive.
• A reproducible offline baseline now measures check-in, POS, logistics, finance, and signed-archive acknowledgement on venue hardware; the current 120-attendee/401-operation fixture passes every p95/p99 engineering target and keeps the event-B sentinel empty.
• The online service adds revocable one-event credentials, writer epochs, digest-idempotent operation acceptance, a durable event change feed, and private service-role database tables.
• Acknowledged LAN check-in, POS, inventory, logistics, accounting, cash, and settlement operations now project transactionally into canonical online records before their cursor is acknowledged.
• Online-origin changes in those domains return to the selected LAN event cache exactly once. LAN echoes are ignored, while direct concurrent check-in or physical-stock changes are held for operator review.

Impact

Venue internet loss no longer needs to stop onsite sales, supply movement, inventory control, cash reconciliation, finance recordkeeping, or evidence capture. A signed archive can preserve a complete event recovery set while fully airgapped. Reconnection can exchange canonical event-day changes and private evidence without duplicating acknowledged effects. Windows and Android packaged-runtime certification now pass, as does the isolated event-A/event-B failure rehearsal. Production enablement is still gated on a deployed non-production canary, controlled live-event rehearsal, and rollback execution.

Upgrade Notes

• Apply 20260812150000_event_lan_hybrid_sync.sql, 20260812160000_event_lan_evidence_storage.sql, and 20260812170000_event_lan_commercial_corrections.sql; deploy partners-api; and distribute the matching EMS LAN build together before linking a test event.
• Use only a selected non-production event until the deployed canary, controlled live-event rehearsal, and offline-only rollback drill are complete.
• Focused validation passes: hybrid outage/reconnect/lost-response/pause-resume/private-evidence retry plus signed/current checkpoint switching 26/26; airgapped commercial/planned-logistics/tax/evidence/correction suite 31/31; online-origin/canonical-acknowledgement local-cache application 12/12; cross-repo and UI contract gate 24/24; combined deterministic report 93/93; PostgreSQL 17 migration parsing; isolated PostgreSQL-compatible projection/replay/conflict/correction flow; API TypeScript; LAN and dashboard Astro diagnostics/builds; and Supabase publish dry-run. The rebuilt Windows x64 executable passes its complete native release gate, including packaged communications. The final Android rerun passes all 28 hosted and 28 in-app routes. Desktop and 390 px Commercial Operations QA committed planned logistics, proof-backed settlement, and all three correction types with no page overflow or clean-session console warnings/errors.

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

Status: Ready for deployment

What’s Changed

• Partners can independently require linked Discord and Telegram accounts for Dealers Den applicants. Email and contact number remain required for every application.
• Dealer applications now retain assistants, all configured custom-question answers, Other-product descriptions, representative contact details, uploaded payment proof, and submitted portfolio links.
• Applicants can edit pending applications and resubmit when organizers request changes. Partners receive a revision history and can approve, deny, or return an application with notes without erasing its audit record.
• Assistant and friend validation is batched during application saves to reduce API work and stay within Cloudflare free-plan subrequest limits.
• The attendee application remains a five-step registration-style workflow with a final review page covering standard and custom answers.
• Dealers Den registration now restores the earlier representative-and-assistant workflow: a dedicated Your Info step, included-pass guidance, collapsible tier and add-on selectors, account-backed rego details, running cost summaries, and one complete section per accepted assistant. Assistant lookup uses the applicant’s friends list.
• Approved application assistants are now prefilled into the Dealer rego as editable defaults. Representatives can remove or replace them for the registration without changing the reviewed application or its assistant history; final rosters are checked against the selected package capacity and the representative’s accepted friends in one batched lookup.

Impact

Partners can set contact-link policy per event and review a complete, revision-aware application. Applicants receive clear linking requirements, can correct an application without creating duplicate records, and can configure each Dealer table attendee without mixing representative and assistant selections.

Upgrade Notes

• Deploy partners-api, partners.furries.ph, and rego.furries.ph together.
• Apply the pending Dealers Den workflow database migration before enabling the new contact requirements or request-changes flow.
• Dashboard and attendee browser certifications pass, dashboard Astro diagnostics have no errors, and API TypeScript checks pass. Regosite diagnostics retain five unrelated existing errors outside this workflow; its production build and isolated Dealers Den browser certification pass.

Repository: rego.furries.ph

Status: Ready for deployment

What’s Changed

• Dealers Den applications now clearly explain that collective applicants must enter the collective’s own table, catalogue, portfolio, website, and social-media details.

Impact

Collectives can be reviewed using the public identity attendees will actually encounter, while the representative’s attendee account remains the authenticated applicant.

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

Status: Ready for deployment

What’s Changed

• Removed the legacy Dealers Den extra-acknowledgement checklists from dashboard authoring, previews, and attendee applications.
• Conditions of Entry is now the single required consent path for Dealers Den applications.
• Existing acknowledgement data remains retained for history but is no longer sent to attendees; the next settings save clears it.

Impact

Partners should place every Dealers Den waiver, rule, and consent statement in Conditions of Entry.

Repositories: docs.furries.ph, partners-api

Status: Ready for deployment

What’s Changed

• Added a source-backed explanation of the forecasting service architecture, its server-side calculation pipeline, current model families, downstream finance and production projections, input fingerprints, forecast vintages, and post-event evaluation.
• Improved fenced code examples across Markdown guides so formulae and technical examples remain readable, scroll safely on narrow screens, and no longer inherit low-contrast inline-code styling.

Impact

Partners and support teams can now understand how a forecast is produced, which operational records affect it, and why a range or evidence warning appears without inspecting service code.

Upgrade Notes

• Deploy docs.furries.ph; no migration or dashboard configuration change is required.