Verification | StagePilot

Quality Notes - StagePilot

Updated: 2026-05-30

These notes keep the repository easy to review without overstating what is production-ready.

Profile

Commands

CI

• .github/workflows/architecture-blueprint.yml
• .github/workflows/ci.yml
• .github/workflows/code-quality.yml
• .github/workflows/dependency-review.yml
• .github/workflows/pages-auto-deploy.yml
• tests/provenance.test.ts
• .github/workflows/repository-health.yml
• .github/workflows/repository-surface.yml
• .github/workflows/secret-scan.yml

Boundaries

• Demo, fixture, and synthetic-data modes must stay clearly labeled.
• Provider keys, tenant credentials, warehouse secrets, medical data, financial data, or customer logs must never be committed.
• Production claims require environment-specific validation, monitoring, rollback, and human approval paths.
• Screenshots, videos, and README claims should match the current implementation and documented commands.

Before Presenting

• README explains the user, the pain, the safety boundary, and the fast path.
• docs/service-launch-playbook.md explains the product, pilot, service, or proof-of-value angle when relevant.
• Tests or smoke checks are documented even when optional infrastructure is unavailable.
• Failure modes and unsupported claims are visible before the project is presented externally.

Checked-in evidence inventory

The following files and commands are discovered from this repository rather than inferred from a generic template. Their presence does not prove production readiness by itself; it gives reviewers a concrete path to reproduce the maintained checks.

Verification commands

• npm run verify
• npm run test
• npm run lint
• npm run typecheck
• npm run build

Test files

• src/__tests__/core/prompts/hermes-prompt.unit.test.ts
• src/__tests__/core/prompts/morph-xml-prompt.unit.test.ts
• src/__tests__/core/prompts/qwen3coder-prompt.unit.test.ts
• src/__tests__/core/prompts/shared/assistant-tool-calls-to-text.serialization.unit.test.ts
• src/__tests__/core/prompts/shared/tool-result-normalizer.normalization.unit.test.ts
• src/__tests__/core/prompts/shared/tool-role-to-user-message.conversion.unit.test.ts
• src/__tests__/core/prompts/yaml-xml-prompt.unit.test.ts
• src/__tests__/core/protocols/protocol.factory-guards.test.ts
• src/__tests__/core/utils/dynamic-tool-schema.unit.test.ts
• src/__tests__/core/utils/generated-text-json-recovery.unit.test.ts
• src/__tests__/core/utils/get-potential-start-index.unit.test.ts
• src/__tests__/core/utils/id.unit.test.ts
• src/__tests__/core/utils/on-error.unit.test.ts
• src/__tests__/core/utils/on-event.unit.test.ts
• src/__tests__/core/utils/streamed-tool-input-delta.unit.test.ts
• src/__tests__/core/utils/tool-call-coercion.unit.test.ts
• src/__tests__/core/utils/tool-choice.unit.test.ts
• src/__tests__/core/utils/tool-input-streaming.unit.test.ts
• src/__tests__/core/utils/tools.unit.test.ts
• src/__tests__/core/utils/type-guards.unit.test.ts

Continuous integration workflows

• .github/workflows/architecture-blueprint.yml
• .github/workflows/ci.yml
• .github/workflows/code-quality.yml
• .github/workflows/dependency-review.yml
• .github/workflows/pages-auto-deploy.yml
• .github/workflows/repository-health.yml
• .github/workflows/repository-surface.yml
• .github/workflows/secret-scan.yml

How to interpret the result

A passing local or CI check supports only the behavior covered by that check. It does not establish security certification, regulatory approval, clinical validity, production availability, or a customer outcome. Review the source, fixtures, environment assumptions, and failure paths before extending the result to another deployment.