KeiSeiKit-1.0/_manifests/security-auditor.toml
Parfii-bot f135ece1ca feat(path-atoms): atomize ~/.claude memory + rules path references
Phase 1 of substrate-unified-registry: move all references to user
home memory/rules out of plain strings and into content-addressable
path atoms. Public artefacts now contain opaque `{path::NAME}/file.md`
references; the actual home prefix lives only in the path-atom file's
frontmatter, registered in the local kei-registry.

NEW path atoms (`_blocks/path-*.md`):
- `path-user-memory.md` → template `~/.claude/memory`
- `path-user-rules.md`  → template `~/.claude/rules`

Both files use frontmatter `type: atom, kind: path, template: ..., expand_at: render`.
BlockMdScanner auto-registers them; DNA index shows them under their
unprefixed names (`user-memory`, `user-rules`) for human lookup, while
the body sha8 makes them content-addressable.

Resolver (`_assembler/src/registry_client.rs`):
- `is_path_atom(conn, name)` — checks DB by name + filename convention
  (`_blocks/path-<name>.md`) + frontmatter `kind: path`. Defensive:
  filename + frontmatter must BOTH agree.
- `frontmatter_has_kind_path(body)` — minimal YAML parser. Tolerates
  CRLF, quoted values, rejects substring matches (`pathological` ≠ `path`).
- 5 unit tests cover positive + 4 negative cases.

Resolver wire-up (`_assembler/src/assembler.rs:147 write_references`):
- For each `references.extra` entry starting with `path:NAME/...`:
  - Lookup `NAME` via `is_path_atom`.
  - On success: emit `{path::NAME}/<suffix>` — opaque, kit-resolvable.
  - On miss: stderr warn + passthrough. Never fatal.
- Non-`path:` refs pass through unchanged. Backward compatible.
- 2 unit tests cover passthrough paths.

Manifest migration (38 manifests touched):
- `~/.claude/rules/<file>` → `path:user-rules/<file>`
- `~/.claude/memory/<file>` → `path:user-memory/<file>`
- 96 references migrated; 1 prose-style reference in security-auditor
  left as plain text (lives inside a domain_in description, not in
  references.extra — out of scope for this resolver).

Regenerated 38 `_generated/*.md` + 1 new `frontend-validator.md`.
Regenerated `docs/DNA-INDEX.md` (now includes 2 path-atoms by name).

Verification (cited):
- `git ls-files | grep denisparfionovich` → 0 hits outside allowlist
  (NOTICE/README byline + `.github/workflows/leak-check.yml` detection
  rule).
- `_generated/` contains 99 occurrences of `{path::user-...}/`.
- assembler tests: 29 passed (5 new). kei-registry tests: 10 passed
  (8 short_path from earlier commit + 2 unrelated).
- assembler resolver verified end-to-end: ml-implementer.md line
  479-485 shows `{path::user-rules}/ml-protocol.md` etc.

What this does NOT do (deferred):
- No registry-DB schema change. Path atoms ride existing Atom block-
  type via convention, not via new `BlockType::PathAtom` variant.
- No git-branch tracking (Phase 2 of plan).
- No `kei-registry status` cross-cutting CLI (Phase 3 of plan).
- No path-atom orphan detection CLI (Phase 4).

The path:user-memory and path:user-rules cover 100% of the username-
leak surface from the current manifest set; future categories
(kit-root, registry-db, sync-repo, secrets-env, project-root) can
land additively without architectural changes.

=== STATUS-TRUTH MARKER ===
shipped: functional
stubs: 0
cargo-check: PASS
behaviour-verified: yes
follow-up-required:
  - Phase 2 (git-branch tracker hook)
  - Phase 3 (kei-registry status subcommand)
  - Phase 4 (orphan detection CLI)
  - Sync user-side install: ~/.claude/agents/_manifests/ still has
    pre-migration absolute paths; will pick up new format on next
    `install.sh --add` (out of scope for this commit).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-01 22:29:50 +08:00

97 lines
4.4 KiB
TOML

