Platform Updates

• rego.furries.ph 2f9c7e56 - fix(rego): expose full add-on markdown details
• docs.furries.ph cc2511d9 - docs(updates): include dashboard canvas markdown fields
• partners.furries.ph a7c251da - feat(dashboard): use markdown editor in canvas text areas
• docs.furries.ph 0702eb74 - docs(updates): explain registration markdown authoring
• partners.furries.ph 83b11081 - feat(rego): support markdown-ext across catalog authoring
• docs.furries.ph cec51533 - docs(updates): explain richer Google Wallet presentation
• partners.furries.ph 3c4fa91b - feat(wallet): expose event pass presentation editor
• partners-api e3f43ed3 - feat(wallet): enrich event ticket presentation controls
• docs.furries.ph 540d6ba8 - docs(updates): explain organizer wallet gate
• rego.furries.ph 8d342925 - fix(rego): hide wallet action without organizer setup
• docs.furries.ph d003f13b - docs(updates): note assigned design review placement
• rego.furries.ph 97abc6b6 - fix(rego): show assigned designs at final review
• docs.furries.ph da03307d - docs(updates): explain fursona question picker fix
• rego.furries.ph ceda1dcb - fix(rego): show saved fursonas in item questions
• docs.furries.ph e8795a10 - docs(updates): explain editable prefill selections
• rego.furries.ph 8f10a385 - feat(rego): clarify editable prefill choices
• docs.furries.ph 01e0abb0 - docs(updates): announce sticky dashboard dialog actions
• partners.furries.ph ee4d4587 - fix(dialog): keep full-width modal actions visible
• docs.furries.ph 230e4a57 - docs(updates): explain gift recipient eligibility fix
• rego.furries.ph 695b4153 - fix(gifts): respect receiver eligibility before checkout
• partners-api 48b133e2 - fix(rego): reject gifts for existing event registrants
• docs.furries.ph 31b19ae0 - docs(updates): explain quick inclusion controls
• partners.furries.ph 69a276f0 - feat(rego): add inline inclusion switch and variant preview
• docs.furries.ph e3d129b8 - docs(updates): note consistent random draw labels
• rego.furries.ph 547cf93b - fix(rego): label grouped draws consistently
• docs.furries.ph 6adfc3b9 - docs(updates): explain tier variant transition labels
• rego.furries.ph 9ae7f17e - fix(rego): explain tier variant mode and composition changes
• docs.furries.ph d3bdcbf8 - docs(updates): explain retained rego variant groups
• rego.furries.ph cb7a3b0c - fix(rego): clarify fixed variants replacing random draws
• partners-api dfeff895 - fix(rego): show saved variants on paused inclusions in EMS
• partners.furries.ph 64a3f227 - fix(rego): retain selected variants on paused inclusions
• docs.furries.ph 77ca931e - docs(updates): explain tier inclusion background fix
• rego.furries.ph 7242092a - fix(rego): let grouped inclusions inherit tier highlight
• docs.furries.ph 7d6fcd4b - docs(updates): explain newest-first transaction history
• rego.furries.ph 0685a241 - fix(rego): show newest transactions first
• docs.furries.ph 76b1bead - docs(updates): note clearer Rego draw counts
• rego.furries.ph 331aa804 - fix(rego): emphasize current random draw count
• docs.furries.ph 3109a5fa - docs(updates): clarify grouped replacement wording
• rego.furries.ph 3d096cd0 - fix(rego): state replacement before grouped items
• docs.furries.ph 83783e86 - docs(updates): explain shared tier replacement note
• rego.furries.ph 3f8c8665 - fix(rego): group shared tier replacements
• docs.furries.ph 9f04f938 - docs(updates): explain tier cleanup after variant removal
• partners.furries.ph 1323aeb1 - fix(rego): clear removed variants from tier selections
• docs.furries.ph 68b24397 - docs(updates): explain inclusion variation reordering
• partners.furries.ph 7f6b8e99 - feat(rego): reorder inclusion variations in editor
• docs.furries.ph c26336c7 - docs: explain grouped Rego tier variants
• rego.furries.ph 27510f55 - fix: keep expanded tier variants under one inclusion
• docs.furries.ph 283e938e - docs(updates): explain variant-only inventory rows
• partners.furries.ph 7bcd8415 - test(inventory): show variant-only analytics rows
• partners-api 4bbe3a92 - fix(inventory): omit variant-only inclusion parents
• docs.furries.ph be47a5a2 - docs(updates): confirm hosted FIFM closed badge
• docs.furries.ph 38b7aa36 - docs(updates): explain registration closing-time corrections
• rego.furries.ph a2e7bae1 - fix(rego): mark closed tiers red and block unavailable offers
• partners.furries.ph c31b967a - fix(rego): save availability windows in event time zone
• partners-api 26ee9175 - fix(rego): enforce closing windows across registration paths
• rego.furries.ph 12c19e59 - fix(rego): use outline icons for tier changes
• docs.furries.ph 9a20fbe6 - docs(updates): describe outline tier comparison icons
• rego.furries.ph 599f836a - fix(rego): distinguish draw-count changes with direction icons
• docs.furries.ph 675f7baf - docs(updates): describe directional draw-count icons
• rego.furries.ph 02e98759 - fix(rego): show draw icon beside tier count changes
• docs.furries.ph d70873fb - docs(updates): note draw-count icon in tier comparisons
• rego.furries.ph 824e0c3a - fix(rego): carry existing random-draw designs across tiers
• docs.furries.ph 70dbafd0 - docs(updates): explain Rego draw-count comparisons
• rego.furries.ph 097a8b44 - fix(rego): inherit inclusion type in variant details
• partners.furries.ph 54ca6a48 - feat(rego): make variants-only and activation separate switches
• partners-api 113bcd6d - feat(rego): store variants-only separately from item type
• docs.furries.ph 3ab802ea - docs(updates): explain variants-only inclusion switch
• rego.furries.ph e8dca812 - fix(rego): group random draw designs under inclusion
• docs.furries.ph 234ffa69 - docs(updates): explain grouped Rego random draws
• rego.furries.ph 7bae44f4 - fix(rego): align Set and bundle headings with inclusions
• partners.furries.ph d49af78c - feat(rego): configure variant-only inclusion Sets
• partners-api e4d7929e - feat(rego): enforce variant-only Set selections
• docs.furries.ph e5aeadd9 - docs(updates): explain variant-only inclusion Sets
• docs.furries.ph 78bbe141 - docs(updates): explain variant detail isolation
• rego.furries.ph b1315070 - fix(rego): isolate variant detail content
• docs.furries.ph a36f0ec9 - docs(updates): explain tier price order and comparisons
• rego.furries.ph f98b8d64 - fix(rego): compare tiers against cheaper offers
• partners.furries.ph a11284ef - fix(rego): show EMS registration tiers by price
• partners-api 6bd12320 - fix(rego): order registration tiers by price across API
• rego.furries.ph d91bab44 - fix(rego): distinguish random draw entries visually
• docs.furries.ph 3e9b0ed4 - docs(updates): explain named Rego variation entries
• rego.furries.ph 2dbc619f - feat(rego): list variation designs by configured title
• partners-api 930d1a0f - feat(rego): expose named random variation designs
• docs.furries.ph 7fef6c3d - docs(updates): describe requirement evidence uploads
• partners.furries.ph d44a900a - feat(planning): add evidence drop area to My Work
• partners-api e6998231 - fix(planning): allow assigned responders to upload evidence
• docs.furries.ph 2dccaaf6 - docs(updates): describe My Work detail modals - partners.furries.ph 1d87b57f - feat(planning): open My Work details in modals

