sweep: BUNDLE_NAME_RE accepts a trailing newline; Bundle.name is used raw as a path segment

[pbean]

Summary

BUNDLE_NAME_RE = re.compile(r"^[a-z0-9][a-z0-9-]{1,39}$") (sweep.py:37) is applied with
.match(), and $ matches before a trailing newline. So a bundle name of "fix-it\n" passes
validation:

>>> BUNDLE_NAME_RE.match("fix-it\n")     # truthy — accepted
>>> BUNDLE_NAME_RE.fullmatch("fix-it\n") # None

Confirmed end to end: validate_triage with bundles=[{"name": "fix-it\n", ...}] returns
errors == [] and plan.bundles[0].name == "fix-it\n".

Consequence

Bundle.name is used raw downstream:

• as a filesystem segment — _run_bundle → _write_intent, self.run_dir / "bundles" / dirname / "intent.md" (sweep.py:637, :1207), with no safe_segment
• as story_key via _bundle_key (dw-fix-it\n), which lands in run state and the journal

On Linux this silently creates a directory whose name ends in a newline. On the native-Windows
target a path segment containing a control character is invalid, so the sweep fails at bundle start.
Branch names are safe — workspace.py:99-100 runs safe_ref_segment — but the directory path and
the story key are not.

Fix shape

Anchor with \Z (or switch the call sites to re.fullmatch):

BUNDLE_NAME_RE = re.compile(r"[a-z0-9][a-z0-9-]{1,39}\Z")

and add a negative case asserting plan is None for a trailing break in both bundles[].name and an
option's bundle_name. Worth auditing the other .match()-with-$ patterns in the same module at
the same time.

Note this is a validation hole, not a ledger-injection one — #305's sanitizer covers the ledger
route (_close_bundle_ledger_when_spec_status builds its note from task.story_key); this is the
path/story-key axis.

Found during the #305 review.

[coderabbitai]

🔗 Related PRs

#93 - feat(sweep): extend intent-gap patch-restore re-drive to deferred-work bundles [merged]
#110 - fix(runs): validate run ids and stop a run ref escaping the runs dir [merged]
#112 - fix(sweep): re-drive in-flight bundles by identity on resume [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[pbean]

Reviewed for bundling — stays its own PR (different module and test file from the #327–#329 deferredwork fixes).

Verified amendment: BUNDLE_KEY_RE (sweep.py:41, .match() at :495/:520/:1161) has the same $+.match() hole. Second-order today — the key only carries a newline if BUNDLE_NAME_RE let one through — but in _ensure_bundle_intent a dw-foo\n key round-trips to name="foo" (.+ can't match \n), silently renaming the degraded bundle. \Z-anchor it in the same PR. These are the only two regexes in the module; the same class exists elsewhere (policy.py, decisions.py:34, sprintstatus.py:18-25) but is out of scope here.