You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Idiom structured store: .chameleon/idioms/<slug>.json is now idiom truth; idioms.md and the conventions.md TEAM IDIOMS section are generated views.
Migration runs automatically on the first teach/refresh/trust touch; the
original file is preserved as idioms.md.legacy, and unparseable or
suspicious blocks are quarantined verbatim in .chameleon/idioms/.quarantine.md
(a quarantining migration never auto-re-stamps trust).
Per-idiom injection scanning: a suspicious phrase now drops only that idiom,
not the whole file.
First-class idiom reactivation: teach_profile_structured(status="active")
on a deprecated slug reactivates it; deprecation now preserves the body.
Hand or old-version edits to the generated idioms.md are detected by digest
and re-imported additively (mixed-version teams keep their idioms).
chameleon_mcp.core: canonical Finding type, entry-anchored TurnBudget,
flocked per-session state doc (foundations for the Stop pipeline overhaul).
Headerless legacy prose (a hand-written preamble, or a whole pre-store idioms.md with no ### blocks) now migrates into a synthesized legacy-notes idiom instead of vanishing silently; poisoned prose is
quarantined the same as a poisoned block.
Teach refuses loudly against a poisoned, not-yet-migrated idioms.md
instead of migrating (and laundering) it first; trust and refresh scan for
poison before mutating anything, so a poisoned file is never cleaned to an
empty view ahead of the scan that's supposed to catch it.
Changed
Trust hashing on migrated profiles covers idioms/*.json instead of the
generated view. Unmigrated profiles hash exactly as before.
The 200KB cumulative idioms.md cap is no longer enforced at teach time
(per-idiom 50KB caps remain); the whole-file cap returns with the view
renderer work.
With CHAMELEON_TRUST_REVALIDATE=1, the first migration changes the trust
hash surface and triggers a one-time stale/re-trust prompt (default
one-time-trust users are unaffected).