• docs.furries.ph 9404c751 - docs: explain targeted event communication audiences

• partners.furries.ph be28e28b - feat(communications): group and search blast audiences

• partners-api a4c2f1d4 - feat(communications): target event blasts by participant group

• docs.furries.ph def9b058 - docs: explain dealer package inclusion overrides and table details

• partners.furries.ph 1e7b727a - feat(dealers): configure inherited inclusions and package table details

• rego.furries.ph f3af82a6 - feat(dealers): show shared tier inclusions and package furniture

• partners-api cde1e2a4 - feat(dealers): preserve package inclusion overrides and table details

• docs.furries.ph 5b24e409 - docs(updates): record simpler activity forms

• partners.furries.ph 03982664 - fix(previews): simplify activity question presentation

• rego.furries.ph ecf3e74e - fix(activities): remove redundant question introduction

• docs.furries.ph 884dc7d9 - docs(updates): describe shared dealer landing introductions

• rego.furries.ph 2e1f33cf - feat(dealers): share the application body with registration landing

• partners.furries.ph a6d67804 - feat(dealers): configure a shared landing page body

• docs.furries.ph 3b65d2cd - docs(updates): explain optional dealer application packages

• rego.furries.ph 359dfb9d - feat(dealers): separate application and registration package choices

• partners.furries.ph 4f4bdb90 - feat(dealers): add optional application package requirement

