Skip to content

varlock: verify the transcription provider contract and env-check workflow #63

Description

@WalksWithASwagger

Parent: https://github.com/WalksWithASwagger/kk-kb/issues/2453

Goal

Make the existing Varlock contract and env-check workflow dependable for local and agent-driven development.

Scope

  • Work from a clean origin/main worktree.
  • Reconcile the schema from committed examples and code references only.
  • Normalize the existing env-check command around agent-safe Varlock output.
  • Add one documented varlock run --inject vars -- ... command for a non-production smoke path.
  • Keep public issue and documentation text free of secret inventory and local machine paths.

Acceptance Criteria

  • Active provider/transcription configuration is covered or intentionally external.
  • The env-check workflow uses redacted output.
  • Claude Code and Codex share the same safe operating instructions.
  • Existing tests pass.
  • No value, provider setting, local path, or ignored env file is exposed or changed.

Verification

make env-check
varlock audit
varlock scan --staged

Stop Rules

  • Do not read, print, reveal, copy, rotate, encrypt, or move real secret values.
  • Do not open real .env files; derive the contract from schemas, examples, code references, and platform variable names only.
  • Do not update GitHub, Vercel, Codex, Claude, Cloudflare, or other provider values.
  • Do not deploy.
  • Stop with a concise blocker if redacted validation requires a human unlock or a missing value.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    configurationConfiguration and environment setupdev-experienceDeveloper experience and toolingin-progressAgentic runner is currently attempting the issue.securitySecurity and secrets managementtype:taskImplementation task

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions