You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs(contributing): Known Issues Sweep references a known_issues/ directory this repo doesn't have #138
CONTRIBUTING.md's 'Known Issues Sweep' section (copied from the monorepo during the split) requires a known_issues/_.md entry plus a GitHub issue, but this repo has no known_issues/ directory; deferred work is tracked in GitHub issues only (CLAUDE.md says so since #137). Either update CONTRIBUTING.md to say GitHub issues are the tracker here, or create known_issues/ and move to that model. The same check applies to LeanerCloud/cloud-commitments-mcp, which also has no known_issues/. Raised by CodeRabbit on #137.
Decision needed (one line): is the tracker GitHub issues only, or known_issues/ plus issues? CONTRIBUTING.md (~:242-308) still mandates known_issues/, CLAUDE.md says the directory does not exist, and it now does (known_issues/01_gcp_compute_nonroot_term.md, edited by open PR #307). Either way the fix is a 30-60 line docs edit. Marking status/needs-info.
Activity
cristim commentedon Oct 17, 2026
Decision needed (one line): is the tracker GitHub issues only, or
known_issues/plus issues?CONTRIBUTING.md(~:242-308) still mandatesknown_issues/, CLAUDE.md says the directory does not exist, and it now does (known_issues/01_gcp_compute_nonroot_term.md, edited by open PR #307). Either way the fix is a 30-60 line docs edit. Markingstatus/needs-info.