Release v26.04.29.2 — Anti-placeholder rule on create_event #46

2026-04-29T12:10:32-04:00

bvandeusen commented

2026-04-29 12:10:32 -04:00

(Migrated from git.fabledsword.com)

Hotfix-style follow-up to v26.04.29.1 — single-commit, prompt-only.

Why

Reproducer in today's prod journal (now-fixed): user said "this Friday, I have an appointment" with no other details. The model immediately called create_event(title="Appointment", description="...hasn't provided details yet") BEFORE asking for time/location, then never updated the title when the user came back with the real info. The placeholder "Appointment" stayed in the calendar permanently.

What

35fab6c — Anti-placeholder rule on create_event description. Names the failure mode explicitly: don't create an event with stand-in titles like "Appointment" / "Meeting" / "Event" and "details TBD" descriptions. Record a moment, ask for the missing pieces, and call create_event once with the actual title, time, and location. The persona changes shipped in v26.04.29.1 (#157) make this complementary — capture-first behavior + anti-placeholder rule together.

Test plan

18 calendar-tool tests pass on the new description (no signature change, just docs)
Ruff clean
Smoke test on prod: ask the assistant about a vague future event ("I have something on Friday") — assistant should record a moment + ask for details, NOT create a placeholder event

Note on CI

The dev-branch CI on 35fab6c had a transient registry-push failure ("failed to push ... unknown" — generic Forgejo registry error) after the build itself succeeded. All code gates (typecheck, lint, tests, build) passed cleanly. The release tag push will run a fresh build and should land without issue.

🤖 Generated with Claude Code

Hotfix-style follow-up to v26.04.29.1 — single-commit, prompt-only. ## Why Reproducer in today's prod journal (now-fixed): user said *"this Friday, I have an appointment"* with no other details. The model immediately called `create_event(title="Appointment", description="...hasn't provided details yet")` BEFORE asking for time/location, then never updated the title when the user came back with the real info. The placeholder "Appointment" stayed in the calendar permanently. ## What **`35fab6c` — Anti-placeholder rule on `create_event` description.** Names the failure mode explicitly: don't create an event with stand-in titles like "Appointment" / "Meeting" / "Event" and "details TBD" descriptions. Record a moment, ask for the missing pieces, and call `create_event` once with the actual title, time, and location. The persona changes shipped in v26.04.29.1 (#157) make this complementary — capture-first behavior + anti-placeholder rule together. ## Test plan - [x] 18 calendar-tool tests pass on the new description (no signature change, just docs) - [x] Ruff clean - [ ] **Smoke test on prod:** ask the assistant about a vague future event ("I have something on Friday") — assistant should record a moment + ask for details, NOT create a placeholder event ## Note on CI The dev-branch CI on `35fab6c` had a transient registry-push failure ("failed to push ... unknown" — generic Forgejo registry error) after the build itself succeeded. All code gates (typecheck, lint, tests, build) passed cleanly. The release tag push will run a fresh build and should land without issue. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bvandeusen/FabledScribe#46