Merged
Conversation
) Add .distignore manifest and build script that produces a clean `release` branch stripped of dev-only files (tests, CI, pyproject.toml, CONTRIBUTING.md). CI automatically rebuilds the release branch on every push to main. Users now pull from upstream/release instead of upstream/main, so they never receive test suites, dev configs, or contributor tooling. - .distignore: dev-only file manifest - .gitattributes: export-ignore for ZIP downloads - scripts/build-release.sh: builds clean release branch from main - CI: build-release job runs after quality checks pass on main - /dex-update and docs updated to use upstream/release Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…24) 1. scripts/release.sh — version bump, CHANGELOG header, git tag 2. .github/workflows/release.yml — GitHub Release on tag push 3. core/tests/fixtures/vault/ — minimal PARA vault for integration tests 4. scripts/generate-manifest.sh — installed-files manifest for rollback 5. Updated dex-rollback skill to use manifest for file cleanup Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Lane A: enforce PR merge gates, MCP CI tests, and coverage policy
Lane B: expand MCP behavior, hook harness, and golden-journey tests (retargeted)
Lane C: platform hardening (migrations, security/perf gates, nightly quality) retargeted
davekilleen
force-pushed
the
codex/ritual-intelligence-release
branch
from
bd08794 to
a613830
Compare
Not all PRs are created via /ao — hand-crafted PRs shouldn't fail CI for missing an /ao-specific section. Made-with: Cursor
srinatar
pushed a commit
to srinatar/Dex
that referenced
this pull request
Mar 23, 2026
* feat: build/release pipeline — separate dev from distribution (davekilleen#20) (davekilleen#23) Add .distignore manifest and build script that produces a clean `release` branch stripped of dev-only files (tests, CI, pyproject.toml, CONTRIBUTING.md). CI automatically rebuilds the release branch on every push to main. Users now pull from upstream/release instead of upstream/main, so they never receive test suites, dev configs, or contributor tooling. - .distignore: dev-only file manifest - .gitattributes: export-ignore for ZIP downloads - scripts/build-release.sh: builds clean release branch from main - CI: build-release job runs after quality checks pass on main - /dex-update and docs updated to use upstream/release Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat: Phase 4 — release automation, fixture vault, rollback manifest (davekilleen#24) 1. scripts/release.sh — version bump, CHANGELOG header, git tag 2. .github/workflows/release.yml — GitHub Release on tag push 3. core/tests/fixtures/vault/ — minimal PARA vault for integration tests 4. scripts/generate-manifest.sh — installed-files manifest for rollback 5. Updated dex-rollback skill to use manifest for file cleanup Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat(testing): enforce lane-a merge gates and CI quality policies * fix(ci): use valid GitHub branch protection payload * feat(testing): expand lane-b behavior tests and hook harness gates * Lane C: add migration safety, security/perf gates, and nightly quality * docs: add testing hardening stack merge runbook * fix(ci): handle checklist grep patterns starting with dash * fix(ci): handle checklist grep patterns starting with dash * fix(ci): handle checklist grep patterns starting with dash * test(ci): run screenpipe integration test without pytest-asyncio * fix(ci): allowlist path-contract script self-reference * test(ci): run screenpipe integration test without pytest-asyncio * test(ci): run screenpipe integration test without pytest-asyncio * test(ci): skip screenpipe integration when aiohttp is unavailable * test(ci): skip screenpipe integration when aiohttp is unavailable * fix(ci): remove raw PARA literals from lane-c path gate targets * test(ci): skip screenpipe integration when aiohttp is unavailable * feat: ship Ritual Intelligence v1 * test: stabilize ritual intelligence fixtures * chore: satisfy ritual intelligence quality checks * chore: retrigger governance checks * fix: make Ralph Wiggum Loop section optional in PR governance check Not all PRs are created via /ao — hand-crafted PRs shouldn't fail CI for missing an /ao-specific section. Made-with: Cursor * fix: satisfy ritual intelligence path contracts * test: cover ritual intelligence entrypoints * test: stub eventkit import in CI --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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
Linked Issue
Test Plan
Ralph Wiggum Loop
Risk & Rollback
Docs Impact
Added beta rollout guidance in docs/ritual-intelligence-beta-rollout.md
No dex-app or cloud docs changed because those surfaces remain out of scope for v1
I implemented the change.
I self-reviewed for defects and edge cases.
I addressed review findings and re-ran checks.
I added/updated tests or documented why no tests are needed.
I added a regression test for bug fixes, or this PR is not a bug fix.
I validated failure modes / edge cases.
I updated docs or confirmed no docs impact.
Verification