• partners-api 81d784e9 - feat(dealers): make application package choice configurable

• docs.furries.ph db9a3349 - docs(updates): record live application release verification

• docs.furries.ph 2b5e33ff - docs(updates): describe application introductions and revised review rules

• rego.furries.ph f811d9a1 - feat(rego): introduce applications and support owner revisions

• partners.furries.ph 9f2d932a - feat(ems): configure multiple applications and share package preferences

• partners-api 6f06fad4 - feat(applications): allow owned revisions and configurable multiple entries

• docs.furries.ph 6c2339c0 - docs(rego): record verified prefill reward deployments

• partners.furries.ph 299682cd - fix(rego): synchronize refreshed reward presentation in EMS previews

• rego.furries.ph 46b1a883 - fix(rego): refresh reward scripts after stale cache responses

• docs.furries.ph 93534c16 - docs(rego): explain prefill rewards and redemption limits

• partners.furries.ph 9d847636 - fix(rego): validate retained discount limits before saving

• partners-api bdc62a28 - feat(rego): enforce prefill rewards and discount redemption caps

• rego.furries.ph d3bb6dfd - feat(rego): display earned prefill discounts and shop coupons

• partners.furries.ph b9fdf273 - feat(rego): configure prefill rewards and coupon eligibility

• docs.furries.ph e6019bdc - docs(updates): record embedded form dialog verification

• partners.furries.ph fa98b967 - fix(ems): keep canonical form dialogs usable inside previews

• rego.furries.ph ef07e388 - fix(forms): open embedded payment and fursona dialogs

• docs.furries.ph f7e7c165 - docs(updates): explain canonical EMS form previews

• partners.furries.ph e8e8e887 - feat(ems): render previews from canonical Rego form code

• rego.furries.ph 868ef422 - refactor(forms): share public Rego views with EMS previews

• docs.furries.ph 937505e0 - docs: record optional zero-slot dealer packages

• partners-api db53b86a - feat(dealers): support table-only packages using existing attendee rego

• partners.furries.ph e05b67eb - feat(dealers): allow optional zero attendee slots for required rego packages

• rego.furries.ph 9ebb8c17 - feat(dealers): checkout table-only packages without duplicate rego

• docs.furries.ph d73af782 - docs: record explicit dealer package type selection

• partners.furries.ph 132a2bcc - fix(dealers): require package type before configuring a new booth

• docs.furries.ph a0e8edf4 - docs: record shared dealer entitlements and eligibility requirements

• partners.furries.ph 45a39524 - feat(dealers): share tier entitlements and configure rego prerequisites

• rego.furries.ph 6a3567aa - feat(dealers): guide package selection by current rego eligibility

• partners-api e945fc9d - feat(dealers): require existing event rego for eligible packages

• docs.furries.ph d2b426ab - docs(inclusions): record variant visibility and repeated-row fixes

• partners.furries.ph 9708a040 - fix(rego-config): reveal saved inclusion variants by default

• rego.furries.ph 44cc4e38 - fix(rego): show shared inclusion designs once

