Skip to content

Instantly share code, notes, and snippets.

View mikehostetler's full-sized avatar

Mike Hostetler mikehostetler

View GitHub Profile
@mikehostetler
mikehostetler / jido_sprite_smoke_tests_index.md
Created February 21, 2026 13:57
Jido PrBot Sprite Smoke Tests — Index

Jido PrBot — Sprite Smoke Test Scripts

End-to-end smoke tests that validate the full PrBot pipeline using Sprites sandboxed VMs + gh + git + a CLI coding agent.

Each script provisions a sprite, clones a repo, runs a coding agent to make a change, commits, pushes, opens a PR, and comments on the issue — all non-interactively.

Scripts

Provider Gist
@mikehostetler
mikehostetler / SPRITE_SMOKE_TEST_ENV.md
Created February 21, 2026 13:57
Jido PrBot Sprite Smoke Test — .env contract docs

Sprite Smoke Test .env Contract

These scripts auto-source jido_lib/.env first, then .env in the workspace root.

Shared keys (all scripts)

Required:

  • SPRITES_TOKEN (or pre-authenticated sprite login session)
  • GH_TOKEN or GITHUB_TOKEN
@mikehostetler
mikehostetler / test_opencode_sprite.sh
Created February 21, 2026 13:57
Jido PrBot Sprite Smoke Test — OpenCode provider
#!/usr/bin/env bash
#
# test_opencode_sprite.sh
#
# Pressure-test the full PrBot flow using ONLY the Sprites CLI + gh + git
# and one provider CLI in streamed JSON event mode.
#
# Validates: sprite lifecycle, env injection, gh auth, git clone, branch,
# provider streaming prompt, provider code change, commit, push, PR, comment.
#
@mikehostetler
mikehostetler / test_gemini_sprite.sh
Created February 21, 2026 13:57
Jido PrBot Sprite Smoke Test — Gemini provider
#!/usr/bin/env bash
#
# test_gemini_sprite.sh
#
# Pressure-test the full PrBot flow using ONLY the Sprites CLI + gh + git
# and one provider CLI in stream-JSON mode.
#
# Validates: sprite lifecycle, env injection, gh auth, git clone, branch,
# provider streaming prompt, provider code change, commit, push, PR, comment.
#
@mikehostetler
mikehostetler / test_codex_sprite.sh
Created February 21, 2026 13:57
Jido PrBot Sprite Smoke Test — Codex provider
#!/usr/bin/env bash
#
# test_codex_sprite.sh
#
# Pressure-test the full PrBot flow using ONLY the Sprites CLI + gh + git
# and one provider CLI in stream-JSON mode.
#
# Validates: sprite lifecycle, env injection, gh auth, git clone, branch,
# provider streaming prompt, provider code change, commit, push, PR, comment.
#
@mikehostetler
mikehostetler / test_claude_sprite.sh
Created February 21, 2026 13:57
Jido PrBot Sprite Smoke Test — Claude provider
#!/usr/bin/env bash
#
# test_claude_sprite.sh
#
# Pressure-test the full PrBot flow using ONLY the Sprites CLI + gh + git
# and one provider CLI in stream-JSON mode.
#
# Validates: sprite lifecycle, env injection, gh auth, git clone, branch,
# provider streaming prompt, provider code change, commit, push, PR, comment.
#
@mikehostetler
mikehostetler / test_amp_sprite.sh
Created February 21, 2026 13:56
Jido PrBot Sprite Smoke Test — Amp provider
#!/usr/bin/env bash
#
# test_amp_sprite.sh
#
# Pressure-test the full PrBot flow using ONLY the Sprites CLI + gh + git
# and one provider CLI in stream-JSON mode.
#
# Validates: sprite lifecycle, env injection, gh auth, git clone, branch,
# provider streaming prompt, provider code change, commit, push, PR, comment.
#
@mikehostetler
mikehostetler / BEDROCK_STATE_ANALYSIS_SUMMARY.md
Last active February 20, 2026 14:01
Bedrock state assessment (extracted from prior Codex thread)

Bedrock State Assessment (Extracted Summary)

Source: Codex archived thread 019c5d6d-702c-7133-90b9-a88fad081eed
Date context in thread: February 14-15, 2026

Executive Summary

The thread’s conclusion was: Bedrock is architecturally promising for distributed durable state, but should be treated as pre-production for critical durability workloads until a few correctness/durability gaps are closed.

What Looked Strong

JIDO_BEDROCK_PLAN

Summary

Create a new package, jido_bedrock, that provides distributed durable persistence for Jido agents and Jido signals on Bedrock without requiring Postgres or a larger external DB.

The package will implement three adapter surfaces:

  1. Jido.Storage for checkpoints + thread journals used by Jido.Persist.
  2. Jido.Agent.Store for InstanceManager hibernate/thaw persistence.
  3. Jido.Signal.Journal.Persistence for signal docs, causality edges, conversation indexes, checkpoints, and DLQ.
#!/usr/bin/env bash
set -euo pipefail
usage() {
cat <<'USAGE'
Usage: scripts/ralph_wiggum_loop.sh [options]
Runs the "Ralph Wiggum" story loop:
- one Codex execution per story card
- one commit per successful story