Skip to content

Normalize formatting line endings#15

Merged
BigSimmo merged 1 commit into
mainfrom
codex/format-baseline
Jun 4, 2026
Merged

Normalize formatting line endings#15
BigSimmo merged 1 commit into
mainfrom
codex/format-baseline

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Jun 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds a repository .gitattributes policy so text files are checked out with LF endings.
  • Fixes the Windows core.autocrlf=true interaction that caused local npm run format:check failures without a content diff.
  • Keeps this branch format/tooling-only; no source behavior, dependency, env, or data changes.

Verification

Local verification under Node 22:

  • npm run format:check passed
  • npm run lint passed
  • npm run typecheck passed
  • npm run test passed: 39 files, 240 tests
  • npm run build passed
  • npm run test:e2e:chromium passed: 20 tests
  • git diff --check HEAD -- passed

Risk notes

  • This changes repository checkout normalization only.
  • Binary patterns are marked for common image/PDF assets.

@BigSimmo
BigSimmo merged commit e8a3280 into main Jun 4, 2026
4 checks passed
@BigSimmo
BigSimmo deleted the codex/format-baseline branch June 4, 2026 04:14
BigSimmo added a commit that referenced this pull request Jul 22, 2026
…solve #15) (#1057)

* test(clinical): content-first + governance-badge regression tests (#15)

Cover the content-first transitions flagged in #1024's CodeRabbit review for
the two record loaders, locking in the clinical-safety invariant that no
authoritative verification badge is asserted before live governance reconciles:

- registry-record-loader.dom.test.tsx (8 tests): fallback paint during loading,
  the fixture-flag neutralization on the provisional paint, spinner when no
  fallback, live swap-in reconciling the badge on/off against governance,
  passthrough when governance is absent, and not_found / unauthorized states.
- medication-record-page.dom.test.tsx (6 tests): fallback paint vs skeleton,
  live swap-in, error-empty panel, and the governance-drop-on-error invariant
  (a fixture "Reviewed" badge must not persist after an error) contrasted with
  the in-flight loading state that trusts the SSR governance.

Test-only; no source/behaviour change. 14/14 pass under the jsdom project.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* docs(issues): resolve #15 — content-first regression tests added

Move #15 to Resolved/archive; covered by the two new jsdom suites in this PR.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
BigSimmo pushed a commit that referenced this pull request Jul 22, 2026
Resolve the merge conflict against main's concurrent archive edits (keep both the
#15 and #4 resolved rows), and address the review finding: archiving #4
(provider-gated RAG safety ideas) while process-hardening.md still advertised the
same rescope as pending left conflicting durable guidance. Update that bullet to
record the closure (rescue source unrecoverable; thresholds + deep-health already
on main; cost-cap preflight dropped) so /issues and the process-hardening doc agree.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LRZ1EyBZW1ADXrZvMxEEsC
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