• docs.furries.ph 38f32518 - docs(wallet): announce Apple passes and shared Pass Config

• partners-api 62587a7e - fix(wallet): use supported redirect handling in Workers

• partners.furries.ph 82011695 - feat(wallet): share Pass Config and add an iPhone sample

• partners-api f84709d3 - fix(wallet): reach WalletWallet through its public Worker route

• rego.furries.ph 20b16b25 - feat(wallet): add Apple passes and aligned receipt actions

• partners-api 0ab41427 - feat(wallet): issue Apple passes for confirmed registrations

• partners.furries.ph cb4d3d2f - fix(forms): isolate activity editing from card drag

• docs.furries.ph d52f47cd - docs(updates): announce editable dashboard visual mode

• rego.furries.ph 81b79b5e - refactor(markdown): share sanitized diagram enhancement

• partners.furries.ph 6c7ff14d - feat(editor): add editable Markdown-backed visual mode

• docs.furries.ph 3a170954 - docs: describe familiar dashboard editor shortcuts

• partners.furries.ph 4cc4c4c8 - fix(editor): support familiar shortcuts and reliable undo

• docs.furries.ph 3b2b1a85 - docs: explain registration save confirmation and retry

• partners.furries.ph f8cc3483 - fix(ems): finish registration saves with canonical confirmation

• partners-api ece4bb06 - fix(ems): retain catalog entitlements in save readback

• partners-api 707f88c6 - fix(ems): preserve tier activation in registration config reads

• docs.furries.ph 021a3e2a - docs: explain separate dealer holder and table fields

• partners.furries.ph faec3401 - fix(wallet): preview dealer holders and tables separately

• partners-api f2afd856 - fix(wallet): separate dealer holder identity from table name

• docs.furries.ph e481cd77 - docs: clarify dealer-only Wallet table details

• partners.furries.ph 61b294bd - fix(wallet): hide attendee table fields in ticket previews

• partners-api 09428621 - fix(wallet): reserve table details for dealer registrations

• docs.furries.ph 9511378f - docs: explain shared registration journey previews

• partners.furries.ph 5dac0712 - feat(ems): preview all registration journeys in one shared modal

• rego.furries.ph 7748d8d9 - refactor(rego): reuse transaction forms in safe dashboard previews

• partners.furries.ph 6490e0a2 - fix(rego): preview tiers with paused inclusion assignments

• docs.furries.ph 773eae56 - docs: record paused-inclusion registration preview fix

• docs.furries.ph a1a6e896 - docs: explain separate global event policy links

• rego.furries.ph 257d0561 - fix(event): group global Conditions of Entry separately

• partners-api 4e375c9e - fix(wallet): label separate platform and event policy links

• partners.furries.ph bdcf9c84 - fix(wallet): distinguish event policies from FPH terms

• docs.furries.ph c518ec0b - docs: record Wallet name and tier placement

• partners-api ff7b8900 - fix(wallet): place attendee name beside tier on event tickets

• partners.furries.ph 1c1999a3 - fix(wallet): show attendee name left of tier in preview

• docs.furries.ph 07136349 - docs: record centered event card layouts

• rego.furries.ph e3510f00 - fix(events): center incomplete card rows

• docs.furries.ph 7f2de1ec - docs: describe bulk shop catalog management

• partners.furries.ph 4cf82953 - feat(shop): manage selected catalog items in bulk

• docs.furries.ph 0cf72017 - docs: record full-card checkbox selection verification

• partners.furries.ph 65b46ea6 - fix(ems): match full-card checkbox activation in previews

• rego.furries.ph add4782f - fix(forms): activate checkbox options across the whole card

• docs.furries.ph c0a7f54f - docs(dealers): describe individual table measurements

• rego.furries.ph 04e499d2 - feat(dealers): show dimensions for each included table

• partners.furries.ph fb5f3f6a - feat(dealers): configure separate dimensions for each table

• partners-api 4550393b - feat(dealers): store individual table measurements in centimetres

