Agents
Enterprise agent runs (Planner → Implementer → Reviewer). Runs are persisted and actionable.
New run
Create an agent run
Runs
15
recent
Last 30 loaded
Guard
Not run
latest
Policy enforcement is the next milestone.
Recent runs
Click a run to review steps, patches, guard reports, and take actions.
| Run | Created | Status | Patches | Guard | Task | |
|---|---|---|---|---|---|---|
|
#15
|
2026-02-19 18:57
|
Failed | 2 | — |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#14
|
2026-02-19 18:48
|
Failed | 0 | — |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#13
|
2026-02-19 18:44
|
Failed | 0 | — |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#12
|
2026-02-19 18:23
|
Failed | 0 | — |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#11
|
2026-02-19 18:20
|
Failed | 0 | — |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#10
|
2026-02-19 18:13
|
Failed | 0 | — |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#9
|
2026-02-19 17:59
|
Blocked | 3 | Blocked |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#8
|
2026-02-19 17:42
|
Blocked | 3 | Blocked |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#7
|
2026-02-19 17:30
|
Blocked | 3 | Blocked |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#6
|
2026-02-19 17:00
|
Blocked | 3 | Blocked |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#5
|
2026-02-18 22:20
|
Blocked | 1 | Allowed |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#4
|
2026-02-18 22:09
|
Blocked | 1 | Blocked |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#3
|
2026-02-18 17:00
|
Succeeded | 1 | Allowed |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#2
|
2026-02-18 16:37
|
Succeeded | 1 | Allowed |
TASK: Implement NBA Injury storage schema (snapshots, enterprise-grade) using EF migrations.
Requirements
• Create Domain entities only (no EF attributes) for injuries:
o NbaInjurySnapshotBatch (identity PK; SourceName, PulledAtUtc, optional SeasonId, optional Notes, BatchGuid or BatchKey string)
o NbaPlayerInjurySnapshot (identity PK; FK to batch; AsOfUtc (or use batch PulledAtUtc); TeamId int; nullable PlayerId long?; PlayerName string; Status enum; Description string?; ReturnDateUtc DateTime?; IsMapped bool; RawJson string?; CreatedUtc)
o Enum NbaInjuryStatus (Unknown, Available, Probable, Questionable, Doubtful, Out)
• Update AppDbContext:
o Add DbSets
o Configure tables, keys, FK batch→snapshots (Restrict)
o String max lengths (PlayerName 80, SourceName 40, Status as int, Description 300, RawJson max)
o Indexes:
Batch: (SourceName, PulledAtUtc)
Snapshot: (TeamId, AsOfUtc) and (PlayerId, AsOfUtc) (PlayerId nullable -> still index)
Snapshot unique: (BatchId, TeamId, PlayerName) (or (BatchId, TeamId, PlayerId) if mapped) — choose safe uniqueness
• Add migration + update DB
Constraints
• Domain doesn’t depend on anything.
• DbContext not used from Pages.
• UTC everywhere.
Deliverable
• PatchSet containing entity files + DbContext mapping + migration.
Reviewer must validate
• Snapshot model supports multiple pulls/day
• Indexes are sane and scalable
• Migration builds
|
Open |
|
#1
|
2026-02-18 08:28
|
Succeeded | 1 | — |
Add PatchGuard enforcement for rule: ‘Never access DbContext from Razor Pages’ by scanning diffs for new AppDbContext( or DbContext usage inside Pages/**/*.cshtml.cs. Block apply with a GuardViolation and show it in the Agents UI.
|
Open |
Showing latest 15 runs.