Bumps [@hypothesis/frontend-shared](https://github.com/hypothesis/frontend-shared) from 7.3.0 to 7.4.0.
- [Release notes](https://github.com/hypothesis/frontend-shared/releases)
- [Changelog](https://github.com/hypothesis/frontend-shared/blob/main/docs/releases.md)
- [Commits](https://github.com/hypothesis/frontend-shared/compare/v7.3.0...v7.4.0)

---
updated-dependencies:
- dependency-name: "@hypothesis/frontend-shared"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [@aws-sdk/client-s3](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3) from 3.504.0 to 3.511.0.
- [Release notes](https://github.com/aws/aws-sdk-js-v3/releases)
- [Changelog](https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-s3/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-js-v3/commits/v3.511.0/clients/client-s3)

---
updated-dependencies:
- dependency-name: "@aws-sdk/client-s3"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Return an enum rather than `bool | null` to make it clearer what the different
resuls mean.

Extend the matching between focus filters and document segments to support
matching page range focus filters against VitalSource chapter page ranges.

In the case of VitalSource PDF books, each page is a separate segment, so this
matching is simple. For EPUB-based books a segment can span a range of pages,
and the `<mosaic-book>` element doesn't provide an API rather returns the page
range directly as far as I can see. Instead we can use
`MosaicBookElement.getPageBreaks` to get a list of the CFIs and corresponding
labels of pages, which can then be matched against the current segment's CFI.

 - Add `SegmentInfo.pages` field which contains a page range for a
   segment

 - Support matching `SegmentInfo.pages` against focus filters in
   `segmentMatchesFocusFilters`.

 - Display data from `SegmentInfo.pages` in "Version" tab in sidebar

 - Add `getPageBreaks` API to VitalSource interfaces and use the data
   from this API to populate the `SegmentInfo.pages` field in the VS
   integration.

 - Extend the fake VitalSource books in the dev server to return fake page break
   information.

This will be used for testing whether an EPUB chapter's page range ovelaps a
page range focus filter.

The new name is verbose, but it makes it more obvious how the call functions.

Notify the user via a message in the content frame if the client is configured
with a CFI focus filter, and a guest frame is displaying part of the book that
is outside that range. Annotations made in this region will not be visible in
the sidebar while the filter is active, and (probably) won't be counted towards
the assignment.

Allow components to render `null` or other non-element values.

This enables testing CFI-based focus filters and related functionality.

This was mostly straightforward except that the `cdn.hypothes.is` bucket resides
in us-east-1, which has a quirk with regards to determining the bucket region.

Fixes https://github.com/hypothesis/client/issues/5544

Creating realistic dummy content for a VS PDF page is quite involved, so each
page just re-uses the same content but with different metadata and a distinct
URL.

This fixes the S3 deployment script after migration to Commander v12.

See https://github.com/tj/commander.js/blob/master/CHANGELOG.md#migration-tips

Bumps [@hypothesis/frontend-shared](https://github.com/hypothesis/frontend-shared) from 7.2.0 to 7.3.0.
- [Release notes](https://github.com/hypothesis/frontend-shared/releases)
- [Changelog](https://github.com/hypothesis/frontend-shared/blob/main/docs/releases.md)
- [Commits](https://github.com/hypothesis/frontend-shared/compare/v7.2.0...v7.3.0)

---
updated-dependencies:
- dependency-name: "@hypothesis/frontend-shared"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps the sentry group with 2 updates: [@sentry/browser](https://github.com/getsentry/sentry-javascript) and [@sentry/cli](https://github.com/getsentry/sentry-cli).


Updates `@sentry/browser` from 7.98.0 to 7.99.0
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-javascript/compare/7.98.0...7.99.0)

Updates `@sentry/cli` from 2.26.0 to 2.27.0
- [Release notes](https://github.com/getsentry/sentry-cli/releases)
- [Changelog](https://github.com/getsentry/sentry-cli/blob/master/CHANGELOG.md)
- [Commits](https://github.com/getsentry/sentry-cli/compare/2.26.0...2.27.0)

---
updated-dependencies:
- dependency-name: "@sentry/browser"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: sentry
- dependency-name: "@sentry/cli"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: sentry
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [prettier](https://github.com/prettier/prettier) from 3.2.4 to 3.2.5.
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prettier/prettier/compare/3.2.4...3.2.5)

---
updated-dependencies:
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps the eslint group with 2 updates: [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) and [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser).


Updates `@typescript-eslint/eslint-plugin` from 6.19.1 to 6.20.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.20.0/packages/eslint-plugin)

Updates `@typescript-eslint/parser` from 6.19.1 to 6.20.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.20.0/packages/parser)

---
updated-dependencies:
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: eslint
- dependency-name: "@typescript-eslint/parser"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: eslint
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [commander](https://github.com/tj/commander.js) from 11.1.0 to 12.0.0.
- [Release notes](https://github.com/tj/commander.js/releases)
- [Changelog](https://github.com/tj/commander.js/blob/master/CHANGELOG.md)
- [Commits](https://github.com/tj/commander.js/compare/v11.1.0...v12.0.0)

---
updated-dependencies:
- dependency-name: commander
  dependency-type: direct:development
  update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [chai](https://github.com/chaijs/chai) from 5.0.0 to 5.0.3.
- [Release notes](https://github.com/chaijs/chai/releases)
- [Changelog](https://github.com/chaijs/chai/blob/main/History.md)
- [Commits](https://github.com/chaijs/chai/compare/v5.0.0...v5.0.3)

---
updated-dependencies:
- dependency-name: chai
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.1545.0 to 2.1550.0.
- [Release notes](https://github.com/aws/aws-sdk-js/releases)
- [Commits](https://github.com/aws/aws-sdk-js/compare/v2.1545.0...v2.1550.0)

---
updated-dependencies:
- dependency-name: aws-sdk
  dependency-type: direct:development
  update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>

Bumps [@npmcli/arborist](https://github.com/npm/cli/tree/HEAD/workspaces/arborist) from 7.3.0 to 7.3.1.
- [Release notes](https://github.com/npm/cli/releases)
- [Changelog](https://github.com/npm/cli/blob/latest/workspaces/arborist/CHANGELOG.md)
- [Commits](https://github.com/npm/cli/commits/arborist-v7.3.1/workspaces/arborist)

---
updated-dependencies:
- dependency-name: "@npmcli/arborist"
  dependency-type: direct:development
  update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>

Refactor the banner container (`<hypothesis-banner>`) in the PDF viewer to work
more like other `<hypothesis->` UI elements with a controller class that uses
`PreactContainer` to create the element and render its contents.

This leaves just the `<hypothesis-sidebar>` as an exception which works
differently.

The various top-level Hypothesis UI elements in the annotator have a
common structure where:

 - There is a `<hypothesis-{name}>` container element

 - The container has a shadow root with the annotator stylesheet loaded
   into it

 - Preact is used to render the contents of the element, into the shadow
   root.

 - There is a controller which wraps the container element and has
   methods to read/write the displayed data. When the data is changed,
   the Preact tree is re-rendered.

Add a `PreactContainer` utility which implements common parts of this pattern,
and refactor two of the top-level UI controls (bucket bar and adder) to use it.

Use MessagePort's built-in `close` event to detect when the sending frame goes
away, instead of the sending window's `unload` event, which is being deprecated.

Currently only beta/dev versions of Chrome support the MessagePort `close`
event.

Fixes https://github.com/hypothesis/client/issues/5621

Extract the `TopBarToggleButton` component that causes the warning into
a separate module.

Revise the documentation in order to:

 - Reduce uninformative noise ("the X frame informs the Y frame to..."). The
   source and destination frame type are given by the type name.

 - Re-phrase the documentation to read more like either a function description
   or an event description, depending on whether the message is a specific
   command/request or a more general event.

 - Use the plural "guests" to make it clear that there can be more than one
   guest frame.

 - Clarify when events specific to third-party authorities are used.