[qchantel]

What does this PR change?

With no earlier release, release-please ignores the manifest's 0.0.0 and starts at its default 1.0.0: the release pull request opened after the release workflow landed proposes 1.0.0 (#19). initial-version sets the first release to 0.1.0, as planned. After merge, the next release-please run updates #19 to 0.1.0; #19 must not be merged before.

Also: the example film on maya.scenario.com takes the page's full width, like the first picture (site/index.html, CSS only).

Validation

• uv run --with pytest pytest -q passes; for changes that touch Maya code, tools/test_maya.sh passes too. The Maya version and OS are listed below.
• python3 tools/lint.py, uvx ruff check . and uvx ruff format --check . pass.
• Packaging changes: the release ZIP installs by dragging install_scenario.py onto a Maya viewport with no errors or warnings in the Script Editor, and its contents were inspected.
• Maya or UI changes were tried in a Maya session (tools/test_maya_gui.sh or by hand), with before/after screenshots for UI.
• Live status is stated: python3 tools/contract_check.py (free) when calls to Scenario change; any paid run had prior authorization for its project and budget.

Commands and results:

• python3 tools/lint.py: clean (the JSON parses). The config is checked on GitHub by the next release-please run.
• tests/unit/test_site.py: 6 passed; the page was checked in a browser after the change.

Public content

• No credentials, tokens, signed URL query strings, or private account, team, project, job or asset IDs are included.
• No personal paths, machine details, agent session IDs or spend anecdotes are included.

Rules

• The spending rules in AGENTS.md still hold (price check first, single-use quotes, paid calls sent once, SCENARIO_NO_SPEND).
• No unrelated manual version or changelog edits; documentation matches the resulting behavior.

Authorship and licensing

• Human review of the complete diff is recorded before merge.
• Adopted third-party code or assets keep their compatible licenses and attribution; original contributions are licensed under MIT, the repository license.

Written with Claude Code (Claude Opus 5.5).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified that the first changelog entry includes commits made since the repository began.
  • Updated the documented initial release version to 0.1.0.
• Style
  • Removed the video container’s background, border, padding, and width limit; added a shadow and border to the video.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The release configuration sets the initial version to 0.1.0, and the first-release guidance describes that version and changelog coverage. The site also changes the film container and video styling.

Changes: Initial release version

Layer / File(s)	Summary
Set and document the initial release version release-please-config.json, RELEASING.md	The configuration sets initial-version to 0.1.0. The guidance contrasts this value with release-please’s default of 1.0.0 and states that the initial changelog entry covers every commit since the repository started.

Film presentation

Layer / File(s)	Summary
Update film and video styling site/index.html	The .film container loses its background, border, padding, and 820px maximum width. The video keeps its sizing and rounded corners and gains a shadow and border.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Merge Risk: Minimal · up to afdda

The change sets the first release to 0.1.0 instead of 1.0.0 and adjusts the film's appearance on the site. No concrete merge-blocking risk was found.

Architecture risk: Low · up to afdda

The change affects 3 systems.

Changed systems: release-please-config.json, RELEASING.md, site

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — release-please-config.json (service) was modified; 1 changed file maps to changed impact.
• observed — RELEASING.md (service) was modified; 1 changed file maps to changed impact.
• observed — site (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in RELEASING.md: The first-release guidance now attributes the starting version to initial-version in release-please-config.json, specifies its value as 0.1.0 and contrasts it with release-please’s 1.0.0 default; it removes the claim that .release-please-manifest.json starts at 0.0.0.
• observed — Modified behavior in release-please-config.json: Adds initial-version with a value of 0.1.0 to the root package configuration.
• observed — Modified behavior in site/index.html: The .film container loses its card background, border, padding, and 820px maximum width. The video keeps its sizing and rounded corners and gains a shadow and border.

Pre-merge checks: 3 · 1

Failed checks: 1 inconclusive

Check name	Status	Explanation	Resolution
Description check		The description covers the main change: release-please ignores the manifest's 0.0.0 and defaults to 1.0.0, so the release pull request #19 proposes 1.0.0. The fix sets initial-version to 0.1.0, and th…	Clarify these items before the check can pass: (1) State the Maya version and OS, or mark the Maya items as not run. (2) Add the exact pytest command and result, or leave the pytest line unticked with a reason. (3) State the live status for…

Passed checks: 3 passed

Check name	Status	Explanation
Title check		The title names the change: the first release is set to 0.1.0 instead of release-please's default 1.0.0. It uses the conventional type(scope) form with the ci scope, which the template lists. It is 77…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the change: the first release is set to 0.1.0 instead of release-please's default 1.0.0. It uses the conventional type(scope) form with the ci scope, which the template lists. It is 77 characters, under the 120-character limit, and has no trailing period.

Full details: Description check

Explanation

The description covers the main change: release-please ignores the manifest's 0.0.0 and defaults to 1.0.0, so the release pull request #19 proposes 1.0.0. The fix sets initial-version to 0.1.0, and the author states that #19 must not merge before the next release-please run updates it. It also covers the site/index.html CSS change that makes the example film full width. The lint check is ticked with the result recorded. The public-content and rules sections are ticked. Missing items: the pytest and Maya validation boxes are unticked with no explanation, the 'Maya version and OS' line the template asks for is absent, the 'tests/unit/test_site.py' result is recorded but the pytest command is not, the contract_check status is not stated, and the human-review box is unticked. The description also says the site page was checked in a browser, which is a manual check the author has not clearly linked to a result. The template asks for an action needed after merge; the author gives one (do not merge #19 early), which is good. The PR title is not included in the provided description, so its conformance to type(scope): summary cannot be assessed.

Resolution

Clarify these items before the check can pass: (1) State the Maya version and OS, or mark the Maya items as not run. (2) Add the exact pytest command and result, or leave the pytest line unticked with a reason. (3) State the live status for python3 tools/contract_check.py, or confirm no Scenario calls changed. (4) Give the browser check a clear result line. (5) Confirm the PR title follows type(scope): summary with a scope from the list (for example docs or release), no trailing period, and 120 characters or fewer. Leave the human-review box unticked until a review happens.

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 7120a98a-ca35-406f-9a2e-fde686690a99

Commits

Reviewing files that changed from the base of the PR and between 04e0763 and afdda09.

Files selected for processing: 1

• site/index.html

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 2 remain after this review.

Recent review details

Context from checks skipped due to timeout: 11

• GitHub Check: CodeRabbit
• GitHub Check: unit (windows-2025, Python 3.13)
• GitHub Check: unit (ubuntu-24.04, Python 3.13)
• GitHub Check: unit (macos-15, Python 3.13)
• GitHub Check: unit (ubuntu-24.04, Python 3.11)
• GitHub Check: unit (macos-15, Python 3.11)
• GitHub Check: unit (windows-2025, Python 3.11)
• GitHub Check: coverage
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (python)

Additional comments: 1

site/index.html: 1

64-64: Functional Correctness

The inline margins of figure.film already reset to zero. The global figure { margin: 0; } rule applies, and .film sets only margin-top. The video fills the figure's width.

[github-code-quality]

Code coverage overview

Languages: Python

Python / code-coverage/python

main e7a804e	fix/release-initial-... afdda09	+/-
87%	87%	0%

ℹ️ Calculations represent line coverage. Results may change as calculations are updated.

---

_{Updated November 13, 2026 16:07 UTC}