AI Slop Code RIsk Monitor

awslabs/aidlc-workflows

AI-Driven Life Cycle (AI-DLC) adaptive workflow steering rules for AI coding agents

4.9 Low pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for awslabs/aidlc-workflows, a TypeScript project with 5,129 GitHub stars. SynthScan examined 770,975 lines of code across 1506 source files, recording 3244 pattern matches distributed across 13 syntactic categories. The legacy adjusted pattern signal is 4.9 (Low pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

4.9
Adjusted Signal
4.9
Raw Pattern Score
100%
Time Factor
2026-10-11
Last Push
5.1K
Stars
TypeScript
Language
771.0K
Lines of Code
1.5K
Files
3.2K
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 20.5/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 3160 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.2/100 · LOW

Are imports declared and package/API names verified? 16 finding(s).

Agent Over-Engineering Ratio 6.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 898 finding(s).

PR Review Velocity Impact 21.5/100 · LOW

Which changes need focused human review? 3244 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 6MEDIUM 226LOW 3012

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 3244 distinct pattern matches across 13 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block1846 hits · 1717 pts
SeverityFileLineSnippetContext
LOWcore/tools/aidlc-documentkb-schema.ts1// DocumentKB index + per-document metadata schema — the machine-checkableCOMMENT
LOWcore/tools/aidlc-documentkb-schema.ts21// collapsing them into one "unsupported" sends the user down the wrong path.COMMENT
LOWcore/tools/aidlc-documentkb-schema.ts181// stores anything free-form (`EXTRACT_OUTPUT_CHAR_CAP`, `BOLT_SLUG_MAX_LENGTH`,COMMENT
LOWcore/tools/aidlc-documentkb-schema.ts201 return false;COMMENT
LOWcore/tools/aidlc-documentkb-schema.ts601 // write this release makes does), not a NEW requirement layered onto anCOMMENT
LOWcore/tools/aidlc-rule-schema.ts1// Rule frontmatter schema — machine-checkable realisation of the rule-fileCOMMENT
LOWcore/tools/aidlc-rule-schema.ts41// Returns {} when no `---...---` block is present. Differs fromCOMMENT
LOWcore/tools/aidlc-rules-held.ts1// Whether the chat already holds a stage's exact rule text (#2023).COMMENT
LOWcore/tools/aidlc-rules-held.ts21// fork may also carry older copies, so after an edit it proves nothing.COMMENT
LOWcore/tools/aidlc-workspace-sync.ts1// aidlc-workspace-sync.ts - reconcile a workspace against its optionalCOMMENT
LOWcore/tools/aidlc-testing-posture.ts1401//COMMENT
LOWcore/tools/aidlc-testing-posture.ts1421//COMMENT
LOWcore/tools/aidlc-testing-posture.ts1481 }COMMENT
LOWcore/tools/aidlc-testing-posture.ts1821// again from step 1 by the next worker. When the brief is for a build thatCOMMENT
LOWcore/tools/aidlc-testing-posture.ts1841// content the build started on. Its key binds the target, the stage attemptCOMMENT
LOWcore/tools/aidlc-testing-posture.ts3981 Atomics.wait(waitCell, 0, 0, 10);COMMENT
LOWcore/tools/aidlc-knowledge.ts1// aidlc-knowledge.ts — the DocumentKB tool: index a customer's documents into aCOMMENT
LOWcore/tools/aidlc-knowledge.ts21//COMMENT
LOWcore/tools/aidlc-knowledge.ts41//COMMENT
LOWcore/tools/aidlc-knowledge.ts221const PRUNED_WALK_DIRS: ReadonlySet<string> = new Set(["aidlc", "node_modules"]);COMMENT
LOWcore/tools/aidlc-knowledge.ts281// --- Content sniffing --------------------------------------------------------COMMENT
LOWcore/tools/aidlc-knowledge.ts361 // Bit 3 (streamed / data-descriptor) means compressedSize here is 0 andCOMMENT
LOWcore/tools/aidlc-knowledge.ts781}COMMENT
LOWcore/tools/aidlc-knowledge.ts901 // `.sources.local.json` sits directly under `knowledge/` -- a SIBLING ofCOMMENT
LOWcore/tools/aidlc-knowledge.ts1021 }COMMENT
LOWcore/tools/aidlc-knowledge.ts1241 // `space` becomes a raw path COMPONENT two lines down. Every in-repo callerCOMMENT
LOWcore/tools/aidlc-knowledge.ts1341 return null;COMMENT
LOWcore/tools/aidlc-knowledge.ts1681 ensureDocumentAssociationAudit(projectDir, space, row, auditState);COMMENT
LOWcore/tools/aidlc-knowledge.ts1761 continue;COMMENT
LOWcore/tools/aidlc-knowledge.ts1821 // publishes NOTHING -- the journal dir (still on disk, never renamed) isCOMMENT
LOWcore/tools/aidlc-knowledge.ts1841 ensureDirSync(documentkbDir(projectDir, space));COMMENT
LOWcore/tools/aidlc-knowledge.ts1881 // order and onboard's edited path -- new code in the same effort --COMMENT
LOWcore/tools/aidlc-knowledge.ts2121// metadata.json's content_trust / content_handling keys are the DURABLE RECORD,COMMENT
LOWcore/tools/aidlc-knowledge.ts2501 if (d.summary_text !== undefined) {COMMENT
LOWcore/tools/aidlc-knowledge.ts2601 const before = readIndex(projectDir, space);COMMENT
LOWcore/tools/aidlc-knowledge.ts2621 // kind, or over the per-document cap) -- tracked SEPARATELY from `byPath`,COMMENT
LOWcore/tools/aidlc-knowledge.ts2721 needsRetry.push({ row, here });COMMENT
LOWcore/tools/aidlc-knowledge.ts2861 for (const next of needsNew) {COMMENT
LOWcore/tools/aidlc-knowledge.ts2901 // lock. A concurrent writer (rebind, another sync, onboard's edit path) mayCOMMENT
LOWcore/tools/aidlc-knowledge.ts2921 // were produced from. Planning (and extraction, for "changed"/"retried")COMMENT
LOWcore/tools/aidlc-knowledge.ts3101 }COMMENT
LOWcore/tools/aidlc-knowledge.ts3441// A document is SPACE-WIDE by default: available to every intent in the space.COMMENT
LOWcore/tools/aidlc-knowledge.ts3821 path: `documentkb/${row.id}/summary.md`,COMMENT
LOWcore/tools/aidlc-install-paths.ts141// The body is location-independent ($0's directory), so it is a constant bothCOMMENT
LOWcore/tools/aidlc-install-paths.ts181 // misfire on; the rendered line is byte-identical.COMMENT
LOWcore/tools/aidlc-runner-gen.ts1// The runner-skill generator — one tool, two runner families.COMMENT
LOWcore/tools/aidlc-runner-gen.ts21// high-traffic ones marked in scope metadata.COMMENT
LOWcore/tools/aidlc-runner-gen.ts101// Initialization-phase stages are bootstrap: they have no standalone meaningCOMMENT
LOWcore/tools/aidlc-runner-gen.ts301}COMMENT
LOWcore/tools/aidlc-log.ts261// --intent/--space, so it relies on default intent resolution. On a fresh shellCOMMENT
LOWcore/tools/aidlc-log.ts341// double quote written as \" inside the value reaches the engine intact).COMMENT
LOWcore/tools/aidlc-log.ts621 if (stageLevel) return { unit: null };COMMENT
LOWcore/tools/aidlc-log.ts1461// --- Subcommand: answer ---COMMENT
LOWcore/tools/aidlc-log.ts2781 ...(recordedRepo ? { repo: recordedRepo } : {}),COMMENT
LOWcore/tools/aidlc-bolt.ts1// aidlc-bolt.ts — Construction-phase bolt lifecycleCOMMENT
LOWcore/tools/aidlc-bolt.ts21// abort --discard — explicit user-driven abort; optional discard tear-downCOMMENT
LOWcore/tools/aidlc-bolt.ts841COMMENT
LOWcore/tools/aidlc-bolt.ts981 : ["ignored files", "eol/text=auto normalization"],COMMENT
LOWcore/tools/aidlc-bolt.ts1001// No audit emission — Merge-Held is internal coordination state, not aCOMMENT
LOWcore/tools/aidlc-bolt.ts1081 }COMMENT
1786 more matches not shown…
Hyper-Verbose Identifiers830 hits · 764 pts
SeverityFileLineSnippetContext
LOWcore/tools/aidlc-kiro-ide-workflows.ts114function unreadableSettingsMessage(settingsPath: string, enabled: boolean): string {CODE
LOWcore/tools/aidlc-kiro-ide-workflows.ts133export function recordKiroWorkflowsAnswer(answer: KiroWorkflowsAnswer): void {CODE
LOWcore/tools/aidlc-kiro-ide-workflows.ts169export function kiroWorkflowsIssueMessage(): string {CODE
LOWcore/tools/aidlc-uninstall-plan.ts55function posixLauncherOwnedByInstaller(path: string): boolean {CODE
LOWcore/tools/aidlc-inline-context.ts295function selectShippedInlineKnowledge(CODE
LOWcore/tools/aidlc-inline-context.ts328export function shippedInlineContextEntries(CODE
LOWcore/tools/aidlc-rules-held.ts220function opencodeIncludedMemoryDir(projectDir: string, space: string): string | null {CODE
LOWcore/tools/aidlc-kiro-ide-terminal.ts105export function setKiroIdeTerminalPowerShell(CODE
LOWcore/tools/aidlc-kiro-ide-terminal.ts125function unreadableSettingsMessage(settingsPath: string): string {CODE
LOWcore/tools/aidlc-kiro-ide-terminal.ts211export function kiroIdeTerminalStandingLine(invoke: string, env: NodeJS.ProcessEnv = process.env): string {CODE
LOWcore/tools/aidlc-kiro-ide-terminal.ts308export function rejoinCommandPromptQuotes(CODE
LOWcore/tools/aidlc-kiro-ide-terminal.ts342export function commandPromptChildCommand(CODE
LOWcore/tools/aidlc-workspace-sync.ts261function localRemoteAlternateReasons(CODE
LOW⚡core/tools/aidlc-testing-posture.ts2386export function questionsFileHasPendingPlanApproval(body: string): boolean {CODE
LOW⚡core/tools/aidlc-testing-posture.ts2395export function questionsFileApprovalFingerprint(body: string): string | null {CODE
LOW⚡core/tools/aidlc-testing-posture.ts2399export function questionsFilePlannedSource(body: string): string | null {CODE
LOW⚡core/tools/aidlc-testing-posture.ts2409export function planApprovalSectionSkeleton(CODE
LOWcore/tools/aidlc-testing-posture.ts309export function planApprovalUnbindableRemedies(): PlanApprovalRemedy[] {CODE
LOWcore/tools/aidlc-testing-posture.ts357export function planSourceDriftStrictMessage(paths: string[] | null, unbound = false): string {CODE
LOWcore/tools/aidlc-testing-posture.ts364export function planSourceDriftRelaxedNotice(paths: string[] | null, unbound = false): string {CODE
LOWcore/tools/aidlc-testing-posture.ts435function keepWorkspaceSourceSnapshot(CODE
LOWcore/tools/aidlc-testing-posture.ts442function generationSourceUnavailableMessage(): string {CODE
LOWcore/tools/aidlc-testing-posture.ts455export function codeGenerationBuildsWithoutSource(CODE
LOWcore/tools/aidlc-testing-posture.ts523export function approvalFingerprintIsCurrentFormat(tag: string | null): boolean {CODE
LOWcore/tools/aidlc-testing-posture.ts533export function recordedApprovalFingerprint(questions: string): string | null {CODE
LOWcore/tools/aidlc-testing-posture.ts736function stripHtmlCommentsFromLine(CODE
LOWcore/tools/aidlc-testing-posture.ts805function markdownWithoutHtmlComments(body: string): string {CODE
LOWcore/tools/aidlc-testing-posture.ts879function extractTestingPostureSection(content: string): string {CODE
LOWcore/tools/aidlc-testing-posture.ts1122export function resolveTestingPostureFromSections(CODE
LOWcore/tools/aidlc-testing-posture.ts1238export function replaceTestingContractSection(CODE
LOWcore/tools/aidlc-testing-posture.ts1333export function testingContractDefectMessage(CODE
LOWcore/tools/aidlc-testing-posture.ts1359function testingContractDefectReason(plan: string): string | null {CODE
LOWcore/tools/aidlc-testing-posture.ts1438export function projectPlanApprovalContent(text: string): string {CODE
LOWcore/tools/aidlc-testing-posture.ts1490export function projectInstructionsContent(text: string): string {CODE
LOWcore/tools/aidlc-testing-posture.ts2218export function codeGenerationResumeNarration(CODE
LOWcore/tools/aidlc-testing-posture.ts2247export function codeGenerationStartNarration(projectDir: string, unit: string | null): string | null {CODE
LOWcore/tools/aidlc-testing-posture.ts2433function missingPlanApprovalFingerprintReason(questions: string): string {CODE
LOWcore/tools/aidlc-testing-posture.ts2446export function promptTestingContractMarkers(text: string): string[] {CODE
LOWcore/tools/aidlc-testing-posture.ts2455function normalizeCodeGenerationTarget(target: CodeGenerationTarget): CodeGenerationTarget {CODE
LOWcore/tools/aidlc-testing-posture.ts2468export function resolveCodeGenerationAuthority(CODE
LOWcore/tools/aidlc-testing-posture.ts2477function activeCodeGenerationDirective(marker: ActiveDirectiveMarker): CodeGenerationIssuance {CODE
LOWcore/tools/aidlc-testing-posture.ts2570export function codeGenerationRulesArrivingReason(marker: ActiveDirectiveMarker | null): string | null {CODE
LOWcore/tools/aidlc-testing-posture.ts2737function codeGenerationApprovalArtifacts(CODE
LOWcore/tools/aidlc-testing-posture.ts2854function approvalFromTheirChangeRequest(CODE
LOWcore/tools/aidlc-testing-posture.ts2960function continuationContractProject(CODE
LOWcore/tools/aidlc-testing-posture.ts2968function codeGenerationContinuation(CODE
LOWcore/tools/aidlc-testing-posture.ts2992export function codeGenerationPlanApprovalFence(CODE
LOWcore/tools/aidlc-testing-posture.ts3015export function codeGenerationExecutionAllowed(CODE
LOWcore/tools/aidlc-testing-posture.ts3026function recordCodeGenerationContinuation(CODE
LOWcore/tools/aidlc-testing-posture.ts3087export function legacyPlanApprovalGuardState(CODE
LOWcore/tools/aidlc-testing-posture.ts3291function assertPlanApprovalBatchLifecycle(projectDir: string, receipt: PlanApprovalRuntimeReceipt): ActiveDirectiveMarkeCODE
LOWcore/tools/aidlc-testing-posture.ts3363function planApprovalBatchSelection(projectDir: string, file: string): PlanApprovalBatchSelection {CODE
LOWcore/tools/aidlc-testing-posture.ts3397function assertLivePlanApprovalBatch(projectDir: string, units: string[]): void {CODE
LOWcore/tools/aidlc-testing-posture.ts3431function planApprovalBatchEvidence(CODE
LOWcore/tools/aidlc-testing-posture.ts3467export function recordPlanApprovalBatchChallenge(CODE
LOWcore/tools/aidlc-testing-posture.ts3500export function recordPlanApprovalBatchReceipts(CODE
LOWcore/tools/aidlc-testing-posture.ts3554function assertPlanApprovalBatchCurrent(projectDir: string, receipt: PlanApprovalRuntimeReceipt): void {CODE
LOWcore/tools/aidlc-testing-posture.ts3579export function recordPlanApprovalChallenge(CODE
LOWcore/tools/aidlc-testing-posture.ts3719export function recordPlanApprovalHumanResponse(CODE
LOWcore/tools/aidlc-testing-posture.ts3786function pickerAsksProtectedQuestion(CODE
770 more matches not shown…
Structural Annotation Overuse290 hits · 531 pts
SeverityFileLineSnippetContext
LOW…e/aidlc-common/stages/operation/deployment-pipeline.md47### Step 1: Load Prior ContextCOMMENT
LOW…e/aidlc-common/stages/operation/deployment-pipeline.md62### Step 2: Generate Clarifying QuestionsCOMMENT
LOW⚡…e/aidlc-common/stages/operation/deployment-pipeline.md73### Step 3: Generate ArtifactsCOMMENT
LOW⚡…e/aidlc-common/stages/operation/deployment-pipeline.md77### Step 4: Completion HandoffCOMMENT
LOW⚡…e/aidlc-common/stages/operation/deployment-pipeline.md83### Step 5: Present Completion & Request ApprovalCOMMENT
LOW…/aidlc-common/stages/operation/deployment-execution.md48### Step 1: Load Prior ContextCOMMENT
LOW⚡…/aidlc-common/stages/operation/deployment-execution.md69### Step 2: Pre-Deployment ChecksCOMMENT
LOW⚡…/aidlc-common/stages/operation/deployment-execution.md79### Step 3: Execute DeploymentCOMMENT
LOW⚡…/aidlc-common/stages/operation/deployment-execution.md83### Step 4: Generate ArtifactsCOMMENT
LOW⚡…/aidlc-common/stages/operation/deployment-execution.md87### Step 5: Completion HandoffCOMMENT
LOW⚡…/aidlc-common/stages/operation/deployment-execution.md93### Step 6: Present Completion & Request ApprovalCOMMENT
LOW⚡…lc-common/stages/operation/environment-provisioning.md40### Step 1: Load Prior ContextCOMMENT
LOW⚡…lc-common/stages/operation/environment-provisioning.md45### Step 2: Generate Clarifying QuestionsCOMMENT
LOW⚡…lc-common/stages/operation/environment-provisioning.md55### Step 3: Provision and ValidateCOMMENT
LOW⚡…lc-common/stages/operation/environment-provisioning.md59### Step 4: Generate ArtifactsCOMMENT
LOW⚡…lc-common/stages/operation/environment-provisioning.md63### Step 5: Completion HandoffCOMMENT
LOW⚡…lc-common/stages/operation/environment-provisioning.md69### Step 6: Present Completion & Request ApprovalCOMMENT
LOW…aidlc-common/stages/operation/feedback-optimization.md51### Step 1: Load Prior ContextCOMMENT
LOW…aidlc-common/stages/operation/feedback-optimization.md58### Step 2: Generate QuestionsCOMMENT
LOW⚡…aidlc-common/stages/operation/feedback-optimization.md69### Step 3: Generate ArtifactsCOMMENT
LOW⚡…aidlc-common/stages/operation/feedback-optimization.md73### Step 4: Completion HandoffCOMMENT
LOW⚡…aidlc-common/stages/operation/feedback-optimization.md79### Step 5: Present Completion & Request ApprovalCOMMENT
LOW⚡…idlc-common/stages/operation/performance-validation.md45### Step 1: Load Prior ContextCOMMENT
LOW⚡…idlc-common/stages/operation/performance-validation.md51### Step 2: Generate Clarifying QuestionsCOMMENT
LOW⚡…idlc-common/stages/operation/performance-validation.md61### Step 3: Design and Execute TestsCOMMENT
LOW⚡…idlc-common/stages/operation/performance-validation.md65### Step 4: Generate ArtifactsCOMMENT
LOW⚡…idlc-common/stages/operation/performance-validation.md69### Step 5: Completion HandoffCOMMENT
LOW⚡…idlc-common/stages/operation/performance-validation.md75### Step 6: Present Completion & Request ApprovalCOMMENT
LOWcore/aidlc-common/stages/operation/incident-response.md43### Step 1: Load Prior ContextCOMMENT
LOWcore/aidlc-common/stages/operation/incident-response.md49### Step 2: Generate Clarifying QuestionsCOMMENT
LOW⚡core/aidlc-common/stages/operation/incident-response.md60### Step 3: Generate ArtifactsCOMMENT
LOW⚡core/aidlc-common/stages/operation/incident-response.md64### Step 4: Completion HandoffCOMMENT
LOW⚡core/aidlc-common/stages/operation/incident-response.md70### Step 5: Present Completion & Request ApprovalCOMMENT
LOW…e/aidlc-common/stages/operation/observability-setup.md50### Step 1: Load Prior ContextCOMMENT
LOW…e/aidlc-common/stages/operation/observability-setup.md64### Step 2: Generate Clarifying QuestionsCOMMENT
LOW⚡…e/aidlc-common/stages/operation/observability-setup.md75### Step 3: Generate ArtifactsCOMMENT
LOW⚡…e/aidlc-common/stages/operation/observability-setup.md79### Step 4: Completion HandoffCOMMENT
LOW⚡…e/aidlc-common/stages/operation/observability-setup.md85### Step 5: Present Completion & Request ApprovalCOMMENT
LOW…e/aidlc-common/stages/inception/reverse-engineering.md65### Step 1: Check ConditionsCOMMENT
LOW…e/aidlc-common/stages/inception/reverse-engineering.md213### Step 2: Developer Code ScanCOMMENT
LOW…e/aidlc-common/stages/inception/reverse-engineering.md296### Step 3: Architect SynthesisCOMMENT
LOW…e/aidlc-common/stages/inception/reverse-engineering.md467### Step 4: Completion HandoffCOMMENT
LOW…e/aidlc-common/stages/inception/reverse-engineering.md486### Step 5: Present Completion & Request ApprovalCOMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md68### Step 1: Check ConditionsCOMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md84### Step 2: Lead Draft (Always)COMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md102### Step 3: Blind Support ReviewCOMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md133### Step 4: Interview (Always)COMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md169### Step 5: Lead IntegrationCOMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md206### Step 6: Learnings + Affirmation GateCOMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md234### Step 7: Promote (On Approve Only)COMMENT
LOW…e/aidlc-common/stages/inception/practices-discovery.md261### Step 8: Commit ApprovalCOMMENT
LOWcore/aidlc-common/stages/inception/refined-mockups.md51### Step 1: Load Prior ContextCOMMENT
LOWcore/aidlc-common/stages/inception/refined-mockups.md59### Step 2: Generate Clarifying QuestionsCOMMENT
LOW⚡core/aidlc-common/stages/inception/refined-mockups.md72### Step 3: Collect and Analyze AnswersCOMMENT
LOW⚡core/aidlc-common/stages/inception/refined-mockups.md76### Step 4: Generate ArtifactsCOMMENT
LOW⚡core/aidlc-common/stages/inception/refined-mockups.md82### Step 5: Completion HandoffCOMMENT
LOW⚡core/aidlc-common/stages/inception/refined-mockups.md88### Step 6: Present Completion & Request ApprovalCOMMENT
LOWcore/aidlc-common/stages/inception/user-stories.md53### Step 1: Load the Lead Persona (mob stage)COMMENT
LOWcore/aidlc-common/stages/inception/user-stories.md61### Step 2: Validate User Stories Are NeededCOMMENT
LOW⚡core/aidlc-common/stages/inception/user-stories.md78### Step 3: Load Prior ContextCOMMENT
230 more matches not shown…
Modern AI Meta-Vocabulary102 hits · 303 pts
SeverityFileLineSnippetContext
MEDIUMCHANGELOG.md79* Content appended under a `## ` heading is now separated from the following `## ` heading by exactly one blank line, keCOMMENT
MEDIUMCHANGELOG.md1283**Upgrade:** re-copy your `dist/<harness>/` shell into the project. This is mandatory, not optional: the old hook files CODE
MEDIUM⚡CHANGELOG.md2081* **Park (#365, #367):** `bun .claude/tools/aidlc-orchestrate.ts park` parks the workflow at the current inter-stage bouCOMMENT
MEDIUM⚡CHANGELOG.md2084* **Conversational carve-out (#365):** the Stop hook no longer nags a human who is just chatting mid-workflow. When the COMMENT
MEDIUM⚡CHANGELOG.md2089Fixes issue #368: a multi-unit Construction phase now runs every Unit of Work through each per-unit design stage before CODE
MEDIUMCHANGELOG.md3032* `## Mandated` and `## Forbidden` headings appended to `.claude/rules/aidlc/guardrails/project-guardrails.md`. Mirrors COMMENT
MEDIUMcore/aidlc-common/protocols/stage-protocol.md391 - **Request Changes** → `{{INVOKE}} engine orchestrate report --stage <slug> --result rejected --user-input "Request CODE
MEDIUMcore/aidlc-common/protocols/stage-protocol.md802# Stage completion is reported through aidlc-orchestrate.ts; no manual checkbox write.COMMENT
MEDIUMcore/tools/aidlc-sensor-claim-sources.ts63// Lines the `## Assumption Confirmation` section owns as scaffolding ratherCOMMENT
MEDIUMcore/tools/aidlc-rule-schema.ts18// - enforcement: enforced (no two-mode keyword; all rules are guardrails)COMMENT
MEDIUMcore/tools/aidlc-runner-gen.ts103// scaffold half a workspace). The whole initialization phase is run as ONECOMMENT
MEDIUMcore/tools/aidlc-runner-gen.ts104// atomic operation by `/aidlc --init` (aidlc-utility.ts: scaffold + scan +COMMENT
MEDIUMcore/tools/aidlc-runner-gen.ts360// aidlc-workspace-scaffold) left by an earlier generation that emitted runnersCOMMENT
MEDIUMcore/tools/aidlc-orchestrate.ts65// dies at its guard before any scaffold write.COMMENT
MEDIUMcore/tools/aidlc-orchestrate.ts12599// stage is rejected (bootstrap stages create/scaffold state — they have noCOMMENT
MEDIUMcore/tools/aidlc-orchestrate.ts12894// behavior (create the state file, scaffold dirs) that doesn't fit the jumpCOMMENT
MEDIUMcore/tools/aidlc-state.ts8265 // Step 4b: Build new project-guardrails.md by appending each rule under theCOMMENT
MEDIUMcore/tools/aidlc-plugin-create.ts2// Deterministic offline scaffold for a new AIDLC plugin repository.COMMENT
MEDIUMcore/tools/aidlc-learnings.ts713// it provides the minimal scaffold the ensure-exists append can land into.COMMENT
MEDIUMcore/tools/aidlc-utility.ts7138// init (scaffold 0.2) — bootstrap state/audit files + scaffold aidlc-docs/COMMENT
MEDIUMcore/tools/aidlc-utility.ts7489 // dir doesn't exist yet (caller should scaffold first)COMMENT
MEDIUMcore/tools/aidlc-utility.ts8739 // subsequent `advance` call would appear to jump from workspace-scaffoldCOMMENT
MEDIUMcore/agents/aidlc-devsecops-agent.md64`aidlc/spaces/<active-space>/memory/{org,team,project}.md` — active-space guardrails and affirmed practices (read per `{CODE
MEDIUMcore/hooks/aidlc-run-sensors.ts150// with empty sensors_applicable like workspace-scaffold, (b) noCOMMENT
MEDIUMcore/hooks/aidlc-run-sensors.ts209// No applicable sensors. Empty array is the workspace-scaffold case;COMMENT
MEDIUMcore/hooks/aidlc-record-human-turn.ts18// harness shell but never ran the framework would scaffold and grow auditCOMMENT
MEDIUMtests/smoke/t06-claude-md-paths.test.ts23// .sh test 2 (flat rules/ — no rules/aidlc/guardrails nested) -> "describes a flat .claude/rules/ layout (no nestedCOMMENT
MEDIUMtests/smoke/t06-claude-md-paths.test.ts65 // milestone 2 flattened the rules tree; the legacy nested guardrails path must beCOMMENT
MEDIUMtests/smoke/t06-claude-md-paths.test.ts66 // gone. .sh: grep -q "\.claude/rules/aidlc/guardrails" => must NOT match.COMMENT
MEDIUMtests/smoke/t01-file-structure.test.ts1// covers: file:skills/aidlc/SKILL.md, file:aidlc-common/protocols/stage-protocol.md, file:aidlc-common/protocols/stage-COMMENT
MEDIUMtests/unit/t157-workspace-shell-seed.test.ts35// (intents/codekb/knowledge ensure-exists) + the workspace-scaffold→ensure-COMMENT
MEDIUMtests/unit/t70-worktree-kb-and-skill.test.ts38// guardrails and practicesCOMMENT
MEDIUMtests/unit/t68-version-changelog-sync.test.ts58// link references were REMOVED. They shipped as broken `OWNER/REPO` scaffoldCOMMENT
MEDIUMtests/unit/t68-version-changelog-sync.test.ts194 // nor the scaffold placeholder. (Prose may name a host in plain words; thisCOMMENT
MEDIUMtests/unit/t230-dispatcher-routes.test.ts3100 // What a scaffold run says instead of "not valid" when it is refused.COMMENT
MEDIUMtests/unit/t87-stage-compartment-headers.test.ts1// covers: file:aidlc-common/stages/construction/build-and-test.md, file:aidlc-common/stages/construction/ci-pipeline.mdCOMMENT
MEDIUMtests/unit/t61.test.ts284 // (P4: creation no longer iterates agents to scaffold knowledge READMEs, so theCOMMENT
MEDIUMtests/unit/t71.test.ts14// overwrites them, appendUnderHeading adds rules to project-guardrails.md).COMMENT
MEDIUMtests/unit/t114-orchestrate-next.test.ts63// :822 Branch 3 --init -> print naming the scaffold cmd.COMMENT
MEDIUMtests/unit/t94-sensor-fire-hook.test.ts44// :184-185 empty sensors_applicable (workspace-scaffold) -> exit 0.COMMENT
MEDIUMtests/unit/t94-sensor-fire-hook.test.ts75// .sh case 16 empty sensors_applicable -> no spawn (HB kept)-> "empty sensors_applicable (workspace-scaffold) -> no sCOMMENT
MEDIUMtests/unit/t94-sensor-fire-hook.test.ts703 // workspace-scaffold carries sensors_applicable: [] in the framework graph,COMMENT
MEDIUMtests/unit/t259-turn-markers.test.ts171 // would scaffold the record tree as a side effect (touchTurnMarker mkdir -p'sCOMMENT
MEDIUMtests/unit/t296-config-setup-walk.test.ts169 // A scaffold records no model policy, so every agent would silently inheritCOMMENT
MEDIUMtests/unit/t97.test.ts191// mkproj() is the TS analogue of the .sh's mkproj: scaffold a minimal projectCOMMENT
MEDIUMtests/unit/t112-learnings-distribution-guard.test.ts35// could scaffold INTO the shipped framework distribution. This pins that theCOMMENT
MEDIUMtests/unit/t112-learnings-distribution-guard.test.ts246 // exit 0, scaffold the manifest under the project's own .claude/sensors, andCOMMENT
MEDIUMtests/unit/t294-config-diagnostics.test.ts4386// harness shell but never ran the framework would scaffold and grow auditCOMMENT
MEDIUMtests/unit/t27.test.ts52// - .sh T33 init bootstrap workspace-scaffold checkbox -> Test 33.COMMENT
MEDIUMtests/unit/t27.test.ts543 // onboarding runs --doctor before --init, so doctor must scaffold nothing.COMMENT
MEDIUMtests/unit/t27.test.ts656 // created intent + state init, not the old "Workspace scaffolded" scaffold line.COMMENT
MEDIUMtests/integration/t-scope-run-bugfix.test.ts1// covers: scope:bugfix, stage:initialization/workspace-scaffold, stage:initialization/workspace-detection, stage:initiaCOMMENT
MEDIUMtests/integration/t48-audit-event-emitters.test.ts345 // workspace-scaffold STAGE_STARTED), now into the created intent's record.COMMENT
MEDIUMtests/integration/t42-state-jumped-fixture.test.ts51// .sh 10 grep '\[x\] workspace-scaffold' -> "init stage workspace-scaffold is [x] completed, not [S]"COMMENT
MEDIUMtests/integration/t51.test.ts257 // and init pre-completes the 3 init stages: workspace-scaffold,COMMENT
MEDIUMtests/integration/t75.test.ts488 // rm the project guardrails target (t75:203).COMMENT
MEDIUMtests/integration/t-scope-run-enterprise.test.ts1// covers: scope:enterprise, stage:initialization/workspace-scaffold, stage:initialization/workspace-detection, stage:inCOMMENT
MEDIUMtests/integration/t-scope-run-security-patch.test.ts1// covers: scope:security-patch, stage:initialization/workspace-scaffold, stage:initialization/workspace-detection, stagCOMMENT
MEDIUMtests/integration/t21.test.ts48// 4 "[x] workspace-scaffold" -> state file contains "[x] workspace-scaffold" (init marker)COMMENT
MEDIUMtests/integration/t21.test.ts132// 11 agent dirs + aidlc-shared)" scaffold-tree line was a --init artifact and isCOMMENT
42 more matches not shown…
Decorative Section Separators68 hits · 195 pts
SeverityFileLineSnippetContext
MEDIUMtests/unit/t288-documentkb-schema.test.ts301// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t288-documentkb-schema.test.ts315// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t288-documentkb-schema.test.ts374// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t288-documentkb-schema.test.ts379// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t297-knowledge-intents.test.ts184// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t297-knowledge-intents.test.ts190// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t297-knowledge-intents.test.ts465// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t297-knowledge-intents.test.ts480// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts448// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts461// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts961// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts983// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts1293// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts1315// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts1429// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts1441// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts1482// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts1572// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts2037 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts2042 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts2116 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t289-knowledge-onboard-boundary.test.ts2121 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t154-codekb-promotion.test.ts94 // ── 1: RE stage outputs re-pointed, filenames preserved ──────────────────COMMENT
MEDIUMtests/unit/t154-codekb-promotion.test.ts109 // ── 2: RE body prose writes to the space-level codekb dir ────────────────COMMENT
MEDIUMtests/unit/t154-codekb-promotion.test.ts120 // ── 3: the freshness marker is preserved as the staleness gate ───────────COMMENT
MEDIUMtests/unit/t154-codekb-promotion.test.ts163 // ── 4: frontmatter consumers — edge intact, read path re-pointed ─────────COMMENT
MEDIUMtests/unit/t154-codekb-promotion.test.ts180 // ── 5: prose consumers re-pointed ────────────────────────────────────────COMMENT
MEDIUMtests/unit/t285-knowledge-skill.test.ts176 // ── I33: present in EVERY harness, at the harness-correct root ────────────COMMENT
MEDIUMtests/unit/t285-knowledge-skill.test.ts236 // ── I41: bidirectional flag parity ────────────────────────────────────────COMMENT
MEDIUMtests/unit/t285-knowledge-skill.test.ts286 // ── the --allow-inactive behaviour the prose promises ──────────────────────COMMENT
MEDIUMtests/unit/t285-knowledge-skill.test.ts410 // ── argv DISPATCH, not the handlers underneath ─────────────────────────────COMMENT
MEDIUMtests/unit/t285-knowledge-skill.test.ts829 // ── The per-verb Emits column, pinned by EXECUTION ─────────────────────────COMMENT
MEDIUMtests/unit/t60.test.ts15// ── CURRENT-SURFACE CORRECTION (audit fold-in) ───────────────────────────────COMMENT
MEDIUMtests/unit/t292-knowledge-list-show.test.ts328 // ── The INVARIANT, not another case ────────────────────────────────────────COMMENT
MEDIUMtests/unit/t284-knowledge-sync-rebind.test.ts199 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/unit/t284-knowledge-sync-rebind.test.ts208 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts21// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts23// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts50// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts52// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts118// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts120// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts232 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts235 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts249 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts252 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts271 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts279 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts302 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts311 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts341 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts347 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts375 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts381 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts485 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts491 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts506 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts535 // ───────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts551// ─────────────────────────────────────────────────────────────────────────────COMMENT
MEDIUMtests/integration/t55-test-suite-drift.test.ts556// ─────────────────────────────────────────────────────────────────────────────COMMENT
8 more matches not shown…
AI Slop Vocabulary53 hits · 136 pts
SeverityFileLineSnippetContext
MEDIUMzensical.toml179# Renders markdown inside HTML blocks carrying markdown="1" (the per-harnessCOMMENT
MEDIUM.gitleaks-baseline.json103 "Message": "feat: add AIDLC Evaluation \u0026 Reporting Framework (#115)\n\n* feat: add aidlc-evaluator framework\n\nECODE
MEDIUM.gitleaks-baseline.json124 "Message": "feat: add AIDLC Evaluation \u0026 Reporting Framework (#115)\n\n* feat: add aidlc-evaluator framework\n\nECODE
MEDIUM.gitleaks-baseline.json145 "Message": "feat: add AIDLC Evaluation \u0026 Reporting Framework (#115)\n\n* feat: add aidlc-evaluator framework\n\nECODE
MEDIUM.gitleaks-baseline.json166 "Message": "feat: add AIDLC Evaluation \u0026 Reporting Framework (#115)\n\n* feat: add aidlc-evaluator framework\n\nECODE
MEDIUM.gitleaks-baseline.json187 "Message": "feat: add AIDLC Evaluation \u0026 Reporting Framework (#115)\n\n* feat: add aidlc-evaluator framework\n\nECODE
MEDIUM.gitleaks-baseline.json208 "Message": "feat: add AIDLC Evaluation \u0026 Reporting Framework (#115)\n\n* feat: add aidlc-evaluator framework\n\nECODE
MEDIUMtests/smoke/t250-question-fence-never-echo.test.ts84 // The prohibition verb: matching keeps this robust to reorder.COMMENT
MEDIUMtests/unit/t251-sensor-stdout-noise.test.ts3// t251 - sensor output parsing is robust to leading stdout noise.COMMENT
MEDIUMtests/unit/t243-install-mechanism.test.ts3954 // #1406: a run that leaves another harness on another release names it, withCOMMENT
MEDIUMtests/unit/t243-install-mechanism.test.ts4200 "# kiro harness",CODE
MEDIUMtests/unit/t-active-space-includes.test.ts491 "# kiro harness",CODE
MEDIUMtests/unit/t116-directive-path-resolution.test.ts126// full path so the assertion is robust to the per-emit temp basename.COMMENT
MEDIUMtests/unit/t304-round18-acceptance-fixes.test.ts1136 // #1406: natively, a refresh that leaves another harness on an older releaseCOMMENT
MEDIUMtests/unit/t274-voice-parity.test.ts190 "### Structured questions (harness-neutral contract)",CODE
MEDIUMtests/unit/t149-codex-hook-adapter.test.ts1629 // --- Stop-hook conversational carve-out on Codex (issue #365 cross-harness) ---COMMENT
MEDIUMtests/unit/t218-kiro-ide-hook-adapter.test.ts5576// idempotent / robust-extraction behaviour the review flagged.COMMENT
MEDIUMtests/unit/t239-documentation-parity.test.ts308 "## Pick your harness",CODE
MEDIUMtests/unit/t199-learnings-memory-path.test.ts20// the workspace prefix is "spaces", not the real phase. The robust extractionCOMMENT
MEDIUMtests/unit/t151-onboarding-skeleton.test.ts146 expect(setup.match(/^#+ .+$/gm)?.[0], harness.name).toBe("# AI-DLC");CODE
MEDIUMtests/unit/t151-onboarding-skeleton.test.ts147 expect(setup.endsWith("\n## Shared AI-DLC onboarding\n\n" + NEUTRAL), harness.name).toBe(true);CODE
MEDIUMtests/unit/t266-conversation-language-rule.test.ts283 const start = body.indexOf("### Structured questions (harness-neutral contract)");CODE
MEDIUMtests/unit/t144-harness-seam.test.ts222 // T1 "harness #N = one harness/ dir + one manifest row, zero core edits"COMMENT
MEDIUMtests/unit/t147-kiro-hook-adapter.test.ts1343 // Current Stage field reflects it (robust to the fixture state alreadyCOMMENT
MEDIUMtests/unit/t147-kiro-hook-adapter.test.ts2378 // --- Stop-hook run-mode cap on Kiro (issue #365/#367 cross-harness coverage) ---COMMENT
MEDIUMtests/integration/t121-stop-hook-enforce.test.ts70// issue #365 broader reading). The hook reads the harness transcriptCOMMENT
MEDIUMtests/integration/t188-plugin-compose.serial.test.ts59const BUN = process.execPath; // the bun running this test — robust for hooksCODE
MEDIUMtests/integration/t91.test.ts257// element, but slice(-3) is robust to it (the .sh comment at t91:55-56).COMMENT
MEDIUMtests/integration/t187-park-conversational.sdk.test.ts118 // observable park signals (robust to the conductor's exact tool path):COMMENT
MEDIUMtests/harness/live-corpus.ts243 const lines = [`# ${report.title}: ${harness} at ${sha} (${stamp})`, "", `${report.sampleLine} Items driven: ${mine.CODE
MEDIUMtests/harness/custom-harness.ts302its \`## Origin\` section so the harness can verify the custom knowledge reachedCODE
MEDIUMtests/e2e/t-tui-t58-workshop-scope.serial.test.ts72// gateless known-scope path is safe too. NET: robust to both routings; the diskCOMMENT
MEDIUMtests/e2e/t-acp-kiro-utilities.serial.test.ts16// fire and the tool output would never reach an ACP surface. The robust surfaces for theseCOMMENT
MEDIUMtests/e2e/t-acp-kiro-status.serial.test.ts21// non-deterministic, never assertable). So the only robust surfaces for thisCOMMENT
MEDIUMtests/e2e/t-tui-t51-poc-scope.serial.test.ts204 // (the template's exact two-step, robust for slash commands).COMMENT
MEDIUMharness/copilot/manifest.ts140 // The pre-neutral shipped variant (#1268 made the root block harness-neutral).COMMENT
MEDIUMharness/copilot/onboarding.fills.ts28 sections_before_resumption: `## What's different on this harnessCODE
MEDIUMharness/cursor/manifest.ts79 // The pre-neutral shipped variant (#1268 made the root block harness-neutral).COMMENT
MEDIUMharness/cursor/onboarding.fills.ts28 sections_before_resumption: `## What's different on this harnessCODE
MEDIUMharness/codex/emit.ts143# hand-editable source of truth, identical on every harness (NOT a per-harnessCOMMENT
MEDIUMharness/codex/emit.ts186 : `# Bun copy-channel allowlist: deterministic framework tools stay under the harness tree.CODE
MEDIUMharness/codex/manifest.ts96 // The pre-neutral shipped variant (#1268 made the root block harness-neutral).COMMENT
MEDIUMharness/codex/onboarding.fills.ts48 sections_before_resumption: `## What's different on this harnessCODE
MEDIUMharness/kiro/manifest.ts131 // The pre-neutral shipped variant (#1268 made the root block harness-neutral).COMMENT
MEDIUMharness/kiro/onboarding.fills.ts27 sections_before_resumption: `## What's different on this harnessCODE
MEDIUMharness/kiro-ide/manifest.ts294 // The pre-neutral shipped variant (#1268 made the root block harness-neutral).COMMENT
MEDIUMharness/kiro-ide/onboarding.fills.ts29 sections_before_resumption: `## What's different on this harnessCODE
MEDIUMharness/opencode/manifest.ts90 // The pre-neutral shipped variant (#1268 made the root block harness-neutral).COMMENT
MEDIUMharness/opencode/onboarding.fills.ts26 sections_before_resumption: `## What's different on this harnessCODE
MEDIUMscripts/package.ts186// manifest.ts. DISCOVERED, not hardcoded: adding harness #N is one harness/<n>/COMMENT
MEDIUMscripts/package.ts970 // override the robust choice. The renameRulesInCompiledData backstop stillCOMMENT
MEDIUM.github/workflows/release.yml164 # Regenerate the projections from core/ + harness/ so the release gateCOMMENT
MEDIUM.github/workflows/ci.yml10# production: live harness shards run in full-suite.yml, whichCOMMENT
Verbosity Indicators32 hits · 54 pts
SeverityFileLineSnippetContext
LOWcore/tools/aidlc-testing-posture.ts1930 // A "## Step 3: Tests" heading groups the tasks under it; any otherCOMMENT
LOWcore/tools/aidlc-state.ts8155 // Step 1: Revalidate the hub-and-spoke evidence immediately before theCOMMENT
LOWcore/tools/aidlc-state.ts8193 // Step 2: Read both drafts.COMMENT
LOWcore/tools/aidlc-state.ts8209 // Step 3: Read both target files. Fail closed if either is missing.COMMENT
LOWcore/tools/aidlc-state.ts8342 // Step 7: Emit PRACTICES_AFFIRMED and record the matching state timestamp inCOMMENT
LOW⚡tests/unit/t-plan-approval-recovery-paths.test.ts142// Step 2: the plan carries the complete `## Testing Contract` block from `render`.COMMENT
LOW⚡tests/unit/t-plan-approval-recovery-paths.test.ts152// Step 3: record both tags the fingerprint command printed, then the options.COMMENT
LOW⚡tests/unit/t221-reviewer-scope-hook.test.ts1205 // Step 1: the write, owed per unit under a run-stage AND under a swarmCOMMENT
LOW⚡tests/unit/t221-reviewer-scope-hook.test.ts1212 // Step 3: the engine removes the record as it records the verdictCOMMENT
LOWtests/unit/t154-codekb-promotion.test.ts134 const step2Start = body.indexOf("### Step 2:");CODE
LOWtests/unit/t277-validate-grid-nearest-stock.test.ts183 contract.indexOf("### Step 7:"),CODE
LOWtests/unit/t277-validate-grid-nearest-stock.test.ts184 contract.indexOf("### Step 8:"),CODE
LOWtests/unit/t-dotnet-build-outputs.test.ts361 const step2 = stage.slice(stage.indexOf("### Step 2:"), stage.indexOf("### Step 3:"));CODE
LOWtests/unit/t-dotnet-build-outputs.test.ts367 const step3 = stage.slice(stage.indexOf("### Step 3:"), stage.indexOf("### Step 4:"));CODE
LOWtests/unit/t351-composer-unsaved-plans.test.ts845 for (const phrase of ["base_scope", "plan_changes", "baseScope", "you never write a scope file", "### Step 10: NothiCODE
LOW⚡tests/unit/t-code-generation-resume.test.ts853 "## Step 1: Fix the filter",CODE
LOW⚡tests/unit/t-code-generation-resume.test.ts856 "## Step 2: Tests",CODE
LOWtests/unit/t305-per-unit-attribution-receipts.test.ts3625 const step3=stage.indexOf("### Step 3: Plan Approval"); const step5=stage.indexOf("### Step 5:"); const step6=stage.CODE
LOWtests/unit/t248-codekb-scope-diff.test.ts960 const step5 = stage.slice(stage.indexOf("### Step 5:"), stage.indexOf("## Sensors"));CODE
LOW⚡tests/integration/t118.test.ts912 // Step 1: the next decision rule defers the skeleton gate -> gate is theCOMMENT
LOW⚡tests/integration/t118.test.ts917 // Step 2: the report dispatcher's STANCE branch records the typed stance andCOMMENT
LOWtests/integration/t118.test.ts934 // Step 3: the next decision rule reads the recorded stance and re-emits theCOMMENT
LOW⚡tests/integration/t49.test.ts367 // Step 1: reviewer receipt, then gate-start [-] -> [?]COMMENT
LOW⚡tests/integration/t49.test.ts371 // Step 2: reject [?] -> [R], increments Revision CountCOMMENT
LOW⚡tests/integration/t49.test.ts384 // Step 3: revise [R] -> [?]COMMENT
LOW⚡tests/integration/t49.test.ts387 // Step 4: approve [?] -> [x] (auto-advances to the next in-scope stage).COMMENT
LOW⚡tests/integration/t49.test.ts395 // Step 5: advance — approve already auto-advanced, so this replays cleanly.COMMENT
LOWtests/harness/custom-harness.ts450### Step 1: Capture the ${SNAPSHOT_ARTIFACT} artefactCOMMENT
LOWtests/harness/custom-harness.ts475### Step 2: Update stateCOMMENT
LOW⚡tests/harness/custom-harness.ts522### Step 1: Read the upstream ${SNAPSHOT_ARTIFACT} artefactCOMMENT
LOW⚡tests/harness/custom-harness.ts528### Step 2: Produce the ${PLAN_ARTIFACT} artefactCOMMENT
LOW⚡tests/harness/custom-harness.ts536### Step 3: Update stateCOMMENT
Cross-Language Confusion (JS/TS)4 hits · 20 pts
SeverityFileLineSnippetContext
HIGHcore/tools/aidlc-completions.ts91 elif [[ "$cur" == --* ]]; thenCODE
HIGHcore/tools/aidlc-completions.ts97 elif [ "\${COMP_CWORD}" -eq 2 ]; thenCODE
HIGHcore/tools/aidlc-completions.ts122 elif [[ "\${words[CURRENT]}" == --* ]]; thenCODE
HIGHtests/unit/t113.test.ts1164 print(),CODE
Fake / Example Data12 hits · 12 pts
SeverityFileLineSnippetContext
LOWcore/knowledge/aidlc-design-agent/wireframing-guide.md11- **Content**: Boxes and lines, placeholder text ("Lorem ipsum"), no color, no real dataCODE
LOWtests/unit/t-resume-kept-replies.test.ts108 filler += `\n## Extra rule section ${i}\n\n${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(60)}CODE
LOWtests/unit/t-resume-kept-replies.test.ts108 filler += `\n## Extra rule section ${i}\n\n${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(60)}CODE
LOWtests/unit/t201-swarm-batch-advance.test.ts388 `\n## Extra rule section ${i}\n\n${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(60)}\n`,CODE
LOWtests/unit/t201-swarm-batch-advance.test.ts388 `\n## Extra rule section ${i}\n\n${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(60)}\n`,CODE
LOWtests/unit/t248-steering-content-delivery.test.ts274 `${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(60)}\n`;CODE
LOWtests/unit/t248-steering-content-delivery.test.ts274 `${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(60)}\n`;CODE
LOWtests/unit/t342-construction-checkpoint-routing.test.ts2832 filler += `\n## Extra rule section ${i}\n\n${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(CODE
LOWtests/unit/t342-construction-checkpoint-routing.test.ts2832 filler += `\n## Extra rule section ${i}\n\n${"Lorem ipsum dolor sit amet, consectetur adipiscing elit. ".repeat(CODE
LOWtests/integration/t325-team-unit-claims.test.ts1602 git(outsider, ["config", "user.email", "outsider@example.org"]);CODE
LOWtests/integration/t325-team-unit-claims.test.ts1606 expect(refused.out).toContain("You cannot push commits for 'outsider@example.org'");CODE
LOWtests/harness/kiro-ide-driver.ts1042 const v = norm(e.getAttribute("placeholder")||e.getAttribute("aria-label")||e.getAttribute("data-placeholder"));CODE
Self-Referential Comments3 hits · 9 pts
SeverityFileLineSnippetContext
MEDIUM.github/workflows/full-suite.yml234 # Create the log before the background writer opens it, so theCOMMENT
MEDIUM.github/workflows/deterministic-tests.yml268 # Create the log before the background writer opens it, so theCOMMENT
MEDIUM.github/workflows/ci.yml164 # Create the log before the background writer opens it, so theCOMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHCONTRIBUTING.md126### AI-generated contributionsCOMMENT
AI Response Leakage1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHtests/unit/t352-workspace-reclassify.test.ts525 // "I've added my existing app to this folder, carry on."COMMENT
Deep Nesting2 hits · 2 pts
SeverityFileLineSnippetContext
LOWscripts/ci-live-deps.py23CODE
LOWscripts/ci-live-deps.py115CODE