Remove the migrated Private Lima calibration harness - #325
Merged
Conversation
Co-authored-by: Codex <noreply@openai.com>
toku345
marked this pull request as ready for review
August 8, 2026 07:51
|
| Filename | Overview |
|---|---|
| .github/workflows/ci.yml | Replaces obsolete harness and profile validation jobs with a full-history protected-input suite whose checkout and test command satisfy the retained test's requirements. |
| tests/outer_loop_history/test_protected_history.py | Moves the unchanged protected-history test into a dedicated discovery directory; the implementation-base commit is available and the suite passes. |
| .chezmoiignore | Removes an ignore entry that became obsolete when the corresponding source directory was deleted. |
| docs/design/codex-claude-outer-loop-private-lima-calibration-implementation.md | Labels the retained implementation design as a historical snapshot and points readers to the active external repository. |
| docs/design/codex-claude-outer-loop-private-lima-calibration.md | Labels the retained calibration design as historical and identifies the repository containing the active implementation. |
| tools/outer-loop-lima-calibration/calibrate.py | Deletes the migrated calibration CLI along with its complete supporting implementation and assets. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart LR
A[dotfiles active calibration harness] -->|migrated| B[private-outer-loop repository]
A -->|removed from dotfiles| C[Harness code and runtime tests deleted]
D[Immutable v1/v2 packages and ADRs] --> E[Protected-history test]
E --> F[Full-history CI job]
G[Historical design snapshots] --> H[Retained in dotfiles]
Reviews (1): Last reviewed commit: "Remove the migrated Private Lima calibra..." | Re-trigger Greptile
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
The active implementation is now maintained in
toku345/private-outer-loop. Removing the frozen duplicate restores a focused dotfiles boundary without changing historical inputs or local runtime state.Validation
git diff --check— passed__pycache__or.pycartifactsSafety
No calibration CLI, Lima lifecycle command, authentication, model call, state migration, cleanup, or evidence mutation was performed.