• docs.furries.ph 62702ae7 - docs(dealers): describe package community benefit display

• partners-api 38add9e0 - fix(dealers): expose readable package social benefits

• partners.furries.ph 56cc7ba2 - fix(previews): reuse community access display for dealer packages

• rego.furries.ph 25c528ca - fix(dealers): show package community benefits like rego tiers

• docs.furries.ph fb644c7a - docs(dealers): record consistent package detail layout

• rego.furries.ph eb73daf8 - fix(dealers): align package details with inclusion modals

• partners.furries.ph ed7fd6f4 - fix(previews): share inclusion guidance layout for packages

• docs.furries.ph 9af0170f - docs(volunteers): explain multi-role applications

• rego.furries.ph 7f9df1e9 - feat(volunteers): apply for multiple roles in one flow

• partners.furries.ph 207fe469 - feat(volunteers): preview multi-role application steps

• partners-api 7e76f3e4 - feat(volunteers): submit selected roles atomically

• docs.furries.ph c9c9df0c - docs: describe sticky event section navigation

• rego.furries.ph 7f1c5511 - feat(events): add sticky navigation for visible event sections

• docs.furries.ph 1cbe7134 - docs: explain shop address defaults and cart item options

• rego.furries.ph d946a5e6 - feat(shop): collect item options in cart and manage delivery addresses

• partners.furries.ph bf997991 - feat(shop): store private delivery addresses and align preview inputs

• partners-api ce871b0f - feat(shop): manage owned delivery addresses for checkout

• docs.furries.ph 8fab5203 - docs: explain variant selection cards and separate shop cart prices

• rego.furries.ph 9d9bd6e3 - feat: show shop variants as selectable cards with distinct cart prices

• rego.furries.ph 7791dce7 - test: verify profile save returns to the shared modal caller

• docs.furries.ph b47314be - docs: record shared preview release correction

• partners.furries.ph c86f778c - fix: include canonical social settings in dealer preview parity

• docs.furries.ph 8a39b3c9 - docs: explain shared profile editing in dealer applications

• rego.furries.ph 6f3db7ff - test: normalize profile modal certificate formatting

• partners.furries.ph ee31a5d3 - feat: mirror updated dealer representative contact component

• rego.furries.ph 4e9147cb - feat: edit representative profiles in a shared modal

• docs.furries.ph c23b8c8c - docs(friends): explain mutual-friend privacy

• rego.furries.ph dac29efb - feat(friends): add mutual-friend privacy preference

• partners.furries.ph 58ec59f8 - feat(friends): store and enforce mutual-friend privacy policy

• partners-api dae044be - feat(friends): enforce mutual-friend discovery and requests

• docs.furries.ph 70d5e144 - docs(forms): document full-card selection accessibility

• rego.furries.ph 63b90827 - fix(forms): make full checkbox and radio cards selectable

• partners.furries.ph 3085067d - fix(forms): make entire preview choice cards selectable

• docs.furries.ph 20a8879b - docs(shop): explain retirement of Event Merch

• rego.furries.ph 1f549b02 - feat(shop): replace event merch with Event Shop

• partners.furries.ph d153fd1a - feat(shop): remove obsolete merch visibility controls

• partners-api 7fbdeb8b - feat(shop): retire the legacy event merch API

• docs.furries.ph 7518490f - docs: record corrected Dealers Den loading text

• partners.furries.ph 90944aab - fix: display clean Dealers Den loading and package text

• docs.furries.ph 44d893f1 - docs: record dealer package base price controls

• rego.furries.ph 26538ace - feat: display dealer package rates and tier value notices

• partners.furries.ph 6bfec0c4 - feat: let partners override dealer base registration prices

• partners-api aa823853 - feat: support dealer package base tier price overrides

• docs.furries.ph c004a795 - docs: explain Gmail ticket extraction and sender onboarding

• partners.furries.ph 8bf5facb - feat: let partners maintain Gmail event postal details

• partners-api 0f83fc20 - feat: prepare registration emails for Gmail event extraction

• docs.furries.ph 97450d57 - docs: record public Wallet policy links and event document modals

