docs: changelog catch-up for PRs #292 → #318#319
Merged
Conversation
The README + docs/changelog.md last entry was 2026-06-13 (#244). Five substantial PRs (#314 #315 #316 #317 #318) and ten more feature PRs between them and that entry shipped without changelog entries. This brings both files current through today. Twenty new entries (newest first, matching the existing style): 2026-06-21 #318 Relay pull-worker provider (queue + provider + /v1/relay/* HTTP) 2026-06-20 #317 pasclaw plan + build PLAN.md pickup + build --goal + cog mode #316 Cloudflare AI Gateway provider catalog rows #315 MCP progressive disclosure + tool_search #314 Stock defaults adopt lean-edit shape; fs_grep split-gate 2026-06-18 #312 Web UI workspace.zip export + import #310 Model-callable cron tool #309 FTS5 snippet window widened 24 -> 60 #307 Windows cmd.exe quoting fix 2026-06-17 #306 cog-build honours profile=security sandbox #304 cog-build default profile = max-build #303 cog-build list[Path] outputs + Secret inputs + -q 2026-06-16 #302 cog-build optional workspace_in #300 pasclaw build cmd + cog-build/ predictor (parent feature) #299 Checkpoints zpaq backend + /redo #298 AGENTS.md + pasclaw init + /init #297 tool_choice force-a-specific-tool form #296 Delphi ExtraEnv injection fix #295 KB native PDF ingest 2026-06-15 #292 pasclaw profile diff + bench Skipped per the changelog's stated convention ("Bug fixes and review follow-ups are in the full git log"): #293 cmd/profile dcc64 fix #294 skills_manage gemini empty-enum fix #301 cmd.build dcc64 fix #311 cron dcc64 fix Files updated identically (the docs/changelog.md note at the top says "This file mirrors the changelog section at the top of the root README.md"): M README.md 20 entries + 20 link refs added M docs/changelog.md same The link-ref block at the bottom of each file gained 20 [#NNN] entries keeping the existing one-per-line / sorted-numerically format.
Per review feedback: early changelog entries are typically 60-200
chars; entries I added in the catch-up commit ran 250-1111 chars.
Trimmed each of the 20 new entries to fit the historical band:
Before count: 20 min: 252 max: 1111 avg: 580
After count: 20 min: 208 max: 580 avg: 359
Cuts applied:
- Drop implementation detail (file paths, internal field names,
"the only X tool in Y that does Z" asides)
- Drop test-count call-outs
- Drop future-facing notes ("plus follow-up work that ...")
- Collapse aspect-by-aspect breakdowns into single-clause WHAT +
one constraint
- Keep the PR's headline change + its most distinctive token
(config flag, command name, endpoint path, file convention)
Both README.md and docs/changelog.md updated identically. Same 20
PRs, same dates, same order, same link-ref block -- just leaner
prose. Going forward I'll target ~200-400 char entries for new
feature PRs, with up to ~600 only for actual big-feature parents
(matches existing entries like #232 Heartbeat at 844 chars or
#233 shell backends at 783).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The README's changelog last entry was 2026-06-13 (#244). Five substantial PRs (#314–#318) and ten more feature PRs between them and that entry shipped without changelog entries. This brings both
README.mdanddocs/changelog.mdcurrent through today (2026-06-21).20 new entries added
Newest first, matching the existing dense-prose style:
/v1/relay/*HTTP endpoints)pasclaw plan+pasclaw buildPLAN.md auto-pickup +--goalRalph wiring + cogmodeInputcloudflare/-anthropic/-gemini)tool_searchfs_grepsplit-gate fromfs_edit_hashlinecrontool (opt-in)cmd.exequoting fixprofile=securitysandboxmax-buildlist[Path]outputs +Secretinputs +-qworkspace_inpasclaw buildcmd +cog-build/predictor (parent feature)/redopasclaw init+/inittool_choiceforce-a-specific-tool formExtraEnvinjection fixpasclaw profile diff+benchSkipped per changelog convention
The changelog's top line says "Bug fixes and review follow-ups are in the full git log." These were skipped:
kindenum (Gemini 400) #294 skills_manage Gemini empty-enum fixFiles
README.md— 20 dated entries + 20 link-ref entries appendeddocs/changelog.md— identical updates (the file's preamble says "This file mirrors the changelog section at the top of the rootREADME.md.")Test plan
git log --merges)git log -1 --format="%ai"- **YYYY-MM-DD** — <prose> ([#NNN])shapeGenerated by Claude Code