v2.17.3
Fixed
- README privacy filtering overstatement — The "Auto-Capture" Key Feature claimed "privacy filtering that strips secrets and PII", implying active secret/PII detection. The actual implementation (
privacy.ts:stripPrivateContent) only redacts content wrapped in<private>...</private>XML tags; it does not detect raw API keys, passwords, emails, or PII in arbitrary text. README corrected to accurately describe the<private>-tag redaction mechanism. - Incorrect contributor credits in v2.17.2 release notes — @boyxil and @bob56621517 were carried forward from v2.17.0/v2.17.1 into the v2.17.2 GitHub release and changelog. Their work shipped in prior releases, not v2.17.2. Credits removed from both surfaces; v2.17.2 notes now correctly state "No community contributors for this release."
- Stale
queryAwareFilteringrow in README — The dead config field was removed fromconfig.tsin v2.17.2 but the README config table row was missed. Removed.
Removed
- Dead config field
userProfileConfidenceDecayDays— Defined in the config interface, Zod schema, defaults, and merge function (4 places inconfig.ts), but its consumerapplyConfidenceDecay()was deleted in v2.17.2's ponytail cleanup (zero production readers). Removed from all 4 config locations plustests/config.test.ts,tests/tool-scope.test.ts,README.md, anddocs/CONFIGURATION.md. Zod schema uses default (strip) behavior, so existing user configs with this key are silently ignored, not rejected. - Stale "confidence decay" references in
docs/ARCHITECTURE.md— Two references to confidence decay as aUserProfileManagercapability removed (the feature no longer exists).
Contributors
No community contributors for this release. All work by @ZeR020.
Full Changelog: v2.17.2...v2.17.3