Make a Codex pet worth keeping

Use English throughout this task. Help me create, finish, or submit my own Codex pet to https://github.com/legeling/awesome-codex-pet.

Use the GitHub API by default so I do not need to clone the full repository. The default outcome is a reviewable pull request, not a blocker report. First ask whether I want to make the pet now from a character or references, finish an in-progress pet, or submit an existing pet folder or spritesheet.webp. Collect all missing decisions in one compact question set.

Requirements:
1. Read AGENTS.md, CONTRIBUTING.md, pets.json, collections.json, the validation scripts, and .agents/skills/submit-codex-pet/SKILL.md through the GitHub API. Search canonical_key, names, and franchise collections. canonical_key groups versions of one character rather than being unique per author. Different authors may submit independently produced versions when variant_note explains the distinction, but a byte-identical spritesheet is not allowed.
2. Based on my choice, decide whether to create from references, finish existing assets, add metadata, or validate a complete three-file package. When production or repair is required, fetch and follow the repository's hatch-pet-v1 or hatch-pet-v2 skill without assuming the repository is cloned.
3. The final folder must be pets/<pet-slug>--<author-slug>/ and contain only submission.json, pet.json, and spritesheet.webp. V1 uses 1536x1872. V2 uses 1536x2288 and spriteVersionNumber: 2.
4. Review actions, look directions, identity, scale, and baseline frame by frame. Repair purple, green, cyan, or magenta fringe and transparent holes on dark, light, and checkerboard backgrounds without globally deleting legitimate character colors.
5. Separate final-pet provenance from reference provenance. Credit the submitter or adapter for original or independently AI-generated final pixels. A public source_url may be empty when the source is described honestly and repository use is marked non-commercial. Character references that are not uploaded remain reference-only; do not miscredit their artists as the pet author. Record direct crops, traces, cleanup, or substantial pixel reuse honestly; regenerate or repair them when they cause inconsistent identity, weak actions, damaged outlines, or chroma residue. When bilingual naming is selected, provide both localized_names.en and localized_names.zh.
6. In a temporary local workspace, run or equivalently perform npm run validate:pr, npm run lint, and an isolated installation test. Do not include QA, references, videos, README files, pets.json, generated previews, or temporary files in the pull request.
7. Before publication, show me the contact sheet or final spritesheet and obtain visual approval. Then use the GitHub API to create or reuse a submission branch in my fork, upload the three final files, and open one focused pull request against the upstream repository. A full clone is not required. Once the package, visual approval, and required validation are complete, open it as a **ready-for-review pull request, not a draft**. Use a draft only when I explicitly request one or the submission is knowingly unfinished, and state the remaining work. Attach the contact sheet to the pull request description rather than committing it to the pet directory. Document duplicate research, final-asset authorship, reference/source notes, the non-commercial statement, version, and validation, and link any existing issue. Repository CI also produces a downloadable preview artifact.
8. Do not block because a public source_url or formal license name is absent. Record authorship and source honestly and state "Non-commercial use only." Put review effort into character fidelity, frame consistency, action direction, alternating running gait, look directions, animation continuity, and transparent edges. If GitHub is not authorized, ask me to connect it and retry.
9. Only after those recovery steps still cannot complete, and after I explicitly approve the fallback, create a [Submission] issue containing <!-- pet-flow: submission -->. State one genuine blocker and the exact resolution step, use the exact headings ### Pet runtime version and ### Primary category, and attach a contact sheet plus an accessible spritesheet or compact package. Filenames and local paths are not attachments. Do not publish a long validation report for inaccessible local files.
10. Follow the CI run. Fix deterministic structural or formatting failures; stop for my confirmation when the decision concerns visual direction, pet quality, or duplicate acceptance.

Ask whether I want live creation, continued production, or submission of existing files first. Then inspect my references and assets and carry production or repair, frame-by-frame review, validation, GitHub API upload, pull request creation, and CI follow-up through end to end.