Harmonize public installation and package copy

[senyo888]

Summary

Harmonize public installation and package wording across the README, contribution guide, v1.0.0 release-note source, per-pet READMEs, catalogue landing page, and all seven installer pages.

The change replaces over-promising one-click language with accurate browser-to-app handoff and package-fallback guidance, uses inspectable package terminology, and normalizes package statements to the exact spritesheet plus matching pet.json.

Architectural intent: keep user-facing copy aligned with the existing catalogue and package ownership model without changing package identity, runtime behavior, installer parameters, catalogue ordering, validation semantics, assets, or deployment mechanics.

Change type

• New pet package
• Existing pet update
• Maintainer-initiated website sync
• Documentation or validation only

Pet details

• Pet name: N/A — collection-wide wording only
• Pet ID: N/A
• Catalogue number: N/A
• Update subtype: N/A
• Related issue: N/A
• Attribution: unchanged

Package checklist

No package, metadata, atlas, preview, QA, or catalogue-entry bytes changed.

• Pet README Package property lists and ordering remain canonical
• Root README count, previews, names, order, summaries, installers, and checksums remain aligned
• Website cards and installers retain canonical identity, number, role, summary, traits, alt text, links, and decoded deep-link parameters
• Website content work was explicitly initiated and approved by the maintainer
• Existing preview cache tokens and atlas SHA-256 values remain unchanged
• Deterministic catalogue ordering remains unchanged

Validation performed

• JSON files parse successfully
• python3 scripts/validate_catalog.py --base-ref origin/main passes
• Preview rendering completed successfully — N/A; no preview or atlas bytes changed
• Local website links and installer routes were checked
• Desktop and 390 px mobile layouts were checked
• Keyboard order, focus visibility, and reduced motion — not rerun; no DOM structure, CSS, interaction, or asset changes
• Browser console contained zero errors or warnings
• HTML5 parsing passed for the landing page and all seven installers
• Privacy scan passed: 84 public candidate files, zero matches
• git diff --check passes

Results:

• Catalogue contract: 7 published pets, 61 local site references, and 78 local Markdown references passed.
• Desktop width 1440 and mobile width 390 had no horizontal overflow.
• Bella installer retained the codex: protocol and two direct package fallbacks.
• Source scope is 17 text files with 22 insertions and 22 deletions.

Files affected

• README.md and CONTRIBUTING.md
• docs/releases/v1.0.0.md
• Six per-pet READMEs whose package wording needed normalization
• site/index.html
• All seven site/install/<pet-id>/index.html pages

Impact

• Runtime/package impact: None. No package metadata, spritesheet, preview, QA, catalogue, loader, or runtime bytes changed.
• Website/UI impact: Text-only wording changes. Layout, CSS, actions, deep links, card order, and installer semantics are unchanged.
• Entity or installer semantics changed: No.
• Generated dashboards/UI affected: No generated surfaces exist in this project; Pages will publish the approved tracked HTML after merge.
• Deterministic lane-ordering risk: None. catalog.json and catalogue numbering/order are unchanged.
• UI truth-consistency risk: Reduced. Copy now describes the browser handoff and fallback path without implying guaranteed one-click installation.
• Migration or restart required: No.
• Hidden behavioral drift: None; the patch changes presentation text only.
• Rollback: Revert this single commit to restore the previous wording. No data, package, or migration rollback is required.

Release and deployment impact

• After merge, the published v1.0.0 GitHub release body should be synchronized from the exact merged docs/releases/v1.0.0.md source under a separate approved release gate.
• Because site/** changes are included, merge to main will trigger the existing Pages deployment workflow. Deployment completion requires a successful workflow run and live desktop/mobile readback.
• This pull request does not itself authorize merge, release editing, or deployment completion.

Rights

No artwork, animation, preview, or other licensed asset changes are included. Existing attribution and CC BY 4.0 terms remain unchanged.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: be9acd46-5486-47b9-bc80-2fb51646a641

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}