Findings commands - OuterLayer

Every command on this page also takes --url <url> and --app-id <id>. Their defaults are in Credential resolution. Each exits 0 on success and 1 with the reason on stderr otherwise. A fix build runs these commands. To record a finding, see outerlayer emit finding.

outerlayer findings show

List the problems a fix item covers, with each problem’s id and its reports. The key needs work.read. The Agent and Runner presets carry it.

outerlayer findings show [--item <number>] [--json]

Flag	Default	What it does
`--item <number>`	the session’s item	The work item, by its number on the factory. Inside a recorded session, the default is the session’s item.
`--json`	off	Machine-readable output.

outerlayer findings show --item 412

outerlayer findings result

Record the build’s result for one problem. The key needs evidence.insert. The Agent and Runner presets carry it.

outerlayer findings result <problem> --fixed|--not-fixed --note "<text>"
                                     [--item <number>] [--json]

Flag	Default	What it does
`<problem>`	required	The problem’s id, as `findings show` prints it.
`--fixed`	none	The change resolves the problem.
`--not-fixed`	none	The change does not resolve the problem.
`--note "<text>"`	required	One sentence that says what you did or why the problem remains.
`--item <number>`	the session’s item	The work item, by its number on the factory.
`--json`	off	Machine-readable output.

Pass exactly one of --fixed and --not-fixed. A second result for the same problem replaces the first. The command is refused when the item does not cover the problem.

outerlayer findings result 3f2a9c10 --fixed --note "Added the missing proxy variable to the gate script."

A problem counts as fixed only when the build reports it fixed and its pull request merges. See When a problem needs a fix again. Exit codes: 0 recorded, 1 refused or invalid.