The 33-60 % figure is for repetitive firmware logs (periodic status lines, hex dumps, etc.) where the XOR-delta between successive bytes is zero most of the time.
The headline should read “compresses repetitive logs”; sorry for the noise.
This two-way sync is slick—saves us from the usual “designer broke prod” dance.
One edge case: if a non-tech user renames a sub-agent in the visual builder while a dev still references the old ID in TypeScript, do you:
automatically rewrite the TS file on the next pull, or
surface a merge conflict and let the dev hand-fix?
Curious how deep the refactor detection goes.
The ids are stable in the dashboard -- users can't modify those.
But generally, for merge conflicts, the current recommendation is to do an `inkeep pull`into a separate 'scratch' project. We're working on more utils to make that case cleaner.
The headline should read “compresses repetitive logs”; sorry for the noise.