|
1 | 1 | # CCCC v0.4.6 Release Notes |
2 | 2 |
|
3 | | -`v0.4.6` is a smaller quality release focused on operator discipline and agent behavior rather than new product surface area. |
| 3 | +`v0.4.6` builds on `v0.4.5` with a broader set of improvements than a pure prompt/preset polish release. |
4 | 4 |
|
5 | | -It strengthens the built-in role presets with higher-signal planning, review, debugging, and implementation rules, while keeping the core prompt stack compact and predictable. |
| 5 | +Compared with `v0.4.5`, this version extends IM bridge coverage, tightens Web-side context and cache behavior, introduces the first built-in role preset workflow, and hardens startup/shutdown behavior further across Windows and the supervised Web runtime. |
6 | 6 |
|
7 | 7 | ## Highlights |
8 | 8 |
|
9 | | -## 1) Built-in role presets are more rigorous |
| 9 | +## 1) WeCom IM bridge support is now real and documented |
10 | 10 |
|
11 | | -This release upgrades the first-wave built-in role presets with stronger execution discipline harvested from high-quality external prompt patterns. |
| 11 | +The biggest functional addition in `v0.4.6` is WeCom bridge support. |
| 12 | + |
| 13 | +Key changes: |
| 14 | + |
| 15 | +- a dedicated WeCom adapter was added instead of trying to force everything through the older bridge path |
| 16 | +- Web-side IM bridge settings were extended so WeCom can be configured from the same operator surface as other bridge providers |
| 17 | +- authentication and readiness behavior for the bridge were repaired and covered by targeted tests |
| 18 | +- the docs now include a dedicated WeCom guide and screenshots for the operator flow |
| 19 | + |
| 20 | +This matters because `v0.4.5` still treated IM bridge support as narrower and more uneven in practice. `v0.4.6` makes WeCom a real supported path instead of a partial edge lane. |
| 21 | + |
| 22 | +## 2) Web context and cache behavior are tighter and less wasteful |
| 23 | + |
| 24 | +`v0.4.6` also improves how the Web surface reads and refreshes shared control-plane state. |
12 | 25 |
|
13 | 26 | Key improvements: |
14 | 27 |
|
15 | | -- planners now push harder on existing-code leverage, minimum viable scope, and complete-vs-shortcut tradeoffs |
16 | | -- implementers are pushed more explicitly to finish the real blast radius in one pass, including nearby tests, docs, and obvious edge-case handling |
17 | | -- reviewers are stricter about reading the full diff first and checking whether docs, diagrams, or adjacent tests went stale |
18 | | -- debuggers are more firmly rooted in regression checks, hypothesis confirmation, and regression-test follow-through |
19 | | -- explorers are better at separating true canonical anchor files from nearby noise |
| 28 | +- actor and context route caching is more deliberate and more thoroughly tested |
| 29 | +- cache invalidation after writes is less fragile, which reduces stale readback after actor/context updates |
| 30 | +- related API/client/store coverage was expanded significantly so the Web state layer is less likely to drift silently |
| 31 | +- surrounding settings and control surfaces were cleaned up so context-related interactions behave more predictably |
| 32 | + |
| 33 | +This is not a flashy feature, but it is a meaningful quality improvement over `v0.4.5` because it reduces a class of “the write succeeded but the UI still feels stale or noisy” problems. |
| 34 | + |
| 35 | +## 3) Built-in role presets and prompt discipline landed |
| 36 | + |
| 37 | +This release introduces the first built-in role preset workflow in the Web actor surfaces and strengthens the default collaboration guidance around those roles. |
| 38 | + |
| 39 | +Highlights: |
| 40 | + |
| 41 | +- built-in role presets were added for the first-wave roster, including planner, implementer, reviewer, debugger, explorer, and related roles |
| 42 | +- preset application now gives actors a faster way to start from a strong role note instead of writing everything from scratch |
| 43 | +- the prompt/help surface was tightened so startup guidance stays lean while richer discipline lives in the longer-lived help/preset layers |
| 44 | +- planning, implementation, review, and debugging guidance are now sharper about things like existing-code leverage, full-diff-first review, regression thinking, and one-pass blast-radius cleanup |
20 | 45 |
|
21 | | -## 2) The startup prompt stays lean, but a bit smarter |
| 46 | +Relative to `v0.4.5`, this is the biggest day-to-day agent-behavior improvement in the release. |
22 | 47 |
|
23 | | -`v0.4.6` keeps the startup preamble compact while sharpening one important default: |
| 48 | +## 4) Windows and runtime lifecycle handling were hardened again |
24 | 49 |
|
25 | | -- actors are nudged to reuse working paths first instead of inventing parallel ones |
| 50 | +`v0.4.5` already improved startup and shutdown behavior. `v0.4.6` continues that line with another pass of runtime hardening. |
26 | 51 |
|
27 | | -This is intentionally a small change. The goal is to improve default judgment without making the startup prompt bloated again. |
| 52 | +Important changes: |
28 | 53 |
|
29 | | -## 3) Built-in help now has a safer growth budget |
| 54 | +- Windows shutdown cleanup was tightened further so lingering process/lifecycle edge cases are handled more reliably |
| 55 | +- daemon/Web supervised runtime ownership and cleanup paths were hardened with additional lifecycle coverage |
| 56 | +- Web readiness checks now tolerate more real failure modes, including `OSError` and `HTTPException`, instead of surfacing brittle behavior |
| 57 | +- process-path handling and related platform-sensitive helpers received more validation, especially around mocked Windows path resolution and runtime probing |
30 | 58 |
|
31 | | -The built-in help surface remains compact, but the enforced ceiling is relaxed from `1300` to `1500` words. |
| 59 | +This makes `v0.4.6` a stronger operational release than `v0.4.5`, especially if you are running CCCC on Windows or frequently exercising stop/start/restart flows. |
32 | 60 |
|
33 | | -Why this matters: |
| 61 | +## 5) Quality bar and verification |
34 | 62 |
|
35 | | -- it preserves a hard anti-bloat boundary |
36 | | -- it leaves room for a few more genuinely universal rules in future iterations |
37 | | -- it avoids treating the previous `1300` test limit as a product law when it was really just a local compactness guardrail |
| 63 | +Beyond the visible changes above, `v0.4.6` also includes: |
38 | 64 |
|
39 | | -## 4) Release readiness stayed clean |
| 65 | +- additional tests around Web cache behavior and stores |
| 66 | +- stronger coverage for IM bridge startup/config flows |
| 67 | +- targeted prompt-default and role-preset tests so the new guidance surfaces are less likely to regress silently |
| 68 | +- follow-up lint/typecheck cleanup after the role preset work landed |
40 | 69 |
|
41 | | -This version is intentionally small in scope, and the main goal was to land the quality improvements without reopening broader workflow or UI churn. |
| 70 | +In short, `v0.4.6` is not just “the preset release.” It is the release that combines: |
42 | 71 |
|
43 | | -Validation included: |
| 72 | +1. WeCom bridge support |
| 73 | +2. better Web context/cache behavior |
| 74 | +3. the first built-in role preset workflow |
| 75 | +4. another round of Windows/runtime hardening |
44 | 76 |
|
45 | | -- Python test suite passing cleanly |
46 | | -- targeted prompt-default tests passing after the compactness-budget change |
47 | | -- Web lint and type-check remaining clean alongside the role-preset text updates |
| 77 | +relative to the `v0.4.5` baseline. |
0 commit comments