<!-- source: openspec/changes/a4-document-the-11-openspec-agent/proposal.md -->

---
title: Document 11 openspec-* agent slugs in db/entities.md
audience:
  - founder
  - architect
  - executor
---

# Document 11 openspec-* agent slugs in current/db/entities.md

> **Affects capability spec:** `openspec/current/db/entities.md`

## Why

`current/db/entities.md` documents only the 6 v1 agent slugs for `forge_findings.agent`. Eleven `openspec-*` slugs introduced during the `add-openspec-audit-pass` work are absent. Forge audit DA-007 flagged this as critical; while the underlying column is free-text (no CHECK constraint, no crash risk), the stale spec misleads implementors about valid values and breaks spec-completeness checks (`pnpm openspec:regen`). The archived change folder is frozen, so the fix must land in `current/`.

## What Changes

- **Extend `forge_findings.agent` value table** — add all 11 `openspec-*` slugs with a one-line description each.
- **Codify the free-text contract** — add an explicit note that the column is `text NOT NULL` with no CHECK constraint; the UI renders whatever string is stored.

## Impact

- Spec files touched: `openspec/current/db/entities.md`
- Packages affected: none (documentation-only change)
- Downstream surfaces: `packages/forge` (slug constants / `--persist` path), `apps/studio` (findings UI renders agent label)

## Out of scope

- DB migrations — the column requires no schema change
- Backfilling historical findings rows with corrected slugs
- Editing the frozen archive at `openspec/archive/2026-06-02-add-openspec-audit-pass/`
- Adding a CHECK constraint or enum type to enforce slug values at the DB layer
