# Sprite Setup Session Notes -- autoresearch-pt5

**Date:** 2026-03-26

## Settings Applied

settings.json was updated from two reference configs:
- https://texts-pt5.sprites.app/texts/2-j3na-zB5k_lX2yVyV3Kw
- https://texts-pt5.sprites.app/agents/oodeCdqKhKhIgHdl4ra2EN3Ej5wa7cUbLG9ZHAGJXQk/page

Changes applied:
- env: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
- effortLevel: high
- model: opusplan
- enabledPlugins (8 active): code-simplifier, feature-dev, ralph-loop,
  commit-commands, security-guidance, autofix-bot, code-review, agent-sdk-dev
- All other plugins explicitly set to false

## Checkpoint Timestamp Issue

The UserPromptSubmit and PostToolUse hooks run sprite-env-check.sh on every
interaction. It warns when the latest versioned checkpoint is 10+ minutes old.

The warning kept firing even after running `sprite-env checkpoints create`.

Root cause: the checkpoint system records create_time as the time of the
underlying filesystem overlay commit, not the time the checkpoint was pinned.
Back-to-back checkpoints with no writes between them share the same timestamp.

Example from this session:
- v0: create_time 2026-03-26T09:12:36Z (session start)
- v1: create_time 2026-03-26T09:12:36Z (pinned right after -- same overlay)
- v2: create_time 2026-03-26T17:44:02Z (pinned after settings.json modified)

Rule: checkpoint *after* making changes, not before or immediately after
another checkpoint with no writes in between.

## Plugin Script Permissions

The ralph-loop stop hook was failing on every session end:
  Permission denied: .claude/plugins/marketplaces/.../ralph-loop/hooks/stop-hook.sh

All .sh files under .claude/plugins/marketplaces/ were missing execute
permission (mode 644 instead of 755). The cache/ copies were fine -- only
the marketplaces/ copies were affected.

Fix: chmod +x on all 16 shell scripts under the marketplaces tree.

## Tools Installed

uv 0.11.1 installed to ~/.local/bin. Required for running reference scripts
from grimoire-pt5.sprites.app (e.g. the texts API example script).

## Encoding Note

The previous version of this report (text ID: HvhRoRHdSug) used UTF-8 em
dashes (U+2014, 0xe2 0x80 0x94). These render as garbage (e.g. a???) in
non-UTF-8 viewers. This version uses ASCII double-hyphens instead.