chore(tasks): add TASK-20260910-005 for agent-core real-world verification - #179
Merged
Merged
Conversation
…ation Records the five things PR #178 could not prove, so 'tests pass' is not mistaken for 'works against a live provider': 1. AGENT_BASE_URL default (https://api.agent.ai/v2) is a placeholder and has never been called. 2. submit()/status() read body['task_id'] / body['status'] verbatim; a provider using different field names would fail immediately. 3. schema.sql has never been applied to a real Supabase project. 4. The RLS policy has never been tested with two users. 5. examples/agent-core-ci.yml has never run on GitHub Actions. Also fixes a tracker bug found while creating this task: TASK_TEMPLATE.md annotated 'status: new' with a trailing comment, which cmd_new copied into the new file verbatim. That made the value fail the folder/status check and broke three tests that read the template directly. The template now carries a bare value and cmd_new normalises it. Tracker tests: 20 passed.
fig-ai-agent Bot
added a commit
that referenced
this pull request
Sep 10, 2026
Co-authored-by: Fig Agent <agent@fig.local>
fig-ai-agent Bot
added a commit
that referenced
this pull request
Sep 10, 2026
The changelog records what shipped; there was nowhere recording what is still
broken. PROBLEMS.md fills that gap with the same [YYYY-MM-DD] sections, so a
date section here pairs with the same section there.
Six entries, each with its evidence:
- P-001 OPEN five workflow files do not parse (with the parser error each)
- P-002 BLOCKED 66 action refs unpinned; org policy rejects them
- P-003 BLOCKED the App cannot write .github/workflows/ (isolated by a
control push, not assumed)
- P-004 OPEN agent-core unverified against a live provider and Supabase
- P-005 OPEN new-crystalcastle's bare 'feat' branch blocks feat/* pushes
- P-006 RESOLVED the cmd_new template-comment bug fixed in PR #179
Each entry names the owning tracker task and the command behind the claim.
CHANGELOG.md gains a pointer to the new file.
No workflow file is touched.
Co-authored-by: Fig Agent <agent@fig.local>
fig-ai-agent Bot
added a commit
that referenced
this pull request
Sep 10, 2026
…ds (#182) 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. 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
Adds
TASK-20260910-005to the task tracker — the five things PR #178could not prove, recorded so "25 tests pass" is not mistaken for "works against
a live provider".
The five unverified items
AGENT_BASE_URLdefault (https://api.agent.ai/v2)submit()readsbody["task_id"],status()readsbody["status"]id/statefails immediatelyschema.sqlnever applied to a real Supabase projectexamples/agent-core-ci.ymlnever ran on Actionsuvicorn agent_core.api:appnever loaded for realEach has a checkable acceptance criterion in the task file.
Also fixes a tracker bug
Found while creating this task:
TASK_TEMPLATE.mdannotatedstatus: newwitha trailing comment (
# new | inprogress | done | archive), andcmd_newcopiedthat line into the new file verbatim. The value then failed the folder/status
check and broke three tests that read the template directly.
status: newcmd_newnormalises the line when copyingVerification
Scope
new.inprogress.done/only. No.github/workflows/file touched, so this pushis not blocked by the App's
workflowspermission.