feat(ops-run): carry harness_profile_ref and attribution refs
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 0s
Build and Publish Container Image / build-and-push (push) Successful in 19s

ACTIVITY-WP-0032-T02 / ACT-ADR-006. ops_runs grows harness_profile_ref (text,
indexed) and execution_refs (jsonb), migration 0008, threaded through the
emission path, queue projection, and run artefacts.

The important part is the enforcement, not the columns. ACT-ADR-006 says
approach_hint must never override, synthesize, or fall back from an absent or
invalid harness_profile_ref — a silent fallback would reintroduce the
claim-time routing failure of 2026-08-17. resolve_execution_selector never
consults the hint: a malformed ref raises even when a hint is present, and
ACTIVITY_CORE_REQUIRE_HARNESS_PROFILE turns an absent ref into an error once
definitions have migrated.

Validation is structural only, since the glas-harness catalogue is
authoritative and must not be mirrored. Requiring the <id>@<version> pin is
worth doing locally: GlasProfiles.resolve matches an unpinned ref against every
version and refuses it as ambiguous, so the pin converts a late failure into an
emission-time error without knowing any profile id.

Migration verified on real PostgreSQL 16: upgrade, downgrade, re-upgrade, and a
legacy-shaped row still inserts and stays claimable.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-21 14:14:08 +02:00
parent 1c4b3c592c
commit 5bd0ee5ff9
10 changed files with 428 additions and 7 deletions

View file

@ -0,0 +1,52 @@
"""add_harness_profile_to_ops_runs
Revision ID: 0008
Revises: 0007
Create Date: 2026-08-21
ACTIVITY-WP-0032 / ACT-ADR-006 profile-driven execution selection.
`harness_profile_ref` is the authoritative execution-constellation selector;
`execution_refs` carries the contract's attribution references. Both are
additive and nullable/defaulted, so existing open ops_runs stay claimable and
`approach_hint` keeps working as the legacy hint during coexistence.
"""
from typing import Sequence, Union
import sqlalchemy as sa
from alembic import op
from sqlalchemy.dialects import postgresql
revision: str = "0008"
down_revision: Union[str, Sequence[str], None] = "0007"
branch_labels: Union[str, Sequence[str], None] = None
depends_on: Union[str, Sequence[str], None] = None
def upgrade() -> None:
op.add_column(
"ops_runs",
sa.Column("harness_profile_ref", sa.Text(), nullable=True),
)
op.add_column(
"ops_runs",
sa.Column(
"execution_refs",
postgresql.JSONB(astext_type=sa.Text()),
nullable=False,
server_default=sa.text("'{}'::jsonb"),
),
)
# Operators need to answer "what is still on the legacy hint?" during the
# coexistence window, and executors filter claimable work by profile.
op.create_index(
"idx_ops_runs_harness_profile",
"ops_runs",
["harness_profile_ref"],
)
def downgrade() -> None:
op.drop_index("idx_ops_runs_harness_profile", table_name="ops_runs")
op.drop_column("ops_runs", "execution_refs")
op.drop_column("ops_runs", "harness_profile_ref")