fix: name a DB span for its operation, not "db query"

[ash-krnl]

Why

Core derives a DB span's semantic type by matching the verb inside the span name (classifyDBType, internal/content/session.go) and never reads db_operation — which this SDK already computes and sends. Two of the three DB span sites hardcoded the name:

dbapi       start_span("db query")
asyncpg     start_span("db query")
sqlalchemy  start_span(f"db {verb.lower()}")   # already correct

So every statement through sqlite3, psycopg2, mysql, pymysql or asyncpg stored as a generic database_query — a SELECT indistinguishable from a DELETE — while db_statement sat right there carrying the verb. Only the SQLAlchemy path classified correctly, which made it look like a driver quirk rather than a naming bug.

What changed

One _db_span_name(statement) helper, used at all three sites, so the convention is the rule rather than the exception. Core upper-cases the name before matching, so case here is irrelevant. A statement with no readable verb keeps "db query", the previous name — no behavior change for those.

Verification

Five statements through sqlite3 against a local stack:

Statement	Before	After
CREATE TABLE …	database_query	database_query
INSERT INTO …	database_query	database_insert
SELECT … FROM …	database_query	database_select
UPDATE … SET …	database_query	database_update
DELETE FROM …	database_query	database_delete

390 tests pass. The 5 failures under tests/instrumentation are unrelated and reproduce on an unmodified tree (git stash confirmed) — they need asyncpg and pymongo, which aren't installed in this environment.

Note for reviewers

Found while restoring span instrumentation in openbox-citadel-sdk-python (OpenBox-AI/openbox-citadel-sdk-python#1). Two related observations, not addressed here:

• install_dbapi patches the DB-API governance seam but instruments no driver, so nothing constructs a CursorTracer and no SQL raises a span at all. install_redis and install_asyncpg patch their drivers; the DB-API family has no equivalent step. Worked around SDK-side for now.
• HTTP spans set only current-convention attributes (url.full, http.request.method) and the status code never lands in attributes, so the dashboard renders no request link and no status badge — it reads attrs["http.url"] and attrs["http.response.status_code"]. Also worked around SDK-side. Both may belong here instead.

🤖 Generated with Claude Code