Compare

​

What it does

​

Usage

filepacks compare <baseline> <candidate>

​

When to use it

• comparing a new agent run to the previously accepted run
• checking whether eval output changed between two runs
• reviewing generated files in CI
• deciding whether a candidate artifact needs human attention

​

What compare does

• files added in the candidate
• files removed from the baseline
• files changed at the same path

​

Minimal example

npx filepacks compare ./baseline.fpk ./candidate.fpk

​

Expected output shape

Compare
baseline=/absolute/path/to/baseline.fpk
candidate=/absolute/path/to/candidate.fpk
ok=false
added=1
removed=0
changed=1
added_file=reports/new.txt
changed_file=summary.txt

​

Exit behavior

• exit 0: no differences
• exit 20: one or more differences were found
• exit 1: usage or file/path error

​

Common mistakes

• assuming compare explains why a change is good or bad
• passing a directory instead of a .fpk file
• relying on implicit baseline lookup; you must provide explicit artifact paths

​

Related commands

• verify before comparing artifacts you plan to trust
• inspect when you want a quick summary before comparison
• Diffing for review guidance after the command runs

​

Core API

const result = await compare({
  baseline: '/tmp/baseline.fpk',
  candidate: '/tmp/candidate.fpk',
})

result.mode // 'structural'
result.ok
result.summary
result.added
result.removed
result.changed

​

Scope