Repository navigation
docs(tasks): polish the Dailybot Plan docs, drop the rename and legacy wording - #124
Conversation
…gacy wording ## Summary Plan is live on /v1/plan/ in API and Web, so the rename banner, the /v1/tasks/ note and the 'formerly' wording are removed from the API reference, README, AGENTS.md and the command help. The shared Beta notice is unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
AI review for
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code review — 1 finding(s): 0 critical · 0 warning · 1 info
Verification: 0 verified · 0 downgraded · 0 refuted · 0 unverified · 1 skipped — grok-4.5
Check: ✅ passing — strictness block-on-critical: highest severity info ≤ critical threshold
Findings
| Severity | Location | Title | Verification | Agreement |
|---|---|---|---|---|
| ℹ️ info | docs/API_REFERENCE.md:800 |
Upgrade floor for pre-3.25.0 clients left only in git history | skipped | — |
Summary
Verdict
Looks good — pure docs/help polish that drops completed-transition wording; one optional retention note on the upgrade floor.
What changed
The PR removes rename/legacy framing now that Dailybot Plan is live on /v1/plan/:
- Help and module copy in
plan.py/_beta.pyno longer say “formerly Tasks” - README command table and
AGENTS.mdstructure comments match the current product name docs/API_REFERENCE.mddrops the Renamed. callout and keeps the live facts (API root,dailybot plancommand root, scopestasks:*, webhookstasks.*)- The shared Beta notice body in
_beta.py/ README is left with “formerly Tasks”, matching the stated “same words as Web and API” constraint tests/plan_root_test.pyasserts the product name onplan --helpinstead of the retired phrase
No auth, credentials, API client, or command-behavior changes. Brand spelling stays Dailybot.
Review notes
- Child-group Beta copy still intentionally includes “(formerly Tasks)”; only transitional banners and help prose were cleaned. That split is coherent with the PR summary.
test_the_old_top_level_names_are_goneand the stale-form sweep inplan_root_test.pystill guard the removed top-level CLI forms even after the README/API sentences about them were shortened.- Adjacent AGENTS.md / API_REFERENCE prose still says “Tasks” for object-level concepts and doors (e.g. “destructive Tasks doors”, “credential reach Tasks”); that is outside this diff and is normal vocabulary for cards/scopes, not a rename regression.
Optional follow-up
The removed API_REFERENCE banner was the only in-tree place that stated CLI 3.25.0+ talks to /v1/plan/ and that older clients calling /v1/tasks/ get 404. Worth a one-line non-banner note if support still sees pre-3.25 installs; otherwise the live root docs are enough.
Recommendation: approve
Check status: ✅ passing — strictness
block-on-critical, highest severity in effectinfo: highest severityinfo≤ critical threshold.This line is written by the reviewer runtime after the gate ran and matches the check conclusion and the tracking comment. Any recommendation above is the model's advisory opinion, not the gate.
|
|
||
| ## Plan (formerly Tasks) — `/v1/plan/*` | ||
|
|
||
| > **Renamed.** The product formerly called Tasks is now **Dailybot Plan** and the public API root is | ||
| > `/v1/plan/` (it replaces `/v1/tasks/` with no fallback). The CLI calls `/v1/plan/` from 3.25.0; earlier | ||
| > versions call `/v1/tasks/`, which a current server answers with 404, so upgrade. Resource names, shapes, | ||
| > scopes (`tasks:read|write|admin`), webhook events (`tasks.*`) and error codes are unchanged. Every command | ||
| > now lives under `dailybot plan` (for example `dailybot plan tasks status`); the old top-level | ||
| > `dailybot tasks|task|board|project|goal` forms are removed, with no alias. | ||
| ## Plan — `/v1/plan/*` | ||
|
|
||
| > Dailybot Plan is served under `/v1/plan/`, and every command lives under `dailybot plan` |
There was a problem hiding this comment.
The shortened Plan callout correctly drops the rename banner, but it also drops the only in-tree note that the CLI speaks /v1/plan/ from 3.25.0 and that older builds still call /v1/tasks/ (current servers answer 404). CHANGELOG.md v3.25.0 does not restate that path cut either.
If operators on pinned older installs still show up in support, keep a single non-banner line under this heading, e.g. “CLI 3.25.0+ uses /v1/plan/; earlier releases called /v1/tasks/ and need an upgrade.” If that cohort is gone, the live root wording here is enough.
1 participant
Summary
Dailybot Plan is live on
/v1/plan/in API and Web, so this removes the legacy wording that only existed for the transition: the rename banner and the/v1/tasks/note indocs/API_REFERENCE.md, the "formerly Tasks" phrasing in the README,AGENTS.mdand thedailybot planhelp. The shared Beta notice is left exactly as shipped by Web and API.Testing
ruffandmypyclean.🤖 Generated with Claude Code