An agent-managed museum exhibit, built in Rust with Gajae-Code / LazyCodex — developed and maintained with no human intervention.
Rust
Record why issue reconciliation is evidence-gated
bellman6f73103bf1a3
diff --git a/docs/pr-issue-resolution-gate.md b/docs/pr-issue-resolution-gate.mdindex 236f8377..97dd513e 100644--- a/docs/pr-issue-resolution-gate.md+++ b/docs/pr-issue-resolution-gate.md@@ -42,15 +42,77 @@ The anti-slop classifications are: `actionable-bug`, `actionable-docs`, `actionaAutomation lanes may recommend labels, comments, defer/close rationales, or merge candidates, but must not merge or close remote PRs/issues without maintainer-owned approval.-## G012 final PR reconciliation snapshot--Worker-3 captured a fresh PR ledger for the final Claw Code 2.0 gate in `docs/pr-triage-g012-final-gate.json`.--- Captured on: 2026-05-15T02:58:00Z during G012 final-gate execution.-- Commands: `gh pr list --state open --limit 100 ...` plus `gh pr view <number> ...` for per-PR file and merge-state evidence.-- Observed count: 51 open PR records.-- Merge action taken by worker-3: none. The safety policy requires correct, safe, non-conflicting, resolvable PRs with evidence; this snapshot found 32 PRs in `CONFLICTING`/`DIRTY` state and 19 `MERGEABLE` PRs that GitHub reported as `UNSTABLE` with no fresh check-rollup evidence in the live snapshot.-- Docs-only candidate-review PRs: #3021 and #2824 remain deferred until content/source-of-truth review and fresh verification are available.+## G012 W4 live issue reconciliation snapshot++A fresh, non-mutating issue snapshot was captured for the G012 final gate from+this worker worktree. The claim-safe task lifecycle is currently blocked because+team task `5` is assigned to Worker-4 in the description but still has+`owner: worker-1`; therefore this worker did **not** close, label, comment on,+or otherwise mutate remote issues from this lane.++Fresh commands run from `origin https://github.com/ultraworkers/claw-code` on+HEAD `2e93264`:++- `gh issue list --state open --limit 5000 --json number --jq 'length'` →+ `1350` open issues.+- `gh pr list --state open --limit 5000 --json number --jq 'length'` →+ `51` open PRs.+- `gh issue list --state open --limit 5000 --json number,title,createdAt,updatedAt,labels,author,url`+ captured the issue metadata used for the classification below.++### Issue classification ledger++| Bucket | Count | Representative issues | Final-gate action | Rationale / evidence |+| --- | ---: | --- | --- | --- |+| Recent external actionable review | 9 | #3039, #3023, #3022, #3020, #3007, #3006, #3005, #3004, #3003 | Defer/route with evidence; do not close automatically | These are real user reports or proposals. Existing G002/G009/G010/G011 work covers parts of #3007, #3004/#3033, #3039, and provider/docs items, but maintainer approval is required before closing remote issues. |+| Owner-authored roadmap/docs/feature trackers | 11 | #3038, #3037, #3036, #3035, #3034, #3033, #3032, #3031, #3030, #3029, #3028 | Mark as linked to G009-G011 evidence or defer as roadmap | The repo now has docs for navigation/file context, local OpenAI-compatible providers and skills, Windows install/release, ACP/Zed/JSON-RPC status, and ecosystem ops UX. Items that request future product surfaces (provider setup wizard, auto-compact retry, `claw serve`, marketplace) remain roadmap/deferred rather than safe final-gate closures. |+| Older potentially actionable issues | 11 | #2980, #2979, #2820, #2819, #1601, #933, #416, #375, #32, #31, #5 | Defer for owner batch triage | These need maintainer/product decisions or separate repro work. Some are broadly addressed by current docs/policy files, but closing them from an automation lane would overclaim. |+| Spam or low-signal flood | 628 | Repeated `经验+3`, `合影`, WeChat/QQ group ads, promotional links | Close/label only under maintainer-owned bulk moderation | These are not Claw Code engineering work and are safe candidates for spam/invalid moderation, but this worker did not mutate remote state. |+| Older low-signal or owner-triage-needed | 691 | #2997 plus many March 2026 low-context comments/promotions/questions | Defer for maintainer-owned bulk triage | Mixed low-signal and unclear reports remain open. They are not safely resolvable by code changes in this final gate without per-issue owner policy decisions. |++### Correct/resolvable issue findings++- #3039 (`How to install skills?`) is addressed by current docs in+ `USAGE.md` and `docs/local-openai-compatible-providers.md`, which document+ `/skills install <path>`, `/skills list`, discovered names, local skill roots,+ and provider credential checks. Closure should wait for maintainer confirmation+ or a response to the reporter.+- #3038 is intentionally deferred: `docs/g011-ecosystem-ops-ux-verification-map.md`+ records marketplace/plugin boundaries and the explicit remote marketplace+ deferral after core UX stabilization.+- #3037 and #3036 are addressed by README/USAGE links plus+ `docs/local-openai-compatible-providers.md`, including Ollama, llama.cpp,+ vLLM, OpenAI-compatible routing, and multi-provider positioning.+- #3035 is partially addressed by `/resume latest` docs and+ `docs/g010-session-hygiene-verification-map.md`; any remaining compacted+ session UX work should stay linked to the session-hygiene roadmap rather than+ be auto-closed.+- #3033/#3004 are addressed only as explicit deferrals by+ `docs/g011-acp-json-rpc-status-contract.md`; no ACP/Zed daemon or JSON-RPC+ engine API is claimed yet.+- #3032/#3030/#3005/#3020 remain provider-diagnostics/setup follow-ups.+ Existing provider docs reduce support ambiguity, but final-gate automation+ should not claim remote closure without reproductions or maintainer sign-off.+- #3007 has regression coverage in `tests/test_security_scope.py` and+ `rust/crates/runtime/src/file_ops.rs`; closure still requires maintainer review+ because the live issue can include shell-expansion edge cases beyond the+ covered symlink/path-scope tests.+- #3003 should be checked against repository ignore/source-control policy before+ closure; this worker did not find or make a code change in the claimed lane.++### Remote-action gate++No issue was closed, labeled, or commented on by this worker. The safe final-gate+recommendation is:++1. Maintainer/leader fixes the Worker-4 task claim conflict before any further+ lifecycle transition.+2. Close or label the 628 spam/low-signal issues in a maintainer-owned bulk+ moderation lane.+3. Link #3039/#3037/#3036/#3028 to the merged docs evidence if maintainers+ agree the docs answer the reports.+4. Keep future-product items (#3038, #3033, #3031, #3030, #3004) open or move+ them to a roadmap/project board with explicit deferral rationale.## Required final evidence