v1.8.4 — Remove working branch enforcement

What changed

SDD no longer requires you to be on a specific git branch to run commands. Previously, every write command checked that the current branch matched the branch value in .sdd/config.yaml (default: sdd) and exited with an error if it didn't. That constraint has been removed entirely.

Why

The working branch concept added friction without providing meaningful safety. Teams work on feature branches, hotfix branches, or directly on main — forcing a switch to a dedicated sdd branch before every sdd push or sdd mark-synced was getting in the way.

---

Changes

CLI

Removed the requireCorrectBranch() guard from all write commands:

• sdd sync
• sdd pull
• sdd push
• sdd mark-synced
• sdd mark-cr-applied
• sdd mark-bug-resolved
• sdd drafts
• sdd mark-drafts-enriched

All commands now work on any branch without restriction.

Agent Skills

Removed the ## Working Branch section from sdd and sdd-remote skill files and from generated scaffold templates. Removed the per-workflow step "Verify you are on the working branch" from the enrich and sync workflows in sdd-remote.

Fix

Corrected a stale description in the sdd-flow agent skill: sdd cr pending was described as "Show draft change requests" — it now reads "Show pending change requests".

---

Upgrading

npm install -g @applica-software-guru/sdd

The branch field in .sdd/config.yaml is ignored by all CLI commands from this version onward.