…#123)

* feat: prefer Makefile over stow when dotfiles repo has install target

When ~/.dotfiles contains a Makefile with an install target, run
`make install` instead of invoking stow directly. This lets the dotfiles
repo own its own deployment logic (directory pre-creation, stow flags,
etc.) without requiring OpenBoot to know app-specific details.

Priority order: Makefile → stow packages → direct symlinks.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: use system.RunCommandInDir for make install in dotfiles linker

exec.Command in internal/dotfiles violated the no-direct-exec archtest
rule. Add system.RunCommandInDir (mirrors RunCommand but sets cmd.Dir)
and use it in linkWithMake. Refresh archtest baselines for the two
pre-existing exemptions whose line numbers shifted.

* fix: wrap make install error with context in linkWithMake

Bare error return was inconsistent with the project convention
(fmt.Errorf wrapping) and linkWithStow's error pattern.

* chore: refresh archtest baseline after error-wrap line shift

Adding 3 lines to linkWithMake shifted the two pre-existing exec.Command
exemptions in dotfiles.go; update line numbers in no-direct-exec baseline.

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

…se it (#125)

…ailures (#126)

linkWithMake ran make install without pre-backing-up files that stow
(called by the Makefile) would conflict with. The default dotfiles repo's
Makefile calls stow directly, so pre-existing .gitconfig/.zshrc on the
runner caused make to exit 2, failing all three vm-e2e dotfiles tests.

Apply the same backupConflicts loop that linkWithStow already uses:
scan each package directory, back up regular-file conflicts, restore on
make failure, clean up on success. Also updates the archtest baseline
whose line numbers shifted with the added code.