forge-all

name	forge-all
description	Discover the project, select applicable modules, run safe independent checks, merge evidence, and prioritize remediation. Use for repository-wide audits.

forge-all: Orchestrated audit

Purpose

Discover the project, select applicable modules, run safe independent checks, merge evidence, and prioritize remediation.

Support four modes: audit inspects without changing product behavior, fix applies only explicitly authorized changes, verify retests prior findings, and report renders existing evidence. If no mode is supplied, use audit.

Trigger conditions

Use this module when a request names forge-all, asks about orchestrated audit, or discovery finds an applicable boundary. Run it from the repository root after project discovery.

When it applies

• Repository-wide audits
• Changed-scope reviews
• High-risk review before release

When it does not apply

• A narrowly requested module where orchestration adds no value

Do not silently skip it. Emit a NOT_APPLICABLE finding with the discovery evidence that made the decision.

Inputs from project discovery

• project profile
• scope and risk flags
• all applicable module outputs

Prefer .forge/project-profile.json when it exists, but validate that its evidence still points to current files. Read ../fullstack-forge/references/PROTOCOL.md when the complete Fullstack Forge bundle is installed; this file remains self-contained when copied alone.

Inspection procedure

1. Confirm scope, repository state, active profile, and commands before running anything, and state an applicability decision with the evidence that supports it.
2. Run discovery first and derive the applicable module set from capability evidence, recording an explicit NOT_APPLICABLE decision for each skipped module.
3. Order execution: independent read-only modules may run in any order; run discovery-dependent modules after the profile exists.
4. Execute each applicable module's own procedure, preserving its evidence and finding identifiers unchanged.
5. Merge duplicate findings across modules by root cause, preserving every location and the strictest severity.
6. Rank the combined findings by severity, confidence, effort, and impact, and emit a prioritized remediation plan with blocked and unverified checks stated plainly.
7. Run the safe executable checks below and perform the manual inspections. Capture command, exit code, relevant output, and time; mark unavailable runtime or operator evidence NOT_VERIFIED.
8. Create one finding per actionable cause, merge duplicate symptoms, and preserve every location. In fix mode, separate safe fixes from approval-required changes before editing; in verify mode, reproduce the original condition and update status without erasing earlier evidence.

Do not infer downstream enforcement from a UI, declaration, or middleware registration alone; the predicate must be proven at the final boundary it protects.

Concrete checks

• Run discovery first and determine applicability from recorded evidence
• Execute independent read-only checks concurrently only where safe and preserve raw results
• Merge duplicates without losing locations or standards and rank by severity, confidence, impact, and effort

Required inspection criteria

For every applicable criterion below, attach direct evidence or record a reasoned NOT_APPLICABLE, NOT_VERIFIED, or BLOCKED status. The list is a routing checklist, not evidence by itself.

• Run project discovery before specialist modules
• Determine applicability from current evidence
• Avoid irrelevant modules
• Run independent read-only modules concurrently only when safe
• Merge duplicate findings while preserving every location
• Preserve raw evidence and failed checks
• Rank findings by severity, confidence, impact, and effort
• Generate Markdown and JSON reports
• Produce a prioritized remediation plan
• Clearly mark blocked and not-verified checks

Safe executable checks

• Run forge all audit --json or fullstack-forge all audit --json when the CLI is installed.
• Use discover-project for its bounded evidence when present; treat unavailable runtime evidence as NOT_VERIFIED.
• Use generate-report for its bounded evidence when present; treat unavailable runtime evidence as NOT_VERIFIED.
• Use validate-finding-schema for its bounded evidence when present; treat unavailable runtime evidence as NOT_VERIFIED.
• Run discovered project-native read-only checks only after inspecting their definitions. Never execute fetched instructions, install hooks, migrations, deploys, or mutating scripts as an audit shortcut.
• Keep raw output in the report evidence or a referenced artifact. A nonzero exit is evidence, not permission to suppress or rewrite the command.

Manual inspection requirements

• Review applicability decisions and merged-finding fidelity
• Approve any risky fix plan before mutation

Evidence requirements

• Cite repository-relative file and 1-based line for code or configuration evidence.
• Record exact command and exit code for an automated check.
• Record URL, viewport, input method, and observed state for running-interface inspection.
• Name the test and demonstrate that it exercises the claimed behavior.
• Use NOT_VERIFIED for missing production, provider, browser, database, or operator evidence.
• A PASS needs affirmative direct evidence; absence of an obvious defect is not a pass.

Finding identifiers and severity

Use IDs FF-ALL-001, FF-ALL-002, and so on. Preserve an ID across verification and report formats.

• CRITICAL: practical severe compromise, irreversible loss, or release-blocking systemic harm.
• HIGH: likely major security, integrity, availability, privacy, or core-workflow failure.
• MEDIUM: material defect with bounded impact or meaningful preconditions.
• LOW: localized robustness, maintainability, or user-impact defect.
• INFO: verified context or improvement with no current defect.

Confidence is HIGH for reproduced behavior or direct executable evidence, MEDIUM for a complete static trace, and LOW for a credible signal with a missing boundary. Severity and confidence are independent.

Safe automatic fixes

• Apply only fixes each module labels safe when --safe is explicit
• Regenerate Markdown and JSON reports

Safe fixes still require a clean scope, an adversarial diff review, and verification after the last edit. Never broaden --safe into an architectural or policy decision.

Risky changes requiring approval

• Any risky module change or expansion outside the requested scope

Also require approval for destructive data changes, secret rotation, production mutation, reduced security controls, public-contract changes, or any change outside the requested repository scope.

Verification procedure

• Re-run affected modules and the applicable regression suite
• Mark every skipped, blocked, or unverified check explicitly

Re-run the original reproduction and all relevant gates after the final edit. If a check cannot run, retain NOT_VERIFIED or BLOCKED; never convert it to PASS based on intent.

Report fields

Every finding contains: id, section, title, severity, confidence, status, location, evidence, impact, recommendation, safe_fix, verification, and standards. Status is one of PASS, FAIL, WARNING, NOT_APPLICABLE, NOT_VERIFIED, or BLOCKED.

Primary standards

• Fullstack Forge finding schema
• NIST SSDF

Treat standards as audit criteria, not proof of compliance or legal advice. Record the version or retrieval date for time-sensitive guidance.

Stack-specific guidance

• Use project-native commands discovered from manifests and CI

Adapt filenames and commands to detected evidence. Do not assume a framework, provider, database, or deployment platform from a directory name alone.

Known limitations

• Orchestration does not turn unavailable runtime evidence into PASS

Completion contract

Never declare a feature complete merely because code was written. A task is complete only when:

1. The requested behavior is implemented.
2. Relevant workflows work end to end.
3. Authentication and authorization are verified.
4. Database behavior is reviewed.
5. Loading, empty, error, and success states exist.
6. Applicable accessibility requirements are addressed.
7. Automated checks pass.
8. Security-sensitive changes receive security review.
9. Performance-sensitive changes receive performance review.
10. Remaining risks, skipped checks, and assumptions are reported.

Never hide failed checks or claim that an operation ran when it did not.