B10: SQLAlchemy declarative_base FP suppression #13

New issue

Open

opened 2026-05-05 02:01:13 +02:00 by claude · 0 comments

claude commented

2026-05-05 02:01:13 +02:00

Collaborator

Ticket B10

Confirmed FP from product audit: SQLAlchemy ORM models flagged as unused-symbol. SQLAlchemy is #1 Python ORM; flagging models destroys credibility on first run of a data-driven project. Add framework heuristic for declarative_base() + DeclarativeBase patterns.

Source: Confirmed FP in 2026-05-03 product audit case A.

Detailed plan

The full ticket brief — TDD plan, current state with file:line references, target state, acceptance criteria, edge cases, hostile reviewer questions, out-of-scope — lives at .codex/MASTER/PHASE-B/B10-sqlalchemy-fp.md in the operator's local working tree (the .codex/ directory is gitignored, so this content is intentionally not in repo history; it's pre-execution planning material that gets updated as evidence comes in).

When picking up this issue, read the local file first. If you're an external contributor without access to the operator's .codex/, comment on this issue and the operator will paste the brief.

Phase context

This is part of Phase B (post-Phase-A) work. Execution is paused until dogfood evidence accumulates from real-world pyfallow integration in operator's other repos (window: 2026-05-04 → ~2026-06-15).

After the window closes, dogfood evidence drives ticket prioritization:

Tickets validated by evidence stay (and may be refined)
Tickets contradicted or made obsolete get closed with rationale
New issues with dogfood:* labels may pre-empt Phase B priority

See docs/dogfood.md and docs/dogfood-log-template.md for the protocol.

Labels applied

phase:b — phase grouping
severity:high — severity (audit-derived)
area:framework-fp — area of impact

— Migrated from .codex/MASTER/PHASE-B/ by Claude Opus 4.7 (orchestrator) on 2026-05-05 per operator request to surface Phase B/C work in Forgejo Issues so it doesn't disappear with session context.

## Ticket B10 Confirmed FP from product audit: SQLAlchemy ORM models flagged as unused-symbol. SQLAlchemy is #1 Python ORM; flagging models destroys credibility on first run of a data-driven project. Add framework heuristic for `declarative_base()` + `DeclarativeBase` patterns. **Source:** Confirmed FP in 2026-05-03 product audit case A. ## Detailed plan The full ticket brief — TDD plan, current state with file:line references, target state, acceptance criteria, edge cases, hostile reviewer questions, out-of-scope — lives at `.codex/MASTER/PHASE-B/B10-sqlalchemy-fp.md` in the operator's local working tree (the `.codex/` directory is gitignored, so this content is intentionally not in repo history; it's pre-execution planning material that gets updated as evidence comes in). When picking up this issue, read the local file first. If you're an external contributor without access to the operator's `.codex/`, comment on this issue and the operator will paste the brief. ## Phase context This is part of **Phase B** (post-Phase-A) work. Execution is **paused** until dogfood evidence accumulates from real-world pyfallow integration in operator's other repos (window: 2026-05-04 → ~2026-06-15). After the window closes, dogfood evidence drives ticket prioritization: - Tickets validated by evidence stay (and may be refined) - Tickets contradicted or made obsolete get closed with rationale - New issues with `dogfood:*` labels may pre-empt Phase B priority See `docs/dogfood.md` and `docs/dogfood-log-template.md` for the protocol. ## Labels applied - `phase:b` — phase grouping - `severity:high` — severity (audit-derived) - `area:framework-fp` — area of impact — Migrated from `.codex/MASTER/PHASE-B/` by Claude Opus 4.7 (orchestrator) on 2026-05-05 per operator request to surface Phase B/C work in Forgejo Issues so it doesn't disappear with session context.

claude added the

area:framework-fp

severity:high

phase:b

labels

2026-05-05 02:01:13 +02:00

claude added this to the Phase B — Engineering hardening milestone

2026-05-05 02:08:04 +02:00