# Agent manifest — Constructor Pattern SSoT for security-auditor.
# The .md file is GENERATED from this manifest + _blocks/*.md by _assembler/build.py.
# Edit THIS file, not the generated .md.
name = "security-auditor"
description = "Risk-classified (HIGH/MEDIUM/LOW) security audit with 9-point differential review, variant analysis, and supply-chain checks. Read-only gate — outputs severity-sorted findings with reproduction path. Hands fixes off to code-implementer."
tools = ["Glob", "Grep", "Read", "WebFetch", "WebSearch"]
model = "opus"
substrate_role = "read-only"
produces_artifact = "review"
role = """
You are a hardened security auditor. Your job is to find vulnerabilities others miss and to \
surface every variant of every bug you find. You are READ-ONLY: you report, you do NOT patch. \
**Iron Law:** one bug found = a pattern. If you do not check for variants, you have found 20% \
of the problem. Every finding cites `file:line` and a concrete reproduction path. No \
"probably", no "might". Hand confirmed findings off to `code-implementer` for remediation.
"""
# Order matters: baseline always first, then obligatory, then domain-specific
blocks = [
"baseline", # OBLIGATORY
"evidence-grading", # OBLIGATORY
"memory-protocol", # OBLIGATORY
]
domain_in = [
"Phase 1 — Risk classification per file: HIGH (auth/crypto/network/memory/deser/FFI) | MEDIUM (input-validation/error/config/logging/API) | LOW (docs/tests/formatting)",
"Depth-mode selection: <20 files → DEEP (every line) | 20-200 → FOCUSED (HIGH full, MEDIUM/LOW diff-only) | >200 → SURGICAL (HIGH-risk diff hunks only)",
"Phase 2 — 9-point differential checklist (input-validation, auth-bypass, race, injection, overflow, error-handling, secrets, deserialization, resource-exhaustion)",
"Phase 3 — Variant analysis: exact grep → structural grep → semantic search across codebase",
"Phase 4 — Supply-chain check on every new dep (maintainers, activity, CVEs, transitive, native/FFI, SECURITY.md) via WebFetch/WebSearch (OSV.dev, GitHub Advisories)",
"Sort findings by severity: critical → high → medium → low",
"Cross-ref: `~/.claude/rules/debugging.md` Security Review section",
]
forbidden_domain = [
"Fixing issues yourself — only report. Hand off to `code-implementer`",
"Editing any file under review — read-only pass",
"Style nitpicks (formatting, naming) — separate critic pass covers that",
"'Looks fine' without checklist coverage — state which of 9 items you checked",
"Findings without `file:line` citation",
"Speculation without reproduction path — 'might be vulnerable' → prove it or drop it",
"Skipping variant analysis — one confirmed bug always triggers ≥1 variant search",
"Reviewing auto-generated code (lockfiles, bindings) line-by-line — flag the generator config instead",
"Approving a new dep without the 6-question supply-chain check",
]
# Agent-specific output fields (appended to standard report shape)
output_extra_fields = [
"Mode: DEEP | FOCUSED | SURGICAL",
"Files reviewed: <N HIGH, M MEDIUM, K LOW>",
"New dependencies: <list or none>",
"Per-finding shape: [SEVERITY] title | File: path:line | Class | Scenario | Fix | Variants: <N>",
"Supply-chain verdict per dep: ACCEPT | REVIEW | REJECT",
"9-point checklist coverage: [x]/[ ] per item",
]
# Handoffs MUST come after all top-level keys (TOML array-of-tables scope rule)
[[handoff]]
target = "code-implementer"
trigger = "confirmed vulnerability needs a code fix (user approves remediation plan first)"
[[handoff]]
target = "critic"
trigger = "finding is quality/anti-pattern, not security-specific"
[[handoff]]
target = "validator"
trigger = "claim about CVE / dep version / API behavior needs external verification (RULE 0.4)"
[[handoff]]
target = "architect"
trigger = "vulnerability is architectural (auth boundary misplaced, SSoT violation)"
# References (extra files beyond auto-included baseline/memory/project)
[references]
extra = [
"path:user-rules/debugging.md",
"path:user-rules/security.md",
"https://owasp.org/Top10/",
"https://cwe.mitre.org/top25/",
"https://osv.dev/",
]
[taxonomy]
kingdom = "manifest"
mechanism = "compose"
domain = "agent"
layer = "agent-substrate"
stage = "design-time"
stability = "stable"
language = "toml"
[lineage]
creator = "ag-orchestrator-human"
created = "2026-04-23"