diff --git a/CLAUDE.md b/CLAUDE.md index 711e60e..f643427 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -106,7 +106,8 @@ The ONLY allowed system APIs are: `isu` is the issue and project tracking tool for this repository and shall always be used for issue/project work. Do not use Tangled issue commands or any -other issue tracker. Tangled is only used for pull request operations. +other issue tracker. All work merges directly to `main`; this project does not +use pull requests. The `.isu/` directory is issue/project tracker state. Any `.isu` change made by creating, updating, labelling, or closing issues must be committed and pushed; @@ -127,9 +128,16 @@ never leave `.isu` changes local-only. If you fix a bug the harness exposed, add a scenario asserting the new behaviour. If you spot a new bug, file an `isu` issue with the `e2e-smoke` label (see "E2E Harness" section). -8. Commit and push code changes and any `.isu/` tracker changes -9. Create PR via tangled: `tangled pr create --title "..." --body "..."` -10. After merge, clean up: `git worktree remove ../we-` +8. Close the issue: `isu issue close ` +9. Commit all code changes and `.isu/` tracker changes; reference `isu issue ` in the message +10. Merge into main and push: + ```sh + cd /Users/piefev/misc/we + git checkout main + git merge + git push origin main + ``` +11. Clean up: `git worktree remove ../we- && git branch -d ` ## Tracking CLI Cheat Sheet @@ -140,11 +148,6 @@ isu issue create --title "..." --body "..." isu issue show isu issue close -# Pull requests only -tangled pr list -tangled pr create --title "..." --body "..." -tangled pr show - # Repo tangled repo show ``` diff --git a/README.md b/README.md index 9e6cfdd..8c2d720 100644 --- a/README.md +++ b/README.md @@ -7,8 +7,8 @@ Zero external crate dependencies. Pure Rust for everything — crypto, TLS, font ## Project Tracking `isu` is the issue and project tracking tool for this repository and shall -always be used for issue/project work. Tangled is used only for pull requests, -not issues. +always be used for issue/project work. All work merges directly to `main`; +this project does not use pull requests. The `.isu/` directory is tracker state. Commit and push every `.isu/` change made by creating, updating, labelling, or closing issues. diff --git a/implementor b/implementor index 26af1b3..f8cf2ed 100755 --- a/implementor +++ b/implementor @@ -24,10 +24,10 @@ PROMPT = r""" You are an autonomous implementation agent for the `we` browser engine project. The git root is at /Users/piefev/misc/we. Always start by reading /Users/piefev/misc/we/CLAUDE.md and /Users/piefev/misc/we/PLAN.md. -The project is hosted on Tangled, but issue and project tracking has migrated to -the local `isu` tracker. `isu` is the only issue/project tracking tool that -shall be used. Use `isu` for every issue/project operation and `tangled` only -for pull request operations. +The project is hosted on Tangled, but issue and project tracking lives in the +local `isu` tracker. `isu` is the only issue/project tracking tool that shall +be used. All work merges directly to `main`; this project does not use pull +requests. The `.isu/` directory is issue/project tracker state. Whenever `isu` creates, updates, labels, or closes an issue, commit and push the resulting `.isu/` @@ -37,65 +37,7 @@ Your job is to pick ONE task, complete it fully, and then exit. Follow this prio --- -## Priority 1: Open Pull Requests - -Check for open PRs: -``` -tangled pr list --repo pierrelf.com/we -``` - -If there are open PRs, pick the first one and: - -1. Read the PR details: `tangled pr show ` -2. Read the diff: `tangled pr show --diff` -3. Read comments: `tangled pr show --comments` -4. Fetch and create a local worktree to review: - ``` - cd /Users/piefev/misc/we - git fetch origin - git worktree add ../we-pr-review - ``` -5. Review the pull request meticulously. Read every changed file. Check for: - - Correctness and logic errors - - Style and convention violations from CLAUDE.md - - Missing error handling or tests - - Dead code, unused imports - - `unsafe` outside of allowed crates: platform, crypto, js - - Any external crate dependencies -6. Fix any issues you find by editing files in the worktree. -7. Run the completion checklist: - ``` - cd ../we-pr-review - cargo fmt --all - cargo clippy --workspace -- -D warnings - cargo test --workspace - ``` - If the PR touches parsing, styling, layout, rendering, the UA stylesheet, - forms, scripting, SVG, canvas, or anything user-visible, also run the e2e - smoke suite and visually inspect the screenshots: - ``` - cargo run -p we-e2e -- --scenario crates/e2e/scenarios/smoke.we --out-dir crates/e2e/artifacts - ``` - If the harness exposes an unrelated pre-existing bug, file it as a separate - `isu` issue with the `e2e-smoke` label rather than blocking the PR, then - commit and push the resulting `.isu/` changes. -8. Commit and push fixes if any, including any `.isu/` tracker changes. -9. If everything passes and the code is good, merge it: - ``` - tangled pr merge - ``` -10. Clean up: - ``` - cd /Users/piefev/misc/we - git worktree remove ../we-pr-review 2>/dev/null - git pull - ``` - -After completing the PR review, exit. - ---- - -## Priority 2: Open Issues +## Priority 1: Open Issues Check for open issues: ``` @@ -160,10 +102,10 @@ After merging to main, exit. --- -## Priority 3: Create Issues for the Next Phase +## Priority 2: Create Issues for the Next Phase -If there are no open PRs AND no open issues, the current phase is complete. -Read PLAN.md to determine what comes next: +If there are no open issues, the current phase is complete. Read PLAN.md to +determine what comes next: 1. Read `/Users/piefev/misc/we/PLAN.md` and identify the next uncompleted phase. 2. Break that phase down into concrete, actionable issues. @@ -171,7 +113,7 @@ Read PLAN.md to determine what comes next: ``` isu issue create --title "" --body "<detailed description with acceptance criteria>" --label "phase-N" ``` -4. Each issue should be self-contained and implementable in a single PR. +4. Each issue should be self-contained and implementable in a single merge to main. 5. Order issues so dependencies come first. 6. Commit and push the resulting `.isu/` changes: ``` @@ -188,7 +130,7 @@ up the first issue. ## Important Rules - Only do ONE task per invocation, then exit. -- For issue implementations, merge directly to main; do not create a PR. +- Merge issue implementations directly to main; this project does not use pull requests. - Always work in git worktrees, never directly on main. - Always run the completion checklist before pushing. - `isu` is the only issue/project tracker. Never use Tangled issue commands.