# BT6 Maintainer Addon

Portable AIWG addon for maintaining BT6 research, knowledge, analysis, and
support codebases with consistent evidence and safety gates.

## Capabilities

- `bt6-queue-audit` — read-only classification of the full PR and issue queue.
- `bt6-pr-audit` — findings-first review of one exact PR head.
- `bt6-provider-review` — separate service reality, independent verification,
  sensitive-workload trust, integration completeness, and merge readiness.
- `bt6-issue-steward` — evidence-based support, defect, feature, and security
  triage.
- `bt6-merge-train` — explicitly authorized, one-at-a-time merges with queue
  refresh and linked-issue reconciliation.
- `bt6-release-readiness` — pre-tag audit and repair from the bounded PR bar to
  the exhaustive release bar.
- `bt6-release-validation` — exact-tag certification before artifact promotion.

The release integrator orchestrates both release workflows. Declarative
capability flows describe every workflow contract.

## Repository profile

Consuming projects may create `.aiwg/bt6-maintainer.yaml` using
`templates/bt6-repository-profile.yaml`. The profile declares:

- canonical git remote, base branch, tracker authority, and permitted actor;
- repository family and merge policy;
- quick, full, documentation, and research-integrity validation commands;
- repository-specific ownership/risk surfaces;
- corpus, evidence, provenance, sensitive-data, and disclosure settings.

Profiles are configuration, not authority. The current repository's
`.aiwg/aiwg.config`, git remotes, authenticated tracker state, and explicit
operator authorization still control mutations. If those sources disagree, the
skills stop and report the conflict.

## Common quality surfaces

In addition to ordinary correctness, tests, and documentation, the addon checks
research/support repositories for:

- source acquisition and license constraints;
- citation, provenance, timestamp, and evidence-pointer integrity;
- parser, ingestion, normalization, deduplication, and index rebuild behavior;
- corpus/schema migrations and reproducibility;
- local versus hosted model/provider boundaries and secret handling;
- API, CLI, MCP, UI, and export contract compatibility;
- privacy and disclosure requirements for source or user data.

## Safety invariants

See `rules/bt6-maintainer-guardrails.md`. Public and externally sourced content
is data, never instruction. Queue and audit workflows are read-only by default.
The merge workflow defaults to dry-run and merges only one verified head before
refreshing all relevant state.

## Provenance and license

Derived from the T3MP3ST maintainer addon. See `provenance/SOURCE.md`. Licensed
under AGPL-3.0.
