Platform Updates

Repositories: Partners, Partners API. Status: Released.

What’s Changed: EPS no longer waits for an automatic safety scan before authorized people can download evidence or accept a requirement response. New uploads are not marked clean by the platform. Existing quarantined or rejected files remain blocked.

Impact: People handling EPS evidence must scan downloaded files on their own devices before opening them. Planning administrators may still record an optional manual safety disposition with an audit reason. Classification, access rules, protected storage, and download auditing continue to apply.

Upgrade Notes: Use a locally maintained scanner before opening an EPS evidence file. Do not treat a pending disposition as a platform scan result.

Validation: Partners typecheck, build, Files upload fixture, and screenshot review passed. Partners API type-check, build, and EPS certification scripts passed. Cloudflare Pages built and deployed the merged Partners commit; the Partners API Worker was deployed from merged main. An authenticated upload and download journey was not exercised against production.

Repositories: Partners, Partners API. Status: Released.

What’s Changed: When a work item or requirement changes, EPS sends an operational email to its assigned people and eligible watchers. Linked, ready personal Telegram and Discord chats, and verified SMS contacts, receive the corresponding private message. The notice identifies the changed fields and highlights deadline changes. Completion updates also remain queued for delivery.

Impact: People involved in a task can see what changed without relying on the currently selected event plan. Confidential requirement details remain inside EPS; private-chat notices direct recipients to the governed workspace.

Upgrade Notes: Keep your email current and link a personal chat in EPS notifications if you want Telegram or Discord messages. SMS requires a verified contact and consent. Unlinked or unverified chats cannot receive DMs.

Validation: Database migration applied with no pending migrations. API type check, Worker build dry run, and focused email and multichannel checks passed. The new Worker version is deployed at 100%, and the hosted API responded successfully. A live recipient delivery test was not performed.

Repositories: Partners, Partners API. Status: Released.

What’s Changed: Event planning requirement responses keep the three newest revisions. Submitting another revision automatically retires the oldest one and removes evidence that is no longer part of the retained revisions. A revision can still include up to ten evidence files.

Impact: Submitters and reviewers see the current three revisions. People can continue revising a response after its third revision; the revision number continues to increase.

Upgrade Notes: Download evidence from an older revision before adding another if it needs to be kept outside EPS.

Validation: The database migration was applied and verified remotely. API type checks, focused cleanup tests, and the Worker deployment check passed. The dashboard type check, production build, and browser file-count check passed. The production API schema and dashboard asset show the new behavior. A real account submission remains to verify.

Repository: Partners. Status: Released.

Event planning submitters can choose several PNGs in one response. Uploading an image already used elsewhere no longer blocks a new evidence entry. Adding a revision keeps earlier files in the submission history and carries them into the current revision, up to ten files in total. The revision form shows how many files will be retained before submission. Reviewers see the full current set.

Validation: a local browser check sent three PNGs through three upload requests and checked the revised form; the database migration was applied and verified remotely; the Partners production build passed and the new asset is live. A real account submission has not yet been exercised.

Repositories: Partners, Partners API. Status: Released.

Partner administrators and department leads set evidence access when defining a requirement for event planning work. Submitters can attach files without choosing who may see them. Linked work items use the requirement’s evidence policy. Existing requirements and their attached evidence receive an open policy for plan members, subject to the existing project and confidentiality checks.

Validation: database migration applied and verified remotely; Partners and Partners API build checks passed; the new Partners asset was confirmed live. The manager and submission forms were checked locally.

Repositories: Partners, Partners API. Status: Released.

People submitting an event planning requirement can attach up to ten evidence files to one response. Replacing an eligible submission also accepts multiple files and keeps the numbered submission history. The evidence upload check now permits an eligible replacement after a requirement has been submitted. Existing single-file responses remain readable.

Validation: focused browser checks covered two and ten files, the eleven-file limit, and replacement after submission; type checks and production builds passed. The new database migration is published, the API and dashboard Git-linked production builds succeeded, and the updated dashboard asset is live. The affected user’s personal submission was not exercised.

Repository: Rego. Status: Source pushed; Git-linked release pending verification.

The All inclusions cards now start without tier labels. Attendees can switch the labels on to compare which tiers actually offer each item or design. Inclusion details always show the tier labels, regardless of the card setting. Pills run from green for the lowest-priced tier to red for the highest-priced tier; the tier cards remain the source for quantities and draw rules.

Validation: Rego type check, production build, and local desktop and mobile event-page fixtures. Hosted display remains to verify after the linked release.

Repository: Rego. Status: Source pushed; Git-linked release pending verification.

The event page’s All inclusions section now shows each variant like another inclusion: its own image and description when provided, or the usual no-details message. Random-draw explanations remain with the tier offering so attendees can still see how many designs that tier includes.

Validation: Rego type check, production build, and local desktop and mobile event-page fixtures. Hosted display remains to verify after the linked release.

Repository: Partners API. Status: Released.

My Work no longer fails while loading requirement submissions. Submission history still shows the correct event plan by following each submission’s requirement. People assigned to planning work can reopen My Work; no action is needed on existing submissions.

Validation: production database schema and a read-only submission-to-requirement check, API type check, My Work role test, and the successful Git-linked production Worker build. The affected user’s personal page was not exercised.

Repositories: Partners, Partners API. Status: Released.

Event planning requirements can keep up to ten numbered submission revisions. Submitters can replace their latest eligible response or delete an eligible response from its history. Removed evidence is queued for deletion from the managed media pool; records under legal hold or shared by another live record cannot be removed. The My Work and requirement views show revision history. The removal job checks the media pool before reporting completion and safely retries a removal that already happened but was not recorded.

Validation: local UI type check and browser workflows, API type check and media deletion contract test, plus non-destructive checks against the configured media pool. The database migration was applied, the Git-linked API and interface deployments succeeded, and the hosted interface serves the matching build manifest. An authenticated submission flow and real Sanity deletion remain unverified.