Merge pull request #5 from patterninc/chore/interface-aidlc-cleanup

Align Code Mint with interface outcomes

Author: jacob-pattern

.agents/code-mint-status.json

@@ -1,8 +1,9 @@
 {
-  "code_mint": "1.0",
+  "code_mint": "1.1",
   "scope": ".",
   "onboarded_at": null,
   "last_validated": null,
+  "heritage": null,
   "outcomes": {
     "validate_current_state": { "status": "Not Started", "date": null },
     "navigate": { "status": "Not Started", "date": null },

…ts/skills/autonomy--env-auditor/SKILL.md …nts/skills/autonomy-env-auditor/SKILL.md.agents/skills/autonomy--env-auditor/SKILL.md renamed to .agents/skills/autonomy-env-auditor/SKILL.md .agents/skills/autonomy--env-auditor/SKILL.md renamed to .agents/skills/autonomy-env-auditor/SKILL.md

@@ -1,12 +1,21 @@
 ---
-name: autonomy--env-auditor
-description: Audit whether a repository's environment variable configuration allows an agent to load all required .env variables from scratch. Use when evaluating a new repository's agent-readiness, when environment loading fails during agent setup, or as part of an initial harness assessment. Do not use when .env files already load correctly and the goal is to add a single new variable, or when creating env loading capability (use autonomy--env-creator).
+name: autonomy-env-auditor
+description: Audit whether a repository's environment variable configuration allows an agent to load all required .env variables from scratch. Use when evaluating a new repository's agent-readiness, when environment loading fails during agent setup, or as part of an initial harness assessment. Do not use when .env files already load correctly and the goal is to add a single new variable, or when creating env loading capability (use autonomy-env-creator).
 ---
 
 # Environment Auditor
 
 Evaluate whether an agent can configure and load all required environment variables from a cold start — with zero pre-existing `.env` files or manual setup.
 
+## Discipline
+
+This auditor follows code-mint's shared auditor discipline:
+
+- **Depth option** — default `standard`; use `quick` for a sanity check on a recently audited repo or `deep` for legacy codebases, quarterly refreshes, or high-risk readiness claims. Heritage classification from `meta-onboarding` Phase 0 sets a sensible default.
+- **Calibration** — every report ends with a Calibration section naming the depth used, confidence level, what was not checked, and what would raise confidence. This is a required artifact, not a disclaimer.
+
+This discipline is inspired by AWS AI-DLC's adaptive-depth and overconfidence-prevention ideas, but code-mint does not vendor or implement the full AI-DLC workflow.
+
 ## Step 1: Discover Environment Requirements
 
 1. **Find all environment variable references** in the codebase:
@@ -60,7 +69,7 @@ Ensure the report directory exists: `mkdir -p .agents/reports/completed && touch
 
 Ensure `.gitignore` ignores generated report contents while preserving the directories with their `.gitkeep` files.
 
-Write the report to `.agents/reports/autonomy--env-auditor-audit.md`:
+Write the report to `.agents/reports/autonomy-env-auditor-audit.md`:
 
 ```
 # Environment Audit Report
@@ -87,13 +96,21 @@ Write the report to `.agents/reports/autonomy--env-auditor-audit.md`:
 - **Current State:** [what exists]
 - **Required State:** [what should exist]
 - **Recommended Action:** [specific step]
-- **Next Skill / Step:** [e.g., Run `autonomy--env-creator`]
+- **Next Skill / Step:** [e.g., Run `autonomy-env-creator`]
 
 ## Cold Start Blockers
 [List of variables that prevent application startup]
 
 ## Next Steps
-Run `autonomy--env-creator` to remediate findings.
+Run `autonomy-env-creator` to remediate findings.
+
+## Calibration
+**Depth:** [quick / standard / deep]
+**Confidence:** [High / Medium / Low] — [one-sentence reason]
+**Not checked:**
+- [specific area + reason]
+**To raise confidence:**
+- [specific next step]
 ```
 
 After writing the report, update `docs/onboarding-checklist.md` and `.agents/code-mint-status.json` with the current `smoke_path` outcome status and date. Optionally update `docs/skills-status.md` if the repository keeps the compatibility view.

…ts/skills/autonomy--env-creator/SKILL.md …nts/skills/autonomy-env-creator/SKILL.md.agents/skills/autonomy--env-creator/SKILL.md renamed to .agents/skills/autonomy-env-creator/SKILL.md .agents/skills/autonomy--env-creator/SKILL.md renamed to .agents/skills/autonomy-env-creator/SKILL.md

@@ -1,17 +1,17 @@
 ---
-name: autonomy--env-creator
-description: Creates the capacity for an agent to load all environment variables from scratch, based on the output of autonomy--env-auditor. Use when an env audit report exists and environment loading needs to be remediated. Do not use when no audit report exists (run autonomy--env-auditor first) or when debugging a single missing variable.
+name: autonomy-env-creator
+description: Creates the capacity for an agent to load all environment variables from scratch, based on the output of autonomy-env-auditor. Use when an env audit report exists and environment loading needs to be remediated. Do not use when no audit report exists (run autonomy-env-auditor first) or when debugging a single missing variable.
 ---
 
 # Environment Creator
 
-Build out a repository's environment variable configuration so that an agent (or new developer) can go from zero to a fully configured `.env` in a single command. Based on findings from `autonomy--env-auditor`.
+Build out a repository's environment variable configuration so that an agent (or new developer) can go from zero to a fully configured `.env` in a single command. Based on findings from `autonomy-env-auditor`.
 
 Prefer one documented bootstrap path that writes local env config from the repo's real source of truth. In many repos that is `scripts/env.sh`. A `.env.example` file can still exist, but it should be secondary.
 
 ## Prerequisites
 
-Read the audit report at `.agents/reports/autonomy--env-auditor-audit.md`. If no report exists, instruct the user to run `autonomy--env-auditor` first.
+Read the audit report at `.agents/reports/autonomy-env-auditor-audit.md`. If no report exists, instruct the user to run `autonomy-env-auditor` first.
 
 Before changing anything:
 
@@ -242,5 +242,5 @@ Update the project's AGENTS.md and/or README to include:
 3. Start the application and verify it boots successfully.
 4. If generation or startup verification fails, keep the old `.env` in place or restore it from the backup before trying again.
 5. If a `.env.example` file exists, keep it as a reference or compatibility file only. Point it to the primary bootstrap path if helpful.
-6. Archive the audit report to `.agents/reports/completed/autonomy--env-auditor-audit-{YYYY-MM-DD}.md`.
+6. Archive the audit report to `.agents/reports/completed/autonomy-env-auditor-audit-{YYYY-MM-DD}.md`.
 7. Update `docs/onboarding-checklist.md` and `.agents/code-mint-status.json` with the current `smoke_path` outcome status and date. Optionally update `docs/skills-status.md` if the repository keeps the compatibility view.

…ts/skills/autonomy--sre-auditor/SKILL.md …nts/skills/autonomy-sre-auditor/SKILL.md.agents/skills/autonomy--sre-auditor/SKILL.md renamed to .agents/skills/autonomy-sre-auditor/SKILL.md .agents/skills/autonomy--sre-auditor/SKILL.md renamed to .agents/skills/autonomy-sre-auditor/SKILL.md

@@ -1,6 +1,6 @@
 ---
-name: autonomy--sre-auditor
-description: Audit whether an agent has working access to the SRE CLIs the project uses — version control host CLI, cloud provider CLI, and observability CLI. Tests each connection and reports access gaps. The steps below use GitHub CLI, AWS CLI, and Datadog Pup as a worked example; adapt for your project's actual tooling. Use when setting up a new agent environment, troubleshooting tool access, or as part of an initial harness assessment. Do not use when debugging a specific production issue (use autonomy--sre-agent) or when auditing general runtime readiness (use autonomy--runtime-auditor).
+name: autonomy-sre-auditor
+description: Audit whether an agent has working access to the SRE CLIs the project uses — version control host CLI, cloud provider CLI, and observability CLI. Tests each connection and reports access gaps. The steps below use GitHub CLI, AWS CLI, and Datadog Pup as a worked example; adapt for your project's actual tooling. Use when setting up a new agent environment, troubleshooting tool access, or as part of an initial harness assessment. Do not use when debugging a specific production issue (use interface-sre-agent) or when auditing general runtime readiness (use autonomy-staging-auditor).
 ---
 
 # SRE Auditor
@@ -9,6 +9,15 @@ Verify that an agent has authenticated, working access to the CLI tools required
 
 The steps below use **GitHub CLI, AWS CLI, and Datadog Pup** as a reference profile. If your project uses a different VCS host (e.g., GitLab, Azure DevOps), cloud provider (e.g., GCP, Azure), or observability platform (e.g., Grafana, New Relic, Prometheus), substitute the equivalent CLI and read-only verification commands while following the same audit structure.
 
+## Discipline
+
+This auditor follows code-mint's shared auditor discipline:
+
+- **Depth option** — default `standard`; use `quick` for a sanity check on a recently audited repo or `deep` for legacy codebases, quarterly refreshes, or high-risk readiness claims. Heritage classification from `meta-onboarding` Phase 0 sets a sensible default.
+- **Calibration** — every report ends with a Calibration section naming the depth used, confidence level, what was not checked, and what would raise confidence. This is a required artifact, not a disclaimer.
+
+This discipline is inspired by AWS AI-DLC's adaptive-depth and overconfidence-prevention ideas, but code-mint does not vendor or implement the full AI-DLC workflow.
+
 ## Step 1: Audit GitHub CLI Access
 
 ### Check Installation
@@ -107,15 +116,15 @@ For each monitoring tool, verify that output is machine-readable:
 - [ ] Traces connect requests across services
 - [ ] Error context includes stack traces, request IDs, and relevant input data
 
-Machine-readable telemetry is required for `autonomy--sre-agent` to operate effectively.
+Machine-readable telemetry is required for `interface-sre-agent` to operate effectively.
 
 ## Output
 
 Ensure the report directory exists: `mkdir -p .agents/reports/completed && touch .agents/reports/.gitkeep .agents/reports/completed/.gitkeep`
 
 Ensure `.gitignore` ignores generated report contents while preserving the directories with their `.gitkeep` files.
 
-Write the report to `.agents/reports/autonomy--sre-auditor-audit.md`:
+Write the report to `.agents/reports/autonomy-sre-auditor-audit.md`:
 
 ```
 # SRE Tooling Audit Report
@@ -166,10 +175,18 @@ Write the report to `.agents/reports/autonomy--sre-auditor-audit.md`:
 - **Current State:** [what exists]
 - **Required State:** [what should exist]
 - **Recommended Action:** [specific step]
-- **Next Skill / Step:** [e.g., Install/authenticate tooling manually, then re-run `autonomy--sre-auditor`; once ready, use `autonomy--sre-agent`]
+- **Next Skill / Step:** [e.g., Install/authenticate tooling manually, then re-run `autonomy-sre-auditor`; once ready, use `interface-sre-agent`]
 
 ## Next Steps
-Address findings to enable `autonomy--sre-agent` to operate effectively. If tooling or auth is missing, complete the manual install/authentication work first, then re-run `autonomy--sre-auditor`.
+Address findings to enable `interface-sre-agent` to operate effectively. If tooling or auth is missing, complete the manual install/authentication work first, then re-run `autonomy-sre-auditor`.
+
+## Calibration
+**Depth:** [quick / standard / deep]
+**Confidence:** [High / Medium / Low] — [one-sentence reason]
+**Not checked:**
+- [specific area + reason]
+**To raise confidence:**
+- [specific next step]
 ```
 
 After writing the report, update `docs/onboarding-checklist.md` and `.agents/code-mint-status.json` with the current `sre_investigation` outcome status and date. Optionally update `docs/skills-status.md` if the repository keeps the compatibility view.

…kills/autonomy--runtime-auditor/SKILL.md …skills/autonomy-staging-auditor/SKILL.md.agents/skills/autonomy--runtime-auditor/SKILL.md renamed to .agents/skills/autonomy-staging-auditor/SKILL.md .agents/skills/autonomy--runtime-auditor/SKILL.md renamed to .agents/skills/autonomy-staging-auditor/SKILL.md

@@ -1,12 +1,21 @@
 ---
-name: autonomy--runtime-auditor
-description: Audit whether an AI agent can go from a clean checkout to a runnable application or local runtime equivalent, without unsafe provisioning or destructive setup. Use when evaluating development or staging-like runtime readiness, onboarding a new project, or checking whether the agent can install dependencies, start services, and perform smoke checks. Do not use when evaluating test strategy and coverage depth (use autonomy--test-readiness-auditor) or when debugging a live production issue (use autonomy--sre-agent).
+name: autonomy-staging-auditor
+description: Audit whether an AI agent can go from a clean checkout to a runnable application or local runtime equivalent, without unsafe provisioning or destructive setup. Use when evaluating development or staging-like runtime readiness, onboarding a new project, or checking whether the agent can install dependencies, start services, and perform smoke checks. Do not use when evaluating test strategy and coverage depth (use autonomy-testing-auditor) or when debugging a live production issue (use interface-sre-agent).
 ---
 
 # Runtime Auditor
 
 Evaluate whether an agent can go from a clean checkout to a safe local runtime or staging-like equivalent, or to the closest safe local simulation of that environment. This skill focuses on install, setup, local services, startup, smoke checks, and infrastructure inspection. It does not require cloud provisioning.
 
+## Discipline
+
+This auditor follows code-mint's shared auditor discipline:
+
+- **Depth option** — default `standard`; use `quick` for a sanity check on a recently audited repo or `deep` for legacy codebases, quarterly refreshes, or high-risk readiness claims. Heritage classification from `meta-onboarding` Phase 0 sets a sensible default.
+- **Calibration** — every report ends with a Calibration section naming the depth used, confidence level, what was not checked, and what would raise confidence. This is a required artifact, not a disclaimer.
+
+This discipline is inspired by AWS AI-DLC's adaptive-depth and overconfidence-prevention ideas, but code-mint does not vendor or implement the full AI-DLC workflow.
+
 ## Collaboration Rules
 
 Do not treat runtime readiness as a pure checklist exercise. Inspect the repository first, then ask only for the operational context the codebase cannot answer confidently.
@@ -57,7 +66,7 @@ Check whether the application dependencies can be installed autonomously:
 
 ## Step 2: Evaluate Environment and Configuration Handoff
 
-Cross-reference `autonomy--env-auditor` findings if that report exists.
+Cross-reference `autonomy-env-auditor` findings if that report exists.
 
 - [ ] The runtime depends on a documented env loading path
 - [ ] Required local or development-safe values are available
@@ -134,7 +143,7 @@ Ensure the report directories exist: `mkdir -p .agents/reports/completed && touc
 
 Ensure `.gitignore` ignores generated report contents while preserving the directories with their `.gitkeep` files.
 
-Write the report to `.agents/reports/autonomy--runtime-auditor-audit.md`:
+Write the report to `.agents/reports/autonomy-staging-auditor-audit.md`:
 
 ```markdown
 # Runtime Audit Report
@@ -189,10 +198,18 @@ Write the report to `.agents/reports/autonomy--runtime-auditor-audit.md`:
 - **Current State:** [what exists]
 - **Required State:** [what should exist]
 - **Recommended Action:** [specific step]
-- **Next Skill / Step:** [for example, run `autonomy--runtime-creator`]
+- **Next Skill / Step:** [for example, run `autonomy-staging-creator`]
 
 ## Next Steps
-Run `autonomy--runtime-creator` to remediate findings.
+Run `autonomy-staging-creator` to remediate findings.
+
+## Calibration
+**Depth:** [quick / standard / deep]
+**Confidence:** [High / Medium / Low] — [one-sentence reason]
+**Not checked:**
+- [specific area + reason]
+**To raise confidence:**
+- [specific next step]
 ```
 
 After writing the report, update `docs/onboarding-checklist.md` and `.agents/code-mint-status.json` with the current `smoke_path` outcome status and date. Optionally update `docs/skills-status.md` if the repository keeps the compatibility view.

…e-auditor/references/smoke-test-guide.md …g-auditor/references/smoke-test-guide.md.agents/skills/autonomy--runtime-auditor/references/smoke-test-guide.md renamed to .agents/skills/autonomy-staging-auditor/references/smoke-test-guide.md .agents/skills/autonomy--runtime-auditor/references/smoke-test-guide.md renamed to .agents/skills/autonomy-staging-auditor/references/smoke-test-guide.md

@@ -1,15 +1,15 @@
 ---
-name: autonomy--runtime-creator
-description: Builds the scripts, setup flow, and runtime documentation needed for an agent to install dependencies, start local services, boot the app, and run smoke checks from a clean checkout. Use when a runtime audit report exists and runtime readiness needs improvement. Do not use when no audit report exists (run autonomy--runtime-auditor first) or when the main gap is test coverage depth (use autonomy--test-readiness-creator).
+name: autonomy-staging-creator
+description: Builds the scripts, setup flow, and runtime documentation needed for an agent to install dependencies, start local services, boot the app, and run smoke checks from a clean checkout. Use when a runtime audit report exists and runtime readiness needs improvement. Do not use when no audit report exists (run autonomy-staging-auditor first) or when the main gap is test coverage depth (use autonomy-testing-creator).
 ---
 
 # Runtime Creator
 
-Build out a repository's runtime readiness so that an agent can go from a clean checkout to a runnable application or local runtime equivalent. Base all work on `autonomy--runtime-auditor`.
+Build out a repository's runtime readiness so that an agent can go from a clean checkout to a runnable application or local runtime equivalent. Base all work on `autonomy-staging-auditor`.
 
 ## Prerequisites
 
-Read `.agents/reports/autonomy--runtime-auditor-audit.md`. If no report exists, instruct the user to run `autonomy--runtime-auditor` first.
+Read `.agents/reports/autonomy-staging-auditor-audit.md`. If no report exists, instruct the user to run `autonomy-staging-auditor` first.
 
 ## Collaboration Rules
 
@@ -26,7 +26,7 @@ When needed, ask the developer:
 - "Which local substitutions are acceptable compared with production?"
 - "Which runtime steps are safe to automate, and which must stay manual?"
 
-For smoke-test patterns and safety boundaries, see [../autonomy--runtime-auditor/references/smoke-test-guide.md](../autonomy--runtime-auditor/references/smoke-test-guide.md). The guide lives with the auditor skill intentionally so runtime audit and remediation share one canonical document (`docs/skill-development.md` documents this cross-skill link pattern).
+For smoke-test patterns and safety boundaries, see [../autonomy-staging-auditor/references/smoke-test-guide.md](../autonomy-staging-auditor/references/smoke-test-guide.md). The guide lives with the auditor skill intentionally so runtime audit and remediation share one canonical document (`docs/skill-development.md` documents this cross-skill link pattern).
 
 ## Step 1: Extract the Handoff Contract
 
@@ -123,5 +123,5 @@ If any step still depends on human approval or real cloud setup, document that b
 
 ## Step 7: Archive
 
-1. Archive the audit report to `.agents/reports/completed/autonomy--runtime-auditor-audit-{YYYY-MM-DD}.md`
+1. Archive the audit report to `.agents/reports/completed/autonomy-staging-auditor-audit-{YYYY-MM-DD}.md`
 2. Update `docs/onboarding-checklist.md` and `.agents/code-mint-status.json` with the current `smoke_path` outcome status and date. Optionally update `docs/skills-status.md` if the repository keeps the compatibility view.