Add jamzilla and jamzilla-int performance workflows

[ascrivener]

Adds two new team entries for jamzilla (JIT mode) and jamzilla-int (interpreter mode):

• Workflow files: jamzilla-performance.yml and jamzilla-int-performance.yml
• Docker image: ghcr.io/ascrivener/jamzilla-tiny:edge
• Command: -socket {TARGET_SOCK}
• Env: PVM_MODE=jit (jamzilla) / PVM_MODE=interpreter (jamzilla-int)
• Team directories: teams/jamzilla/ and teams/jamzilla-int/
• README: Updated status table with both entries

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f7dcb83f-22e2-460c-b8e6-633e8b2441fa

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Two new GitHub Actions workflows are introduced for scheduled performance testing of jamzilla and jamzilla-int, each configured to run daily and on manual dispatch. The README is updated to document these new performance monitoring entries in the Minifuzz + Performance team table.

Changes

Cohort / File(s)	Summary
Performance Workflows .github/workflows/jamzilla-int-performance.yml, .github/workflows/jamzilla-performance.yml	Two new workflow files configured to run performance tests on a daily schedule (06:00 UTC) with manual dispatch capability. Both delegate to the reusable-picofuzz workflow with target-specific parameters (jamzilla-int uses interpreter mode, jamzilla uses JIT mode).
Documentation README.md	Two new entries added to the Minifuzz + Performance team table for jamzilla and jamzilla-int, each with corresponding performance badge links.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding two new performance workflows for jamzilla and jamzilla-int, which matches the changeset contents.
Description check	✅ Passed	The description is directly related to the changeset, providing clear details about the workflow files, Docker image, commands, environment variables, and README updates that were added.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

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 and usage tips.}

Tip

Migrating from UI to YAML configuration.

Use the @coderabbitai configuration command in a PR comment to get a dump of all your UI settings in YAML format. You can then edit this YAML file and upload it to the root of your repository to configure CodeRabbit programmatically.

[coderabbitai]

🧹 Nitpick comments (1)

.github/workflows/jamzilla-performance.yml (1)

13-13: Pin the Docker image to an immutable digest for reproducible performance tracking.

The mutable tag :edge allows the underlying image to change between runs, which can cause benchmark fluctuations unrelated to code changes.

Suggested change

-      docker_image: 'ghcr.io/ascrivener/jamzilla-tiny:edge'
+      docker_image: 'ghcr.io/ascrivener/jamzilla-tiny@sha256:<resolved_digest>'

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/workflows/jamzilla-performance.yml at line 13, The Docker image is
pinned to a mutable tag ("docker_image:
'ghcr.io/ascrivener/jamzilla-tiny:edge'") which can change between runs; update
the value to a specific immutable digest (sha256) to ensure reproducible
performance tracking by replacing the ":edge" tag with the image@sha256:<digest>
form; obtain the correct digest from the registry (e.g., ghcr.io manifest or
`docker pull` + `docker inspect --format='{{index .RepoDigests 0}}'`) and set
docker_image to that full digest string.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.github/workflows/jamzilla-performance.yml:
- Line 13: The Docker image is pinned to a mutable tag ("docker_image:
'ghcr.io/ascrivener/jamzilla-tiny:edge'") which can change between runs; update
the value to a specific immutable digest (sha256) to ensure reproducible
performance tracking by replacing the ":edge" tag with the image@sha256:<digest>
form; obtain the correct digest from the registry (e.g., ghcr.io manifest or
`docker pull` + `docker inspect --format='{{index .RepoDigests 0}}'`) and set
docker_image to that full digest string.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0b2ebdfd-b28a-4762-8cb5-2c0a6131b9bd

📥 Commits

Reviewing files that changed from the base of the PR and between c4dc208 and b586857.

📒 Files selected for processing (5)

• .github/workflows/jamzilla-int-performance.yml
• .github/workflows/jamzilla-performance.yml
• README.md
• teams/jamzilla-int/.gitkeep
• teams/jamzilla/.gitkeep