## What Problem This Solves
Remove the blanket CODEOWNERS review routing to openclaw-secops, as requested by steipete and relayed by the author.
## User Impact
Security-related paths no longer automatically request secops code-owner review. Dependency Guard and Security Sensitive Guard remain unchanged, including dependency detection, lockfile autoscrub, comments/labels, and their SHA-bound approval commands. This does not remove dependency checks or change guard authorization.
## Why This Change Was Made
Remove only the secops CODEOWNERS block, the matching contribution restriction and stale lockfile-owner documentation, and two tests that require the retired CODEOWNERS entries. Keep steipete's ownership of CODEOWNERS and release-manager routing. Security scanning, dependency audits, and release approvals are untouched.
The earlier revision removed the guards too broadly; this revision restores them completely.
## Evidence
- All four guard suites pass: 59 tests.
- Both workflows, all three guard scripts, test routing, and guard script tests match the original baseline byte-for-byte.
- Two obsolete CODEOWNERS assertions removed; all guard behavior coverage retained.
- Targeted formatting, lint, and `git diff --check` pass.
- [Hosted CI](https://github.com/openclaw/openclaw/actions/runs/35324860885) failed in Telegram QA tooling: TS2353 at `scripts/mantis/run-request-telegram.mts:446` and four recorder tests whose fixture rejects `reply_to`. The failing caller, lease helper, recorder, fixture, and test are byte-identical between the actual CI merge `e1f02ecfae2b450fb4363c5205abd97c979c5aaa` and its main parent `c616fb4852ef9d6904427914bd75d2ba170b8146`. The required CI check remains red; no bypass or merge attempted.
## Compatibility
No runtime, configuration, SDK, GitHub ruleset, or environment changes. Both `/allow-*` guard commands retain their existing behavior.
Co-authored-by: Ayaan Zaidi <hi@obviy.us>
* fix(tooling): prevent accidental shared dependency installs
Stop creating implicit checkout-root dependency links during tool bootstrap.
Refuse default pnpm reconciliation through borrowed roots before linking,
while preserving explicit hydrated aliases, existing read-only borrows,
and configured-to-local toolchain fallback.
Include the early guard in package files and document its checkout-root
scope, lifecycle bypasses, and concurrent-path limits.
Validation: 127 focused Linux tests, seven real pnpm install cases,
packaged-root command proof, full checks plus final scoped loader checks,
and independent P0-P2 review.
* fix(tooling): audit install hook and align bootstrap coverage
Include the dependency ownership guard in the exact install lifecycle
contract and dependency fingerprint inputs so CI admits the hook and
invalidates cached dependencies when its implementation changes.
Update the existing wrapper expectation for the intentionally removed
implicit primary-checkout borrowing path while retaining hydration proof.
Validation: reproduced both failures, 517 workflow guards (2 existing
skips), 98 bootstrap/ownership tests, full scoped Linux checks, and
independent P0-P2 review.
* test(tooling): align isolated harness and routing contracts
Provision the copied Docker harness's TypeScript package explicitly and
update the preflight diagnostic and dedicated shim test routing expectations.
Validate compact tooling runner capacity from each resulting group's compiler
membership, preserving all file-policy and negative mutation checks without
freezing incidental compiler co-tenants onto a larger runner.
Validation: all 604 affected Linux tests, complete scoped checks, original
failure reproductions, planner inventory attribution and independent P0-P2
review. No production dependency or capacity policy changed in this follow-up.
* test(tooling): keep bootstrap cases in the runtime owner suite
Preserve all eight bootstrap cases and fixture logic in the existing local
runtime suite, with scoped environment cleanup and precise test routing.
The standalone filename fragmented the integrated GitHub compact plan into
81 jobs; the actual consolidated merge fits all three plans within80.
Keep the cap, estimates, compiler capacity, assertions and test coverage.
Validation: identical moved AST/token bodies, 571 local tests, 624 integrated
Linux tests and full scoped checks, exact merged planner proof, and clean
independent P0-P2 review.
* fix(runtime): require Node builds with lossless SQLite reads
* fix(runtime): preserve upgrades and guard sealed workers
Validate downloaded Node before switching the active runtime alias, reject unsupported sealed-worker runtimes, and keep the Gateway error fixture on a supported Node release. Document the approved ARMv7 and older macOS compatibility losses and decoder fix boundaries.
* test(runtime): use typed process exports in worker fixture
* test(runtime): align installer fixtures without growing test shards
* test(runtime): align release and guest runtime fixtures
* fix(test): canonicalize Windows temp roots for Node 24
Expand Windows short paths before creating test directories and owned child environments. Node 24 filesystem watchers otherwise abort when native long event paths differ from inherited short temporary paths. Preserve explicit custom-root spelling and existing cleanup ownership.
* test(ci): run Windows temp-root regressions in the native lane
Read the effective hooks path before initializing an unset selection in worktree scope. Preserve inherited and empty settings; let Git refuse shared initialization instead of changing sibling checkout configuration.
Fixes#139449. Seven real-Git regression cases fail before the repair; the final 15-case suite and scoped checks pass. Tooling net -15 LOC.
Align contributor guidance with the maintainer-requested release-only rule already recorded in AGENTS.md. Ordinary PRs and merges keep release-note context in PR bodies or commits; takeover permissions remain unchanged.
Add PR limits section explaining:
- 10 open PRs per author cap
- r: too-many-prs label auto-close mechanism
- How to get exception via #clawtributors Discord
Fixes: #38283