# Upgrade Guide — v0.28.69

<!-- bump: patch -->

## What Changed

The boot-time grounding audit in `JobLoader.ts` no longer emits a warning for built-in default jobs shipped with instar. The audit is meant to nudge users toward declaring grounding on jobs they add — firing on package-provided defaults created noise the user could not silence without editing vendored jobs, which trained everyone to ignore the message. The exempt set now covers all current and historical built-in default slugs (reflection-trigger, guardian-pulse, insight-harvest, the overseer-* family, identity-review, memory-hygiene, etc.). The audit still fires for user-authored jobs missing grounding, which is the signal it was built for.

Fixes feedback cluster `cluster-jobloader-warns-12-enabled-jobs-lack-grounding-config`.

## What to Tell Your User

- **Quieter startup logs**: "The grounding warning that used to show up in my logs at every boot is gone — it was pointing at my own package defaults, not anything you need to act on."

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Quieter boot logs for built-in jobs | Automatic |

## Evidence

- Root cause traced in `src/scheduler/JobLoader.ts` `auditGrounding`; the warning list was enumerating jobs whose definitions ship in `src/commands/init.ts` `getDefaultJobs()`.
- Verified 22 of 26 warned slugs are currently defined defaults; the remaining 4 (sentry-error-scan, self-diagnosis, evolution-review, commitment-check) are historical defaults still present in long-running agents' `jobs.json`.
- No logic change — only the `GROUNDING_EXEMPT_SLUGS` set widens.
