Repository navigation
chore: remove obsolete workflows and LFS restoration - #19
Merged
Merged
Conversation
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.
Change
Remove obsolete tooling after the move to immutable GitHub Releases. Dataset export, trusted review and the deployment gate now require each snapshot's own Release lock and upload plan. Remove LFS restoration, transport switches, lockless historical adapters and legacy review acceptance; retain pointer rejection and the current hash-bound publication checks.
data:*aliases, the old TR orchestrator and its two-map browser adapter. Preserve individual rendering for all five maps,render:all, tests, builds and deployment commands.dexie-react-hooks, unmatched Playwright globs and two unused imports.The active five-map graph, manifests, Release lock and upload plan are unchanged. Existing
v1.0.0packages are reused; no new render or dataset release is required. Renderer backends and fingerprints remain unchanged. Current tools intentionally no longer restore pre-migration snapshots without a Release lock.Checks
pnpm install --frozen-lockfileandpnpm verifypassed: typecheck, lint, 243 application/contract tests, 494 Python tests, 26 acceptance tests, 26 UI tests and production build.pnpm test:acceptance:prepared: 6 passed.git diff --checkpassed. Maintainer reports, private configuration and source game inputs remain outside Git.One Python case-collision test skips on the local case-insensitive filesystem. The normal browser run skips six opt-in prepared tests and the unconfigured candidate gate; the separate runs above exercise those paths. The 74 UI skips are viewport-specific guards. Remote Actions and a full OpenMW rerender are not part of the local verification.