v0.10.1

A pack mirrored into a Windows project came back dirty after every sync — no content diff, only line endings, and back again the moment it was reverted. The clone ran under the host's git configuration, and core.autocrlf=true, the Git for Windows default, rewrites a checkout to CRLF whenever the remote repo declares no .gitattributes of its own. materialize_pack then copies those bytes verbatim into the declared mirror:, so a project that normalizes to LF saw its entire vendored pack reported as modified on every run. A pack cannot be relied on to declare its line endings, so the engine no longer relies on the host either.

Highlights

Fixed

• The pack clone materializes the bytes the pack has stored, whatever the host's core.autocrlf says. fetch_remote_source now pins core.autocrlf=false and core.eol=lf next to the core.symlinks=false that was already there, on the shallow clone, the full-clone fallback, and the SHA checkout beside it. autocrlf=false covers packs declaring no attributes; eol=lf covers those that mark files text.
• update.sh pins the same two on its own upstream clone. That checkout is copied straight into intelligence/sync/scripts/, so a CRLF one would install CRLF shell scripts — the thing the engine's own .gitattributes exists to prevent.

Added

• CI asserts it: a job sets core.autocrlf=true globally, syncs a pack that declares no attributes, and fails if a single \r reaches the mirror.

Full changelog: https://github.com/ainova-systems/intelligence-sync/blob/v0.10.1/CHANGELOG.md

Install

Set up intelligence-sync in this project: clone https://github.com/ainova-systems/intelligence-sync, copy its `intelligence/` folder here, and follow intelligence/sync/INIT.md to bootstrap config.yaml and the first rules, agents and skills.

Already installed? Paste this instead:

Update intelligence-sync: fetch the latest engine from https://github.com/ainova-systems/intelligence-sync and run its update flow to migrate this project to the newest version. Leave my rules, agents, and project skills untouched. If it fails, read the CHANGELOG "### Breaking" entries between my version and the latest, base your fix plan on them, make sure you are running the latest scripts, and retry; ask me only if it still fails.