Release v0.3.1

[lionelchamorro]

Follow-up to #4, which merged at b11645e — before these two commits landed.

• fix(fonts): load Archivo weight 300 + italic axis so the Figma "Light Italic" captions (ArchiveProgress/ArchiveView/Search) render real, not faux-synthesised.
• chore: bump package.json to 0.3.1.

After merge, tag v0.3.1 on the merge commit → triggers release.yml (verifies tag matches package.json, builds, and publishes the GitHub Release with the tarball).

🤖 Generated with Claude Code

Summary by Sourcery

Prepare v0.3.1 release with updated font styling and version metadata.

New Features:

• Expand Archivo font imports to include light weight and italics for accurate caption rendering.

Enhancements:

• Document full range of Archivo font weights and styles used by the UI.

Build:

• Bump package version to 0.3.1 for the new release.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the font import to include Archivo light (300) and corresponding italic variants to match Figma usage and bumps the package version to 0.3.1 for release tagging and automation.

Flow diagram for release tagging and automation for v0.3.1

flowchart LR
    D[Developer] --> T[Create git tag v0.3.1]
    T --> GHA[GitHub Actions release.yml]
    GHA --> C[Verify tag matches package.json version 0.3.1]
    C --> B[Build tarball]
    B --> R[Publish GitHub Release with tarball]

Loading

File-Level Changes

Change	Details	Files
Update Archivo font import to include light and italic variants so UI captions use real, not faux, italics.	Expanded Google Fonts @import to include weight 300 and italic axis for weights 300, 400, 600, 700. Documented in-file which weights/styles are covered and their Figma usage to justify the font configuration.	src/styles/fonts.css
Bump package version for the new release.	Incremented package.json version from 0.3.0 to 0.3.1 to align with the release tag and CI release workflow.	package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider adding the &display=swap (or another explicit display mode) parameter to the Google Fonts URL so text rendering behavior is controlled and consistent across consumers of this package.
• Given that this library is shared, you may want to clarify or centralize how consumers can override or disable the Google Fonts import (e.g., via a CSS variable or build-time flag) to avoid forcing these additional font weights/styles in environments that prefer self-hosting.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider adding the `&display=swap` (or another explicit `display` mode) parameter to the Google Fonts URL so text rendering behavior is controlled and consistent across consumers of this package.
- Given that this library is shared, you may want to clarify or centralize how consumers can override or disable the Google Fonts import (e.g., via a CSS variable or build-time flag) to avoid forcing these additional font weights/styles in environments that prefer self-hosting.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}