• partners-api c9b58149 - fix(wallet): preserve saved class holder restrictions during sync

• rego.furries.ph 1dfb7e85 - feat(rego): open event policy documents from modal buttons

• partners.furries.ph 422e25fa - fix(wallet): show canonical public policy links in settings

• partners-api a44ce6bd - fix(wallet): link tickets to public registration policies

• docs.furries.ph 4608e303 - docs(wallet): confirm hosted ticket preview and API release

• partners.furries.ph b0409906 - docs(wallet): record verified event ticket rollout

• partners.furries.ph 38566d98 - fix(wallet): preserve Google preview source through CDN delivery

• docs.furries.ph 61c665b9 - docs(wallet): document official ticket preview and provider requirements

• rego.furries.ph 253ec93e - feat(wallet): link confirmation emails to registration save action

• partners-api e3fe253d - feat(wallet): synchronize tickets and rotate transferred entry credentials

• partners.furries.ph ee49c224 - feat(wallet): use Google ticket preview and managed event branding

• docs.furries.ph e0f10040 - docs(dealers): record compact application settings layout

• partners.furries.ph 88459e53 - fix(dealers): keep application settings inputs compact

• docs.furries.ph 79f29dde - docs(dealers): confirm hosted booth package verification

• partners.furries.ph e1d23170 - docs(dealers): record verified booth package release

• docs.furries.ph 19592a72 - docs(dealers): explain booth package pricing and choices

• partners.furries.ph 5e96bded - feat(dealers): configure tier-based and standalone booth packages

• rego.furries.ph dd6de568 - feat(dealers): guide registration by booth package type

• partners-api 348bf84d - feat(dealers): enforce tier-based and standalone booth packages

• partners.furries.ph 5f8773ca - feat(ems): add confirmed removal for activity entries

• partners-api 4cbd1636 - feat(ems): remove individual activity submissions

• rego.furries.ph adf00b03 - fix(rego): open today’s schedule or earliest activity day

• docs.furries.ph d109fc56 - docs(ems): announce schedule time-format preference

• rego.furries.ph 0121f1a3 - feat(rego): switch published schedule time format

• partners.furries.ph db675d0b - feat(ems): switch schedule between 12h and 24h views

• docs.furries.ph 4ea8234f - docs(updates): restore pre-existing historical commit rows

• docs.furries.ph 1b751cd2 - docs(updates): preserve historical release log formatting

• docs.furries.ph c3ddf060 - docs(updates): separate recorded schedule release entries

• docs.furries.ph d3265ec8 - docs(ems): explain event dates and preparation day numbering

• partners.furries.ph 39dbe0e1 - feat(ems): number preparation days from the event start

• rego.furries.ph 455efc27 - fix(rego): show published schedule after about with relative days

• partners-api cf71ecb4 - fix(ems): expose event dates in schedule snapshots

• partners.furries.ph 424cc502 - fix(ems): default schedule days to event details dates

• docs.furries.ph 7565d10c - docs(updates): explain confirmed schedule activity removal

• partners.furries.ph f47e0721 - fix(ems): remove activities from the edit dialog

• partners-api 40f5f823 - feat(hr): apply higher-tier payment and fee policies across registration
• partners.furries.ph dda9866a - feat(hr): configure higher-tier prices and fee absorption by role
• rego.furries.ph 796f8925 - chore(rego): stop tracking local Wrangler cache and trace state
• rego.furries.ph cff14cf3 - fix(rego): exclude partner-funded subsidy fees from attendee charges
• partners.furries.ph d49cb327 - feat(ems): finish HR assignment and subsidy configuration
• partners-api b7918405 - feat(hr): enforce single assignments and selected-tier subsidies
• report.furries.ph 77850044 - docs(licenses): retain bundled dependency notice inventory
• pawsport.furries.ph fe00675a - docs(licenses): retain bundled cryptography attribution inventory
• cms.furries.ph 86cad137 - fix(cms): exclude generated captures from source validation
• furries-ph-cron be1cfdf4 - feat(cron): publish social entitlement reconciliation runner

