sscoble/speckl
1
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

[speckl#37.2] Fix top P0+P1 TS generator bugs from #37.1 triage #40

New issue
Closed
opened 2026-06-02 02:49:31 +00:00 by agent-cos · 3 comments
agent-cos commented 2026-06-02 02:49:31 +00:00
Copy link

Problem

Parent #37 is blocked. The triage in #37.1 enumerated the bugs. This ticket is the bounded fix.

Scope

Fix all P0 bugs (block all examples) and all P1 bugs (block ≥1 example) from the #37.1 triage table. Defer P2 bugs to a follow-up.

Acceptance Criteria

  • Every P0 bug from #37.1 has a fix commit referencing the bug_id
  • Every P1 bug from #37.1 has a fix commit referencing the bug_id
  • Affected example specs that triggered each P0/P1 now compile without errors
  • Test suite passes (or new tests added if none exist)
  • Comment on this issue with: list of commits, example specs verified clean

TDD (per Scott's May 24 directive)

  1. Write a failing test for each bug FIRST
  2. Implement the fix
  3. Test passes
  4. No exceptions

Why this exists

Each P0/P1 bug is a bounded code change. A subagent can fix 1-3 in 600s. A child with a specific list is dispatchable; the parent with "fix all bugs" is not.

Depends on

  • speckl#37.1 (triage complete)

Blocks

  • speckl#37.3 (final verification)
## Problem Parent #37 is blocked. The triage in #37.1 enumerated the bugs. This ticket is the bounded fix. ## Scope Fix all P0 bugs (block all examples) and all P1 bugs (block ≥1 example) from the #37.1 triage table. Defer P2 bugs to a follow-up. ## Acceptance Criteria - [ ] Every P0 bug from #37.1 has a fix commit referencing the bug_id - [ ] Every P1 bug from #37.1 has a fix commit referencing the bug_id - [ ] Affected example specs that triggered each P0/P1 now compile without errors - [ ] Test suite passes (or new tests added if none exist) - [ ] Comment on this issue with: list of commits, example specs verified clean ## TDD (per Scott's May 24 directive) 1. Write a failing test for each bug FIRST 2. Implement the fix 3. Test passes 4. No exceptions ## Why this exists Each P0/P1 bug is a bounded code change. A subagent can fix 1-3 in 600s. A child with a specific list is dispatchable; the parent with "fix all bugs" is not. ## Depends on - speckl#37.1 (triage complete) ## Blocks - speckl#37.3 (final verification)
sscoble commented 2026-06-02 03:26:35 +00:00
Owner
Copy link

Status note from CoS (2026-06-01 20:13 PT)

Sibling ticket #39 (triage) timed out on first dispatch. Re-dispatching with tighter scope next cycle. This ticket (#40) depends on #39 — will dispatch once triage ships. No action needed here yet.

## Status note from CoS (2026-06-01 20:13 PT) Sibling ticket #39 (triage) timed out on first dispatch. Re-dispatching with tighter scope next cycle. This ticket (#40) depends on #39 — will dispatch once triage ships. No action needed here yet.
sscoble commented 2026-06-02 03:51:25 +00:00
Owner
Copy link

Status (2026-06-02 03:30 PT)

This ticket depends on #39 (triage) which has been blacklisted with 2 consecutive 600s timeouts. Speckl#39 is now permanently de-listed. Since this ticket cannot be dispatched until a triage list exists, recommend Scott consider:

  • Option A: Manually run the triage (or accept that no P0/P1 bugs need fixing because verification #38 confirmed 19/19 examples compile clean).
  • Option B: Close this ticket as WONT-FIX with rationale: "verification pass confirmed no P0/P1 bugs; no fixes needed."
  • Option C: Create a smaller bounded child (e.g., one ticket per generator file) for subagent dispatch.

Unassigned from agent-engineering while blocked.

## Status (2026-06-02 03:30 PT) This ticket depends on #39 (triage) which has been blacklisted with 2 consecutive 600s timeouts. Speckl#39 is now permanently de-listed. Since this ticket cannot be dispatched until a triage list exists, recommend Scott consider: - **Option A:** Manually run the triage (or accept that no P0/P1 bugs need fixing because verification #38 confirmed 19/19 examples compile clean). - **Option B:** Close this ticket as WONT-FIX with rationale: "verification pass confirmed no P0/P1 bugs; no fixes needed." - **Option C:** Create a smaller bounded child (e.g., one ticket per generator file) for subagent dispatch. Unassigned from agent-engineering while blocked.
sscoble commented 2026-06-02 23:18:08 +00:00
Owner
Copy link

Closure (2026-06-02 22:45 UTC)

Closing as superseded by the 6 atomic children created from the 2026-06-02 11:55 PT decomposition:

  • #41 (B4 difference operator) — 4 ACs
  • #42 (B3 if/then/else) — 4 ACs
  • #43 (B1 let/forall stubs) — 5 ACs
  • #44 (B5 init block parser) — 4 ACs
  • #45 (B2 constraint/verify) — 5 ACs
  • #46 (B6 readonly + JSDoc) — 4 ACs

This ticket's broader scope ("fix all P0+P1 bugs") is now covered by the bounded children. Each child is atomically releasable per the 2026-06-02 decomposition directive. Dispatching children in priority order in the 2026-06-02 22:45 UTC cycle.

## Closure (2026-06-02 22:45 UTC) Closing as **superseded by the 6 atomic children** created from the 2026-06-02 11:55 PT decomposition: - #41 (B4 difference operator) — 4 ACs - #42 (B3 if/then/else) — 4 ACs - #43 (B1 let/forall stubs) — 5 ACs - #44 (B5 init block parser) — 4 ACs - #45 (B2 constraint/verify) — 5 ACs - #46 (B6 readonly + JSDoc) — 4 ACs This ticket's broader scope ("fix all P0+P1 bugs") is now covered by the bounded children. Each child is atomically releasable per the 2026-06-02 decomposition directive. Dispatching children in priority order in the 2026-06-02 22:45 UTC cycle.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
lagrangia-v1.1
ifblock-fix
now-fix
lagrangia-score
fix/speckl-55-ltl-inner-identifier-scope
fix/parser-precondition-postcondition
fix/compiler-enum-rewrite-parser-quotes
No results found.
Labels
Clear labels   
blocked

   
bug

   
design

   
docs

   
engineering

   
feature

   
infra

   
priority:high

   
priority:low

   
priority:medium

   
question
No labels
blocked
bug
design
docs
engineering
feature
infra
priority:high
priority:low
priority:medium
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: sscoble/speckl#40
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?