Skip to content

Sync Interlock from Intelligence Flow @ b3c24af48495 - #9

Closed
operator-stack-publisher[bot] wants to merge 1 commit into
mainfrom
sync/intelligence-flow-b3c24af48495
Closed

Sync Interlock from Intelligence Flow @ b3c24af48495#9
operator-stack-publisher[bot] wants to merge 1 commit into
mainfrom
sync/intelligence-flow-b3c24af48495

Conversation

@operator-stack-publisher

Copy link
Copy Markdown
Contributor

Projection provenance

Generated from operatorstack/intelligence-flow@b3c24af484954ef0e5a12a2e89f99748c1d9f125.
Review the operator contract, provenance, and compatibility before merging.

@operator-stack-publisher
operator-stack-publisher Bot force-pushed the sync/intelligence-flow-b3c24af48495 branch from 46b8458 to b0a0fd5 Compare July 24, 2026 14:28
@bigboateng bigboateng closed this Jul 24, 2026
@bigboateng bigboateng reopened this Jul 24, 2026
@bigboateng

Copy link
Copy Markdown
Contributor

Closing as superseded. This sync projects commit b3c24af4 (prebuilt binaries, Stage 3), which predates the CRLF fix. The Windows test failure here is a false "BREAKING CHANGE" from the compat corpus being checked out as CRLF and compared byte-for-byte against always-LF canonical bytes. Fixed in a3aa03c0 (#161) via .gitattributes (* text=auto eol=lf), which shipped in sync PR #10 (merged, green on all OS) and #11 (merged, green). This branch predates the fix and cannot go green in place.

@bigboateng bigboateng closed this Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant