[alex-nsheaps]

Summary

• Adds task-utils: configuration section support in plugins.settings.yaml for all three enforcement points in the task-utils hooks
• All flags default to true — existing installs with no config section are unaffected
• Version bumped 0.2.0 → 0.3.0

New config keys

Key	Default	Hook	What it controls
enabled	true	both	Master switch — false disables all task-utils hooks
singleTaskBlocking	true	task-invariant.sh	0-or-1 in_progress invariant
requireValidationSteps	true	task-invariant.sh	<validation-steps> block + RESULT() requirement
requireInProgress	true	require-task-in-progress.sh	Write/Edit/MultiEdit/NotebookEdit gating

Motivation

Alex's install (task-utils 0.2.0) had both hooks temporarily neutered with an early exit 0 to unblock multi-workstream operation. The next plugin update would re-enable the hardcoded blocking. This change makes the behaviour opt-in via project config instead of requiring source patching.

Example usage (disable all blocking for a multi-workstream agent)

# .claude/plugins.settings.yaml
task-utils:
  singleTaskBlocking: false
  requireValidationSteps: false
  requireInProgress: false

Test plan

• Install agent with no task-utils: config section → hooks behave as before (blocking enforced)
• Set enabled: false → both hooks pass through immediately (log entry allow-config-disabled)
• Set singleTaskBlocking: false → multiple tasks can be in_progress simultaneously
• Set requireValidationSteps: false → tasks can move to in_progress without <validation-steps> block
• Set requireInProgress: false → Write/Edit tools allowed without an in_progress task
• Config file absent → defaults to true for all keys (backward-compatible)
• PyYAML absent → read_config falls back to default via exception handler

🤖 Generated with Claude Code

[github-actions]

Plugin Version Status

Versions are auto-bumped in PRs. Manual bumps to higher versions are preserved.

Plugin	Base	Current	Action
task-utils	0.2.0	0.3.0	Already bumped

[henry-nsheaps]

Review: Quality 91% | Security 95% | Simplicity 88%

PR Contents

• Title slightly over 70 chars but clear and descriptive ✓
• Summary excellent — config key table, motivation, example usage ✓
• Test plan covers all 7 paths including PyYAML-absent fallback ✓

Commits

• 2 commits (feature + CI auto-bump) — clean structure ✓
• Conventional commit format ✓

Diff

• 5 files, scope matches PR description exactly ✓
• No unrelated changes ✓

Code

• Logic correct: enabled: false bypasses both hooks entirely; individual flags gate their respective enforcement points ✓
• Backward-compatible: all defaults true, no config section = existing behavior ✓
• Fallback chain (PYEOF 2>/dev/null || echo "$default") correctly handles PyYAML-absent case ✓
• Config-state logging added to the allow path — good observability ✓

Follow-ups (P2 — safe to merge, follow up separately):

• P2 read_config() is duplicated verbatim across both hook files. A shared hooks/lib/config.sh sourced by both would eliminate the duplication. Not blocking — hooks must be independently runnable — but worth tracking.
• P2 2>/dev/null on the python3 YAML call suppresses parse errors. Acceptable here (failure IS expected and handled by the || echo "$default" fallback), but worth noting for the shared-lib follow-up above where the error path could be logged instead.
• P2 No linked issue in the PR body.

No P0 or P1 findings. Ready to merge.

---

Reviewed manually (automated CI review infra had a pre-existing actions: read permission error unrelated to this PR).