- `/manage/period/$periodId` now has two faces. Edit is opt-in via `?mode=edit`; View is the absence of the param, and `validateSearch` normalises any other value to View. A View/Edit toggle sits in the header, hidden when there is no wallet or the period is frozen.

- Every write affordance now gates on one flag, `showEditControls` (`sdk && mode === 'edit' && editable`). They previously used three different gates: `sdk` alone for the period body form and the topic Edit/Add body buttons, nothing at all for Add topic, and `status === 'upcoming' && !ready && sdk` for the schedule, topic options and election picker — so a ready or ended period showed a half-editable page.

- Drops the `status === 'upcoming'` condition. `editPeriod` asserts only operator, `!ready` and `end > start`, so a draft whose voting window has passed is still editable on chain; gating on status hid the one field needed to fix it.

- A ready period keeps its editors live in Edit mode and shows a warning that saves will fail until it is reverted to draft. The contract, not the UI, rejects the write.

- New `src/utils/periodEditing.ts` with `periodHasVotes` and `periodFrozen`, shared by the list and the detail page. A ready period with votes cast is frozen: the contract blocks `setReady(false)`, so it gets no Edit affordance and no toggle.

- The detail page waits for `usePeriods` before rendering. `ready` comes from that query and falls back to `false`, so until it resolved a frozen period read as a draft — enabled Mark ready, visible toggle, honoured `?mode=edit`.

- Assignment-warning copy branches on the period's own state (draft / ready with no votes / voted) instead of the edit gate, which claimed a revertible period could no longer be corrected.

- Manage list: the title cell links to View, and the actions column holds a single button per row — Edit, or View for a frozen period. Periods with no body read `Untitled` rather than an em dash.

- Add period and Add topic return to `?mode=edit` instead of dropping the operator into View.

- Upcoming status chip is pink; it was `bg-accent`, which renders the same as `--muted` in light mode.

- Show the period title in the /manage list. New Title column, and the whole row is now one `PeriodTableRow` component so the period body is read once per row instead of twice — the title and the ballot label both come from it, and the list query doesn't include it.

- The voting window column now shows dates only, with the full UTC times on hover. This needed a new `formatDateRangeUTC`: the existing `formatDateRange` uses the viewer's timezone, and the manage panel works in UTC, so it could show a different day than the tooltip below it.

- Sample data: election ballots read Support / Veto / Abstain, matching what the manage UI writes.

Fix labels sitting too close to their inputs. In Tailwind v4, `space-y-*` sets margin-bottom on the label, and a plain `<label>` is inline — inline elements ignore top and bottom margins, so the spacing did nothing. `ui/label.tsx` is now `block`, which takes the gap from 1.8px to the 8px it was meant to be, in every form.

This commit introduces a comprehensive security audit report detailing findings from the audit conducted on August 4, 2026. The report highlights one Critical and one High severity finding related to DEX aggregator swaps and ARC-60 domain binding vulnerabilities, along with additional Medium and Low severity findings. Recommendations for addressing these issues are included, along with a summary of the audit scope, methodology, and dependency review.

pushbytess and pushints only discovered a stack overflow after pushing
all of their constants, when the generic post-op depth check ran.
Report the same "stack overflow" error up front, before pre-sizing the
stack or pushing anything, so these ops fail at the same point as the
rest of their immediate validation instead of doing needless work
first.

parseByteImmArgs had an off-by-one that rejected an empty final byte
constant ending exactly at the end of the program, so a program ending
in `pushbytess ""` failed with "const bytes list ran past end of
program" even though the assembler happily emits that encoding.

Fix the bounds check, and reproduce the old behavior for programs run
under protocols before v13 with rejectTrailingEmptyByteImm, which can
simply be deleted once v13 is in effect. Since the bug only caused
errors, and programs are checked when placed on chain, no stored
program depends on it.

Starting at v13, bytecblock and pushbytess check their byte constant
immediates against maxStringSize (4096 bytes) at Check and Eval time,
so byte constants get the same limit and error reporting as AVM byte
values everywhere else.

The assembler reports oversized constants for all versions, since such
programs cannot run once v13 is in effect.

Bumps [aiohttp](https://github.com/aio-libs/aiohttp) from 3.13.5 to 3.14.3.
- [Changelog](https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst)
- [Commits](https://github.com/aio-libs/aiohttp/compare/v3.13.5...v3.14.3)

---
updated-dependencies:
- dependency-name: aiohttp
  dependency-version: 3.14.3
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>