Conversation
Opcore ship runs depend on setup being idempotent in a fresh worktree. Add a CI guard that runs setup in a throwaway worktree and fails if it leaves dirty files.
Align Opcore Zeroshot defaults with the enforced branch workflow: feature runs target dev and dev promotes to main.
Fix #210 by resolving Python validation tools from the repository under check before falling back to PATH. Routes repoRoot through Python validation status, reports resolved command/source/config metadata, and keeps missing type tools degraded rather than silently passing. Also fixes release package inspection ordering so forbidden public bins fail with the intended diagnostic before packlist checks.
Co-authored-by: Eivind <eivindcovibes.ai@Eivinds-MacBook-Pro.local>
# Conflicts: # packages/validation-python/src/type-check.ts
feat: P0 — Make Python syntax validation compiler-truthful
feat: add canonical Python project-context resolver
fix(python): share import resolution with graph
…ust be comprehensive — graph-backed checks are silently skipped
feat: Hypothetical (validate pre-write) evaluation must be comprehensive — graph-backed checks are silently skipped
…al-bin Fix agent gate local opcore resolution
feat(python): add authoritative mypy type gate
feat(validation-python): complete Pyright authority
…alization fix(rust): bound validation workspace materialization
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
| from typing import TYPE_CHECKING | ||
|
|
||
| if TYPE_CHECKING: | ||
| from pkg import conditional_target |
| @@ -0,0 +1 @@ | |||
| from pkg.star_target import * | |||
| import { mkdtempSync, readFileSync, rmSync, writeFileSync } from "node:fs"; | ||
| import { tmpdir } from "node:os"; | ||
| import { dirname, isAbsolute, relative, resolve, sep } from "node:path"; | ||
| import { delimiter, dirname, isAbsolute, join, relative, resolve, sep } from "node:path"; |
chore(release): sync main ancestry into dev
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
3 participants
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
Promote the verified
devbranch tomainfor the Opcore0.2.1macOS stability hotfix.0.2.1Verification
ffb2e7f3dad821e354317fe62124b1308d642744npm run cipassed end-to-enddocs/release/v0.2.1.mdMerging this PR triggers the main-branch CI and, after successful CI, the automated npm/GitHub release workflow for
opcore@0.2.1.