rejectTrailingEmptyByteImm and checkByteImmSizes each tested
Proto.LogicSigVersion, and the size check was too large to inline, so
every bytecblock/pushbytess paid two version compares and a function
call. The checks are mutually exclusive by version, so fold them into
a single if/else in byteImmArgs: one compare, no calls, and both
helpers disappear.

Also skip the size loop entirely when the whole program fits in
maxStringSize: every constant is a sub-slice of the program, so no
constant can exceed the limit unless the program itself does. One
length compare covers all logicsigs (max 1000 bytes) and any app
program of 4096 bytes or less.

Interleaved benchstat runs show -6% on a typical small bytecblock and
no regression when the loop must still run.

- `/manage/period/$periodId` now has two faces. Edit is opt-in via `?mode=edit`; View is the absence of that param, and `validateSearch` normalizes 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`, defined as connected SDK + `mode === 'edit'` + `editable`. `editable` now means the period is not frozen, based on readiness and votes. This replaces the previous status-based definition.

- Dropped the `status === 'upcoming'` condition. The contract's `editPeriod` only asserts operator, `!ready`, and `end > start`, so a draft whose voting window is active or has passed is still editable on chain.

- A ready period with no votes cast is still editable because it can be reverted to draft. It keeps edit controls live in Edit mode and shows a warning that changes will fail until it is reverted. The contract, not the UI, rejects those writes.

- Added `src/utils/periodEditing.ts` with shared `periodHasVotes` and `periodFrozen`, used by the list and detail page. A ready period with votes cast is frozen, so it gets no Edit affordance and no View/Edit toggle.

- Manage periods list: the title cell links to View, and the actions column holds a single button per row: Edit, or View for a frozen period.

- Misc: the Upcoming status chip no longer uses `bg-accent`; it now uses a custom soft pink so it is visually distinct from Ended. This intentionally uses a Tailwind color outside the design tokens because it only appears in the operator-only Manage UI.

binary.Uvarint reports bytesUsed > 0 only when the varint terminated
inside the slice, so pos cannot exceed len(program) after advancing.
The check existed as pos >= len(program), which wrongly rejected an
empty final constant; corrected to pos > len(program) it can never
fire, so delete it and document the invariant.

bytecblock and pushbytess already reject constants over maxStringSize at
assembly time, but byte and pushbytes did not, so the assembler could
still emit programs that always fail the runtime size checks. Enforce
the same limit in asmByte and asmPushBytes (which also covers the byte
pseudo-op paths that delegate to pushbytes).

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.0 to 3.1.5.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.0...v3.1.5)

---
updated-dependencies:
- dependency-name: fast-uri
  dependency-version: 3.1.5
  dependency-type: indirect
...

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