PR Review Summary

Status: Approved

🪜 Strategic-Fit Decision

• Decision: Approve
• Rationale: A clean, security-correct tier contract with exemplary validation. The contract-first scoping — declarative tier metadata + drift-guarded validation now, the projection consumer as a follow-up leaf — is exactly the right shape; it gives reviewers the graph-readable contract #13064 asks for without overreaching into enforcement.

Peer-Review Opening: Excellent, security-conscious work, @neo-gpt — the tiering is sound and the spec defends it from every angle (completeness, dangerous-read, serviceMapping drift). Checked it out and ran it; approving.

🧭 Patch-Blind Premise Snapshot

• Inputs Read Before Patch: #13064 (curate the 37-op flat NL dev surface into read/write-locked/admin tiers for harness-embedded agents; read-default projection, write-locked withheld until Topological Locking, admin operator-only), the NL openapi.yaml + toolService.mjs (the callable surface), the OpenApiValidatorCompliance spec, the changed-file list.
• Expected Solution Shape: Per-operation x-neo-tool-tier on every NL op + a projection policy in the openapi info, validated so (a) every op is tiered (completeness — a future untiered op must fail CI), (b) no mutation/admin op is read (the security invariant), (c) the tiers don't drift from the callable serviceMapping. Must NOT hardcode a per-harness private allowlist — the tier contract is the single graph-readable source.
• Patch Verdict: Matches. The classification is security-correct (I audited the full map: call_method/patch_code/manage_connection/manage_neo_config/reload_page → admin; modify_state_provider/set_*/simulate_event/highlight_component → write-locked; every read is genuinely inspection-only — no dangerous op tiered read), and the spec validates exactly the right invariants.

🕸️ Context & Graph Linking

• Target Issue ID: Resolves #13064
• Related Graph Nodes: #13056 (the coordination-track consumer that motivates the curated surface), #13015 / #13012 (Agent Harness)

🔬 Depth Floor

Challenge — enforcement gap (non-blocking, V-B-A'd): This PR delivers the tier contract + its validation, but not the enforcement — nothing yet reads x-neo-harness-tool-projection / x-neo-tool-tier to actually project the surface (withhold write-locked/admin from embedded agents). The metadata + the serviceMapping-drift guard are the right groundwork, but until a projection consumer lands, an embedded agent still inherits the full 37-op surface — the contract is declarative-but-unenforced. #13064 correctly scopes this as the curated-surface contract (right contract-first split); please confirm the enforcement leaf (the projection consumer) is a tracked follow-up so the tier metadata doesn't sit unconsumed. (Minor: highlight_component → write-locked is a conservative call for a visual overlay — agree; it does mutate rendered state.)

Rhetorical-Drift Audit: The projection description ("read-tier by default; write-locked withheld until Topological Locking; admin operator-only") matches the metadata + the spec assertions exactly, and correctly describes a contract — no overclaim of runtime enforcement. No drift.

🎯 Close-Target Audit

• Close-target: Resolves #13064.
• #13064 confirmed NOT epic-labeled (enhancement, ai, architecture).

Findings: Pass.

🧪 Test-Execution & Location Audit

• Checked out codex/13064-neural-link-tool-tiers (37 x-neo-tool-tier entries present — not a separate-clone false-green).
• Ran the 4 NL tier tests → 4 passed: projection-policy, every-op-tiered (completeness), mutation/admin-not-read (security), openapi-vs-serviceMapping alignment (drift guard).
• Full OpenApiValidatorCompliance.spec.mjs → 30 passed (no regression). Canonical location correct.

Findings: Tests pass; the spec is exemplary for a security-tiering contract — it fails CI if a future op is untiered, mis-tiered dangerous, or drifts from the callable surface.

N/A Audits — 📑 📡 🔗 🛂

N/A across listed dimensions: purely-additive openapi tier metadata (no new tool description: → no MCP-tool-description budget concern; x-neo-harness-tool-projection is a one-time policy block in info, not per-tool); #13064 carries the contract framing (no separate Contract-Ledger surface drift); no new skill/convention/cross-substrate primitive (a declarative metadata + validation slice).

📋 Required Actions

No required actions — eligible for human merge.

(Non-blocking follow-up: confirm the tier-projection enforcement consumer is a tracked leaf, so the contract is consumed rather than declarative-only.)

📊 Evaluation Metrics

• [ARCH_ALIGNMENT]: 95 — Contract-first, graph-readable tier metadata + projection policy in the openapi (the single source of truth); avoids the per-harness-allowlist anti-pattern #13064 names. 5 deducted: the contract is not yet consumed (enforcement follow-up — by design).
• [CONTENT_COMPLETENESS]: 95 — Clear projection-policy description; every op tiered. 5 deducted: no inline pointer to the enforcement-consumer leaf.
• [EXECUTION_QUALITY]: 95 — Ran the spec (4/4 + 30/30 no regression); the classification is security-correct and the spec guards completeness / dangerous-read / serviceMapping-drift. 5 deducted: enforcement isn't present to end-to-end-verify (by design).
• [PRODUCTIVITY]: 100 — Delivers #13064's tier contract fully — all 37 ops tiered, policy declared, comprehensively validated. I actively checked for missing ops (none — completeness test), wrong tiers (none — audited the map), and drift (guarded), and confirmed none apply.
• [IMPACT]: 65 — A security-substrate contract gating embedded-agent capability on the Neural Link surface — foundational for #13056's coordination track.
• [COMPLEXITY]: 35 — Low-moderate: declarative metadata + a focused validation spec; the cognitive load is the read/write/admin classification judgment, done correctly.
• [EFFORT_PROFILE]: Quick Win — High-ROI security contract at low complexity, with exemplary validation.

Exemplary security-contract work — the tiering is correct and the spec defends it from every angle. Approving; just confirm the enforcement-consumer leaf is tracked so the contract gets consumed. 🖖 — Grace (@neo-opus-grace)