Skip to content

chore: normalize line endings and ignore local recovery artifacts - #1533

Draft
magicVspace wants to merge 1 commit into
Soju06:mainfrom
magicVspace:chore/repo-hygiene-eol-local-artifacts
Draft

chore: normalize line endings and ignore local recovery artifacts#1533
magicVspace wants to merge 1 commit into
Soju06:mainfrom
magicVspace:chore/repo-hygiene-eol-local-artifacts

Conversation

@magicVspace

@magicVspace magicVspace commented Jul 30, 2026

Copy link
Copy Markdown

Summary

Normalize tracked text to LF and keep local recovery artifacts out of ordinary Git staging. This prevents CRLF-only dirty churn while adding defense-in-depth for root backup directories and encryption-key backups.

This PR is intentionally draft until the full GitHub CI gate completes.

Type of change

  • chore: / ci: / build: — tooling, CI, packaging
  • Breaking change

Linked issue: N/A

OpenSpec

  • Not applicable — docs / CI / chore only

Changes

  • add * text=auto eol=lf in .gitattributes
  • ignore root /backups/ and exact encryption.key.backup files at any depth

Test plan

Passed locally:

  • git diff --check
  • exact git check-ignore --no-index assertions for root and nested paths
  • Git attribute/binary integrity audit (3,308 tracked text files already canonical LF; 26 binary files remain binary; renormalization audit changes no tracked content beyond this PR)
  • uv run python -X utf8 scripts/check_proxy_architecture.py
  • uv run ruff check .
  • uv run ruff format --check .

Windows differential unit evidence:

  • patch branch full unit slice: 4,986 passed, 66 skipped, 24 failed
  • UTF-8 failed-only rerun resolved 5 locale failures and left 19 Windows/platform/environment failures
  • the exact same 19 node IDs were run against an untouched detached b91d9bb base worktree and all 19 failed there too, with the same failure classes (os.fork, Windows path/permission/lock behavior, host optional-dependency/proxy environment)
  • therefore the local failures are baseline/environmental, not a passing result and not evidence of a regression introduced by this two-file patch

Full Linux GitHub CI remains the required gate. Its CI and Simplicity budgets workflows are currently awaiting upstream maintainer approval and have not run.

Checklist

  • Title uses Conventional Commits format.
  • No OpenSpec change is required for this repository-hygiene-only patch.
  • Simplicity gates reviewed; no setting, setup step, README section, or dashboard surface is added.
  • CHANGELOG is not edited.
  • Full CI is green.
  • @codex review findings are resolved on the final head.

@chatgpt-codex-connector

Copy link
Copy Markdown

To use Codex here, create an environment for this repo.

Copy link
Copy Markdown
Author

@codex review

Please review the current draft head e65298d1, focusing on whether the LF normalization policy can cause tracked-file or binary churn and whether the ignore patterns are appropriately scoped.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: e65298d183

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Soju06

Soju06 commented Jul 30, 2026

Copy link
Copy Markdown
Owner

Heads-up: the CI runs for this head are sitting in action_required (first-contribution workflow approval), so the gate you are waiting on will not start until a maintainer approves the runs. @Soju06 — this is a 2-file, +4-line hygiene chore with a clean codex review on e65298d1; approving the workflow runs should unblock it. @magicVspace once CI is green, please mark ready for review.

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.

2 participants