fix(capture): removeCaptureHooks throws on missing hooks array entry in settings.json

[dean0x]

Problem

The removeCaptureHooks() function in src/cli/commands/capture.ts:93 can throw if a settings.json hook entry is missing its hooks array. This throws during the init settings pass, aborting the entire init command.

Current Status

• Pre-existing: identified in feat/flags-typed-registry review (2026-08-25)
• PR feat(flags): typed flag registry, settings-page TUI, new upstream flags #300 Scope: author scoped this out as out-of-scope (not in DIFF_FILES)
• Risk: Init can fail ungracefully if settings.json is malformed

Expected Behavior

• removeCaptureHooks() should gracefully handle missing/malformed hook entries
• Should return a Result type or log a warning instead of throwing
• Init should continue even if hook cleanup encounters a missing array

Acceptance Criteria

• removeCaptureHooks() returns Result type instead of throwing
• Graceful handling of missing hooks array in settings.json entries
• Init completes successfully even if a hook entry is malformed
• Error logged with clear guidance if cleanup is needed
• Test added for malformed hook entry scenario

Related

• PR feat(flags): typed flag registry, settings-page TUI, new upstream flags #300 (feat/flags-typed-registry)
• Source: regression.md review finding, 2026-08-25
• Related: devflow engineering principles (always return Result types)