Skip to content

fix: enforce repository identity and safety boundaries - #51

Open
theonly1me wants to merge 7 commits into
mainfrom
fix/confirmed-safety-fixes
Open

fix: enforce repository identity and safety boundaries#51
theonly1me wants to merge 7 commits into
mainfrom
fix/confirmed-safety-fixes

Conversation

@theonly1me

Copy link
Copy Markdown
Owner

What changed

  • Match managed policy and project profile selection against the repository identity parsed from the git remote.
  • Preserve only public provider prefixes during redaction and retain no characters from generic secrets.
  • Bound every provider authentication probe with a timeout.
  • Stop shadowclone learn from installing clone artifacts into the current repository.
  • Discard the ineffective requireCleanExit setting while continuing to parse older repository configuration.
  • Record the confirmed failures, decisions, data boundaries, and regression tests in a design document.

Why

Several safety paths trusted the checkout directory name instead of the repository remote, retained secret characters, or could wait forever for a provider probe. learn also wrote repository files without an explicit install command, while requireCleanExit appeared to enforce a dispatch guarantee that its execution order made unreachable.

How to verify

bun run typecheck
bun run lint
bun test

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