zetetic-team-subagents

There is a documented upgrade path and the project keeps it working. https://github.com/cdeust/zetetic-team-subagents/blob/main/docs/MIGRATION.md gives a five-step adoption path for an existing non-compliant project, from permissive through standard to strict. Version currency is enforced rather than assumed: https://github.com/cdeust/zetetic-team-subagents/blob/main/tools/plugin-version-check.sh compares installed, pinned and released versions and names which of the two possible lags applies and who fixes it, and it runs at session start. Upgrade-relevant changes are called out per release in https://github.com/cdeust/zetetic-team-subagents/blob/main/CHANGELOG.md

GitHub Issues: https://github.com/cdeust/zetetic-team-subagents/issues

No vulnerability has been resolved in the last 12 months, so there is no reporter to credit. The commitment is documented: reporters are credited in the release notes for the patched version unless they request anonymity. https://github.com/cdeust/zetetic-team-subagents/blob/main/SECURITY.md

https://github.com/cdeust/zetetic-team-subagents/blob/main/SECURITY.md documents the whole response process: the private advisory channel, what a report must contain, a per-severity SLA table (24 hours first response and 7 days to patch for critical, 3 and 14 days for high), a five-step disclosure timeline with a 30-day default coordinated date, and what is out of scope.

The standard is a document in the tree, not a preference: https://github.com/cdeust/zetetic-team-subagents/blob/main/rules/coding-standards.md covers SOLID, the layer dependency rule, size limits, dependency injection, local reasoning, source discipline, mutation testing, the definition of done and the boy-scout rule, each with its primary source. CONTRIBUTING.md names it as binding and excerpts the load-bearing rules: https://github.com/cdeust/zetetic-team-subagents/blob/main/CONTRIBUTING.md

Enforced automatically at two points. At commit time https://github.com/cdeust/zetetic-team-subagents/blob/main/hooks/pre-commit-zetetic.sh runs tools/zetetic-checker.sh on the staged diff and returns exit 2 on a violation. In CI four hard gates block the merge (https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/workflows/ci.yml): the craftsmanship checker on newly added files, the redaction sweep on the full tree under ZETETIC_PROFILE=strict, the tools regression suite, and shellcheck at error severity. The ratchet shape (new files gated, legacy debt reported) is documented in the workflow itself.

No native binaries are generated. There is no compiler or linker invocation anywhere in the project, so CC, CFLAGS and LDFLAGS have nothing to apply to.

There is no build or installation system that strips anything. The software is Markdown and scripts, installed by copying, and the source on disk is what runs.

There is no build system, so there are no subdirectory builds to make recursive or otherwise.

Although nothing is compiled, the one thing that is generated is bit-for-bit reproducible by construction. https://github.com/cdeust/zetetic-team-subagents/blob/main/tools/build-release-bundle.sh creates the release tarball with --sort=name --mtime=@0 --owner=0 --group=0 --numeric-owner, so the archive does not depend on filesystem order, timestamps or the building user. The script says why: an attestation over a non-deterministic archive proves nothing a second builder can check.

Installed and uninstalled through the ecosystem's package manager: "claude plugin marketplace add cdeust/zetetic-team-subagents" then "claude plugin install zetetic-team-subagents" (https://github.com/cdeust/zetetic-team-subagents#install). The manual path is https://github.com/cdeust/zetetic-team-subagents/blob/main/scripts/setup.sh with install, update, uninstall and configure verbs, and the installer writes a manifest so that uninstall removes exactly what it added.

There is no installation system that writes built artifacts to a configurable prefix. Installation copies agents, skills, hooks and tools into the host's own plugin directory under ~/.claude, which is the convention the host defines, so DESTDIR and similar variables have nothing to select.

git clone and the software is complete: nothing is compiled and there are no dependencies to resolve. https://github.com/cdeust/zetetic-team-subagents/blob/main/CONTRIBUTING.md lists the prerequisites (bash 4+, GNU coreutils, ripgrep, python3) and https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/workflows/ci.yml gives the exact command for every suite, which is the same command a developer runs locally. The stale command list inside CONTRIBUTING is being corrected under issue #73.

Listed in two computer-processable forms. Every release publishes a CycloneDX SBOM (zetetic-team-subagents.cdx.json) inventorying every bundled file with its hash, including the vendored third-party skill material, alongside an EXECUTABLE-MANIFEST.sha256 that enumerates every hook and tool that will run on the user's machine (https://github.com/cdeust/zetetic-team-subagents/blob/main/SECURITY.md). The only external supply-chain surface, the GitHub Actions, is declared in https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/dependabot.yml and each action is pinned to a full commit SHA in the workflows.

