chore(tasks): close TASK-20260910-005 and correct the open task records - #182
Merged
Conversation
TASK-20260910-005 -> done/. Its Completion summary now cites both companions: the deliverable half in CHANGELOG.md ([2026-09-10] -> item PR #178 / #179) and the unverified half in PROBLEMS.md P-004, with a row mapping each of the five unverified items to its place in P-004. Closing this task does not mean those five pass — the summary says so explicitly and repeats that agent-core must not be called production-ready yet. Two records corrected while reviewing: - TASK-20260910-004 lived in a file named 'example-task.md'. Renamed to match its id. Its content was also stale: PR #168 (moving non-workflow files out of .github/workflows/) had since merged, and the prepared SHA-pin + YAML repair work was recorded as 'none yet — blocked before commit' when it is in fact built and verified but unpushable. Validation table now carries the measured numbers (5 of 12 files fail to parse, 66 unpinned refs, 11/11 parse after the fix, 0 unpinned after the fix) and the blockers point at P-001/P-002/P-003. - TASK-20260910-003 gained a re-check section: the codeql.yml fix is still NOT on remote (both SHAs return HTTP 422 against the GitHub API, with a control SHA returning 200), plus a newly measured, separate cause of red CI in that repo — five workflows read requirements.txt at the root while the repo only has scripts/errorlog-generator/requirements.txt. That is out of this task's scope. Tracker tests: 20 passed. No workflow file touched.
fig-ai-agent Bot
added a commit
that referenced
this pull request
Sep 10, 2026
) CHANGELOG.md gains the three PRs that were not yet recorded (#180 changelog PR, #181 PROBLEMS.md, #182 the task close-out), so the [2026-09-10] section matches what actually merged. PROBLEMS.md gains two entries: - P-007 OPEN — new-crystalcastle CI: five workflows run 'pip install -r requirements.txt' but the repo has no root requirements.txt (only scripts/errorlog-generator/requirements.txt). Evidenced by run 34471137096. Separately caused from P-002/the bad-SHA issue, so fixing SHAs alone will not turn that repo green. - P-008 RESOLVED — TASK-20260910-004 had been stored in a file named example-task.md; renamed in PR #182. New task TASK-20260910-006 owns P-007. It is blocked deliberately: whether the right fix is a new root requirements.txt or repointing each workflow at the real path depends on the intended project layout, and the two workflows may want different files. Guessing would make CI pass while being wrong. Tracker tests: 20 passed. No workflow file touched. Co-authored-by: Fig Agent <agent@fig.local>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Closes
TASK-20260910-005and corrects two stale task records.TASK-20260910-005 →
done/Its Completion summary now cites both companions:
CHANGELOG.md— the delivered half ([2026-09-10] → Added, items PR feat(deliverables): add agent-core, a runnable agent task backend #178 / chore(tasks): add TASK-20260910-005 for agent-core real-world verification #179)PROBLEMS.mdP-004 — the unverified half, with a row mapping each of thefive unverified items to its place in P-004
Closing this task does not mean those five items pass. The summary says so
explicitly, and repeats that
agent-coremust not be described asproduction-ready until P-004's rows pass.
Two records corrected
TASK-20260910-004was in a file namedexample-task.md; renamed to match its id. Its content was also stale:.github/workflows/) has since merged, so that step is ticked with its PRuses:refs on currentmaingit apply --checkTASK-20260910-003gained a re-check section: thecodeql.ymlfix is still not on remote — both SHAs return HTTP 422 from the GitHub API while a control SHA returns 200. It also records a newly measured, separate cause of red CI in that repo: five workflows readrequirements.txtat the root, but the repo only hasscripts/errorlog-generator/requirements.txt. That is out of this task's scope and needs its own task.Verification
No workflow file is touched, so this push is not blocked by the App's
workflowspermission.