Add jotl

[polykrate]

Update memory limit from 512 MB to 2048MB

Summary by CodeRabbit

• Documentation

  • Added project documentation for JOTL (JAM On The Lisp).
  • Included new performance monitoring entry with associated badge in the main documentation.

• New Features

  • Enabled automated daily performance testing for JOTL with configurable execution parameters.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ba3a7d03-e0ca-4743-ab99-5c8abdce77dc

📥 Commits

Reviewing files that changed from the base of the PR and between 8086412 and 69067f9.

📒 Files selected for processing (3)

• .github/workflows/jotl-performance.yml
• README.md
• teams/jotl/README.md

---

📝 Walkthrough

Walkthrough

Introduces a new GitHub Actions workflow for performance testing of the jotl target, configured to run on a daily schedule and reuse the existing reusable-picofuzz workflow. Accompanying documentation updates in the root README and a new team-specific README entry are included.

Changes

Cohort / File(s)	Summary
Performance Workflow Configuration .github/workflows/jotl-performance.yml	New workflow file that triggers daily or on-demand, delegating to reusable-picofuzz with jotl-specific inputs: docker image (ghcr.io/polykrate/jotl:latest), memory (2048m), and readiness pattern configuration.
Documentation Updates README.md, teams/jotl/README.md	Root README updated with jotl performance badge and workflow link in the Minifuzz + Performance table. New team README file created with jotl project header.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• FluffyLabs/jam-testing#2: Introduces identical changes to jotl-performance.yml workflow configuration and teams/jotl README, directly paralleling this PR.

Poem

🐰 A JAM upon the Lisp so grand,
Now dancing in our test command!
With JOTL added to the fold,
Performance stories to be told. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Add jotl' is vague and generic, providing minimal information about what is being added and why, lacking specificity about the actual changes (workflow, performance testing, memory configuration).	Consider a more descriptive title such as 'Add JOTL performance testing workflow with 2048MB memory' to better convey the main purpose and context of the changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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.}

[polykrate]

Superseded by #2 (merged) and #5 (memory increase).