Read-only investigation brief for one Heroku release. It reads the target release, neighboring release/build/runtime/domain context, and asks the AI summarizer for what changed, rollback eligibility, likely operational impact, and next checks. It never creates builds, rolls back, restarts or stops dynos, scales formation, mutates config vars, deletes resources, or calls arbitrary Heroku API routes.

How it works 20 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (20 steps)

■ app_key trim

Trim whitespace from setting app name

■ release_key trim

Trim whitespace from setting release id or version

■ app ?

■ target_release ?

■ releases_raw ?

■ builds_raw ?

■ dynos_raw ?

■ formation_raw ?

■ domains_raw ?

■ releases default

Apply default

■ builds default

Apply default

■ dynos default

Apply default

■ formation default

Apply default

■ domains default

Apply default

■ summarize ?

■ release_rows slice

Take a subset of

■ build_rows slice

Take a subset of

■ release_table to_table

Format results as a data table

■ build_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Investigate this Heroku release using only the provided data. Explain status, current/rollback eligibility, adjacent release context, build signals, runtime/domain implications, and concrete next checks.

heroku setting =

app name setting =

row limit setting = 12

max length setting = 900

release id or version setting =