Problem
talm init --update without --preset resolves the preset from Chart.yaml dependencies, which an init'd project does not record — so the bare form always errors and every remediation hint must carry --preset <preset>. Likewise, the library-drift warning prints a literal <preset> placeholder even though the project records the actual preset name.
Proposal
.talm-preset.lock (introduced in #216) already pins preset: <name> at the project root. Use it as the fallback in the inference chain for init --update: --preset flag → Chart.yaml dependencies → .talm-preset.lock. Let CheckChartDrift read the lock (best-effort) as well, substituting the real preset name into the remediation hint instead of the placeholder — matching what the preset-drift message already does. Projects without a lock keep the current behavior.
Suggested while reviewing #216; deferred there to keep the review scope tight.
Problem
talm init --updatewithout--presetresolves the preset from Chart.yaml dependencies, which an init'd project does not record — so the bare form always errors and every remediation hint must carry--preset <preset>. Likewise, the library-drift warning prints a literal<preset>placeholder even though the project records the actual preset name.Proposal
.talm-preset.lock(introduced in #216) already pinspreset: <name>at the project root. Use it as the fallback in the inference chain forinit --update:--presetflag → Chart.yaml dependencies →.talm-preset.lock. LetCheckChartDriftread the lock (best-effort) as well, substituting the real preset name into the remediation hint instead of the placeholder — matching what the preset-drift message already does. Projects without a lock keep the current behavior.Suggested while reviewing #216; deferred there to keep the review scope tight.