• partners.furries.ph b425821e - feat(ems): add guarded entry removal and confirmed profile setup
• partners-api 342f18db - feat(ems): enforce confirmed profiles and guarded entry deletion
• rego.furries.ph 0492344c - fix(rego): require confirmed email before profile setup

Repositories: docs.furries.ph

Status: Released

What’s Changed

• Added internal per-section numbering to article links in the documentation sidebar.
• Allowed long sidebar article titles to wrap instead of truncating with ellipses.
• Made only the page table of contents sticky and collapsible on mobile layouts, with a floating current-section header that docks directly under the site header and follows the active heading after the list collapses.
• Matched the docked mobile table of contents width to the documentation shell so it lines up with page content instead of spanning unrelated chrome.
• Matched the stacked mobile table of contents width to the same documentation shell before it becomes sticky.
• Kept dashboard links in the page tools column as normal scrolling content instead of sticky controls.
• Added explicit per-category order frontmatter to docs pages so generated sidebar ordering follows the original manual navigation order instead of filename sorting.

Impact

Readers can keep their place more easily in long documentation sections, especially on mobile where the current page section stays visible while scrolling.

Upgrade Notes

• No operator action is required.

Repositories: docs.furries.ph

Status: Released

What’s Changed

• Reworked the docs information architecture around product-docs patterns used by Supabase and GitHub: start pages, foundations, task guides, surface references, lifecycle guides, and reference pages.
• Rewrote Markdown docs across Reports, Event Management, EMS LAN, and Platform API docs with deeper operator-focused explanations, scope tables, procedures, stop points, handoff rules, and plain-language models.
• Added tags frontmatter across docs pages and changed related links to be generated from shared tags instead of hand-typed related lists.
• Added a reusable rewrite script so the docs structure can be regenerated consistently when the taxonomy changes.

Impact

Partner teams can now move through the docs by product area and task type, then follow tag-based related links to nearby concepts, workflows, references, and surfaces. This should make the docs feel closer to established product documentation rather than a set of disconnected guides.

Upgrade Notes

• Use page tags and the Related panel to move between connected pages.
• When adding a new docs page, include meaningful tags frontmatter so related pages stay automatic.
• Avoid manually repeating related links unless a page needs a special exception.

Repositories: docs.furries.ph

Status: Released

What’s Changed

• Improved the right-side “On this page” navigation styling.
• Added current-section highlighting so the active page section appears in bold.
• Limited the Updates page table of contents to release headings so repeated release-note subsections do not clutter the navigation.

Impact

Readers scanning long release notes can now see which release section they are currently reading without the table of contents stretching into repeated headings.

Upgrade Notes

• No operator action is required.

Repositories: partners.furries.ph, docs.furries.ph

Status: Released

What’s Changed

• Rendered saved report detail pages with the shared markdown-ext renderer.
• Added markdown rendering for report summaries, statements, submitted evidence, violation details, prior history, witness notes, action notes, appeal process text, and sharing notes.
• Normalized contact links in report views so Discord profile values use safe web links instead of showing discord:// protocol text.

Impact

Partner admins, trust and safety reviewers, and event operators should now see formatted report narratives instead of raw markdown symbols such as ###, **bold**, [label](url), or [^1]^.

Upgrade Notes

• Open an existing report that contains evidence links, headings, or Discord contact fields.
• Confirm the formatted text and links are readable before sharing the report with another team.

Repositories: partners.furries.ph, docs.furries.ph

Status: Released

What’s Changed

• Stopped the forgot-password form from showing “Invalid reset link” while someone is only entering their email address.
• Kept the invalid-link message for actual reset-link callback failures.
• Added the release note entry for partner teams and event operators.

Impact

Partner admins and event operators using the forgot-password flow should no longer see a failure state before requesting a reset email.

Upgrade Notes

• Request a fresh reset email from the forgot-password screen if a dashboard password needs to be changed.
• Use the invalid-link message only as a signal that a received reset link is missing, expired, or already used.