https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/dependabot.yml runs weekly against the github-actions ecosystem, which is this project's only external dependency surface: there is no runtime package to install, so there is no pip or npm manifest to watch, and the config states that reasoning rather than declaring an empty ecosystem. Dependabot updates the pinned SHA and rewrites the version comment in place, so pinning discipline is preserved automatically. OpenSSF Scorecard runs on a schedule on top of it (https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/workflows/scorecard.yml), with each finding's disposition recorded in https://github.com/cdeust/zetetic-team-subagents/blob/main/docs/SCORECARD.md

Reused components are identifiable and updateable. The GitHub Actions are pinned by full commit SHA with a version comment and updated by Dependabot weekly. The Python code imports only the standard library, so there is no vendored runtime dependency to go stale. The one convenience copy, the vendored writing and redaction rule material, carries its provenance in the file and is inventoried in the per-release CycloneDX SBOM.

The technology stack is current and nothing deprecated is relied on. The Python is standard library only (argparse, hashlib, json, ssl, subprocess, urllib, xml.etree, tempfile) with no deprecated or removed module, and CI pins Python 3.12. The shell targets bash 4+ with POSIX coreutils, and shellcheck at error severity would flag obsolete constructs on every push.

Every push to main and every pull request runs the full gate set and reports pass or fail per job: seven jobs in https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/workflows/ci.yml (memory suites, agent auditor, worktree tests, zetetic checker, craftsmanship checker, redaction sweep, tools regression suite covering 16 suites), plus shellcheck and CodeQL in their own workflows. Four of them are hard gates that block the merge. The Python pytest suites are the one part not yet wired into CI, tracked in issue #71.

Well above 50 percent, because the standard makes it mandatory: rules/coding-standards.md section 13.1 G2 requires every bug fixed in a pull request to carry a regression test that fails on the pre-fix code. Recent fixes follow it: issue #64 (redaction-checker missing untracked files) shipped with the test that reproduces the false local pass, and issue #60's CodeQL fix was made structural so the checker itself is the regression guard. https://github.com/cdeust/zetetic-team-subagents/blob/main/rules/coding-standards.md

A formal written policy exists. rules/coding-standards.md section 13.1 A1 to A3 requires happy paths, every enumerated edge case and every failure path (including the emission of the signal itself) to map to a test, and section 13.2 makes the mapping a required artifact of the pull request. Section 13.3 enumerates the refusals, including that classifying a coverage gap in new code as a follow-up is blocking. https://github.com/cdeust/zetetic-team-subagents/blob/main/rules/coding-standards.md

CONTRIBUTING.md states it for hooks ("Changes to that hook need a corresponding test in tests/") and rules/coding-standards.md section 13 states it generally, with the Completion Ledger as the mechanism that makes it checkable in review. https://github.com/cdeust/zetetic-team-subagents/blob/main/CONTRIBUTING.md and https://github.com/cdeust/zetetic-team-subagents/blob/main/rules/coding-standards.md

Maximally strict for the languages in use. shellcheck runs at error severity over every shell file in hooks/ and tools/ with no "|| true" escape, so a single finding fails the job: see the step "ShellCheck (error severity - hard gate)" in https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/workflows/shellcheck.yml. CodeQL runs the widest query pack, security-and-quality, rather than the default security-only pack. The redaction sweep runs under ZETETIC_PROFILE=strict, which promotes every finding to exit 1 (https://github.com/cdeust/zetetic-team-subagents/blob/main/.github/workflows/ci.yml). Warning severity for shellcheck is currently informational, with the backlog measured and scheduled in issue #74.

The principles are implemented, with one stated exception. Fail-safe defaults: the memory ACL denies any write outside a scope's owner list and tools/manifest_gate.py rejects an ungrounded source with exit 3. Separation of privilege: the release job holds only id-token and attestations write, everything else is contents: read. Open design: the enforcement surface and its documented limits are public (https://github.com/cdeust/zetetic-team-subagents#what-this-system-does-not-do). Economy of mechanism: web_ingest, manifest_gate and semantic_layer import none of each other and are wired by a skill, so each is independently testable. The exception is complete mediation at one tool boundary, described under input_validation below.