core-labs/core
core-labs/core
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Merge pull request 'docs: forbid tea CLI, fix stale smoke-count and tea references' (#54) from docs/forbid-tea-cli-doctrine into main
Some checks failed
lane-shas / verify pinned lane SHAs (push) Successful in 15m35s
Details
full-pytest / fast pytest (-m "not quarantine and not slow" -n 2) (push) Failing after 46m52s
Details

Browse source
This commit is contained in:
Joshua Matthew-Catudio Shay 2026-07-16 21:23:07 +00:00
commit 3019eb41b9
2 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
AGENTS.md
View file

@ -237,8 +237,8 @@ Before branch movement or edits:
Our sole remote and CI/CD platform is **core-gitquarters.acbcontent.org**.
- **DO NOT** use the `gh` (GitHub) CLI for normal work or PR management.
- **DO NOT** attempt to push, pull, or clone from `github.com` for developer/agent loops.
- **USE** the provided Forgejo MCP tools if available.
- **USE** the `tea` CLI (Gitea/Forgejo CLI) for issues, PRs, and repository management targeting `core-gitquarters.acbcontent.org`.
- **DO NOT** use the `tea` CLI (Gitea/Forgejo CLI) — it frequently hangs and times out (Cloudflare 524) due to HTTP/2 proxying and WAF handoffs.
- **USE** the Gitea/Forgejo MCP tools for issues, PRs, and repository management targeting `core-gitquarters.acbcontent.org`.
### Local-First CI Validation Protocol
To optimize server resources and bypass external CI billing dependencies, all agents and developers must run validation suites locally.
@ -246,9 +246,9 @@ To optimize server resources and bypass external CI billing dependencies, all ag
```bash
uv run core test --suite smoke -q
```
Ensure all 108+ tests pass. Pushing broken code is a critical protocol violation.
Ensure all 175 tests pass (parity with the CI smoke gate is pinned by `test_cli_smoke_suite_covers_ci_smoke_gate`). Pushing broken code is a critical protocol violation.
- **Pre-Merge Gate:** Before proposing a merge or requesting a review on a PR, you **MUST** run the larger validation suite relevant to your changes (e.g. `uv run core test --suite cognition` or `uv run core test --suite algebra`).
- **PR Documentation:** When creating a PR on Forgejo (via `tea pr create`), document the local test execution in the PR description, matching this format:
- **PR Documentation:** When creating a PR on Forgejo (via the Forgejo MCP tools), document the local test execution in the PR description, matching this format:
`[Verification]: Smoke suite passed locally (<run_duration>s, <test_count> passed)`
### CI/CD Runner Architecture (2026-07-16 doctrine)

2
CLAUDE.md
View file

@ -3,7 +3,7 @@
`AGENTS.md` is the canonical governance file. If this file conflicts, follow `AGENTS.md`.
Startup: read `AGENTS.md`, `docs/specs/runtime_contracts.md`, inspect working tree, use the smallest validation lane.
**CRITICAL**: Remote is `core-gitquarters.acbcontent.org`. Do not use GitHub/`gh` CLI. Use Forgejo tools/`gitea` CLI.
**CRITICAL**: Remote is `core-gitquarters.acbcontent.org`. Do not use GitHub/`gh` CLI. Do not use `tea` CLI. Use Gitea/Forgejo MCP tools.
**CI**: local-first — pre-push gates are mandatory; CI jobs run on the developer's local Mac Act runner, never on the Forgejo server (see `AGENTS.md` §CI/CD Runner Architecture).
Before non-trivial edits, apply the protocol in `AGENTS.md`.