Arbor Agent Resume Report
Productivityarbor-agent-resume-reportArbor Agent Resume Report is an Agent Skill for productivity published in the RUC-NLPIR/Arbor repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Resume, checkpoint, event, dashboard, finalization, and report phase for Arbor. Use when continuing interrupted sessions, handling running-node requeue, writing checkpoints/messages, consuming events.jsonl/run_stats, recovering best submissions, generating REPORT.md, or summarizing durable artifacts.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/RUC-NLPIR/Arbor/blob/HEAD/skills/arbor-agent-resume-report/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/arbor-agent-resume-report, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Arbor Resume And Report
Use this when a run stops, resumes, times out, or needs a durable report.
Checkpoint Files
Open-source Arbor stores the run under:
.arbor/sessions/<run_name>/
.coordinator/
idea_tree.json
idea_tree.md
checkpoint.json
messages.jsonl
events.jsonl
run_stats.json
REPORT.md
idea_tree.json is the primary state. messages.jsonl restores conversation
history. checkpoint.json stores run name, cycle number, phase, git state,
in-flight executors, cache anchors, and pending human gates.
Resume Procedure
- Require an existing
.coordinator/idea_tree.json. - Load the tree.
- Requeue nodes left as
runningby setting them back topending. - Replay
messages.jsonlif available. - Seal any dangling tool-use tail with an interrupted-result marker.
- Append a short resume nudge:
- do not restart INIT;
- call
TreeView; - continue the loop from pending nodes.
- Keep the existing workspace/session directory.
If the tree is corrupt, do not pretend resume is possible. Start a fresh run in a clean session only after making that explicit.
Events
Important event families:
session.start,session.end,session.checkpointcycle.start,cycle.end,cycle.phaseidea.proposed,idea.completed,idea.pruned,idea.mergedexecutor.start,executor.endtool.start,tool.endllm.call,llm.error,llm.cache_statuser.await,user.input_receivedprogress.heartbeat
Events are JSON-serializable and secret-free. The dashboard, WebUI, stats collector, and reports consume them.
Shutdown
Before final report:
- Wait for background SearchAgents to flush if any are pending.
- Write final checkpoint and messages.
- Run plugin
on_finalizehook if present. - On emergency timeout, recover best submission:
- keep trunk
submission.csvif present; - otherwise copy the best scored snapshot from
submissions/; - otherwise copy the most recent snapshot.
- keep trunk
- Write
run_stats.json. - Generate
REPORT.md.
In smoke/forward tests, finalization is still mandatory even when no real
executor, merge, or B_test ran. Generate REPORT.md, make the smoke caveat
explicit, and stop after artifact validation.
After REPORT.md is written and expected artifacts validate, do not keep
polishing reports or launching extra checks. Return a concise final response
with paths, scores, and caveats.
REPORT.md Contents
Include:
- instruction/task;
- exit reason;
- model/provider if known;
- event summary;
- run stats and token scope;
- baseline/final B_dev;
- baseline/final B_test when available;
- merged ideas;
- top ideas by score;
- artifact paths.
Reports must tolerate partial data. Missing stats, events, or tree fields should produce a partial report, not a crash.
Manual Report Generation
Native:
arbor report <project>/.arbor/sessions/<run_name>
Skill-only:
python <tools>/arbor_state.py report --cwd <project> --run-name <run_name>
For skill-suite smoke tests, run python <tools>/arbor_state.py check before
report for tree integrity, then run it again after report with artifact
flags:
python <tools>/arbor_state.py check --cwd <project> --run-name <run_name>
python <tools>/arbor_state.py report --cwd <project> --run-name <run_name>
python <tools>/arbor_state.py check --cwd <project> --run-name <run_name> \
--require-report --require-experiment --require-executor-prompt
Use --strict-artifacts only for full sessions that are expected to contain
events and run stats in addition to tree, experiment, prompt, and report
artifacts.
Final Response To User
Summarize durable evidence, not transient thoughts:
- session directory;
- final dev/test scores;
- best/merged node ids;
- report path;
- important caveats such as no B_test, timeout, failed search, or incomplete executor run.