~bigbes/agents-dev · parade

main · last commit 13 days ago · 7g0stsfu

← Back to the parade

ah-efe.2 SPEC section 12: config surface missing Stage 3-4 + Yonote blocks; ask-user wrongly marked future work Past Stand

status: closed P3 chore milestone:v0.1.0
bd reopen ah-efe.2
Created byEugene Blikh
Ownerbigbes@gmail.com
Created2026-07-19T23:38:12Z
Started2026-08-04T23:32:44Z
Updated2026-08-04T23:38:07Z
Closed2026-08-04T23:38:07Z
Description
Section 12 lacks archive_dir, task_types on_success/on_changes_requested + routing.max_auto_routes, agentsview, yonote (claim_budget, publish_collection_id, nested qa block), mem0, tools_api, and the designer/validator/fixer roles — all shipped and validated in internal/config + config.example.yaml (which agree with each other; only SPEC lags). Also line 784 still calls the ahub tool ask-user CLI-over-HTTP variant future work, directly contradicting delivered ah-0ge.6 and SPEC section 5 principle 5 — delete the stale parenthetical. SPEC-gap audit 2026-07-20.

Depends on

  • ah-efe — Docs: SPEC refresh to Stage 3-4 + Yonote reality parent-child closed

Depended on by

Nothing depends on this issue.

No comments.

Close reason

Done in 54b2176. Section 12 had drifted ~2 stages behind the code. ADDED: archive_dir; the on_success/on_changes_requested routing keys and routing.max_auto_routes; the designer/validator/fixer roles and their design→review→fix task types; and the whole agentsview, yonote (claim_budget, publish_collection_id, nested qa), mem0 and tools_api blocks — all of which already existed in internal/config and config.example.yaml, which agreed with each other. Each got its own validation bullet with the real default (archive_dir → <work_root>/archive, max_auto_routes → 4, claim_budget → 90s, qa.bucket → ready, qa.poll_interval → 60s, tools_api → ON via a *bool), plus a lead-in naming the shared presence pattern the optional integration blocks follow. CORRECTED two outright errors: the parenthetical calling the ahub tool ask-user CLI-over-HTTP variant future work (it shipped in 07bd9d4/03f4496 — the file channel and the mid-run channel are now presented as two transports over identical board state), and the bucket-map comment calling blocked/question parked when §10 has made them real states since Stage 4 (triage is now the one parked bucket, map reordered to match domain.CanonicalBuckets()). NEW PROSE on what the config gates: the mid-run tools API, the three Yonote lanes, the mem0 lifecycle, and the Context Pack documented as deliberately having NO config surface (order and budgets are package constants). Defaults spot-verified against internal/config/config.go before commit.
  • Eugene Blikh added under epic ah-efe · 2026-07-20T02:38:11Z
  • Eugene Blikh created the issue · 2026-07-20T02:38:11Z
  • Eugene Blikh added label milestone:spec-refresh · 2026-07-20T03:08:20Z
  • Eugene Blikh removed label milestone:spec-refresh · 2026-07-20T03:10:18Z
  • Eugene Blikh added label milestone:v0.1.0 · 2026-07-20T03:11:24Z
  • Eugene Blikh changed status to in_progress · 2026-08-05T02:32:44Z
  • Eugene Blikh closed the issue · 2026-08-05T02:38:07Z
    Done in 54b2176. Section 12 had drifted ~2 stages behind the code. ADDED: archive_dir; the on_success/on_changes_requested routing keys and routing.max_auto_routes; the designer/validator/fixer roles and their design→review→fix task types; and the whole agentsview, yonote (claim_budget, publish_collection_id, nested qa), mem0 and tools_api blocks — all of which already existed in internal/config and config.example.yaml, which agreed with each other. Each got its own validation bullet with the real default (archive_dir → <work_root>/archive, max_auto_routes → 4, claim_budget → 90s, qa.bucket → ready, qa.poll_interval → 60s, tools_api → ON via a *bool), plus a lead-in naming the shared presence pattern the optional integration blocks follow. CORRECTED two outright errors: the parenthetical calling the ahub tool ask-user CLI-over-HTTP variant future work (it shipped in 07bd9d4/03f4496 — the file channel and the mid-run channel are now presented as two transports over identical board state), and the bucket-map comment calling blocked/question parked when §10 has made them real states since Stage 4 (triage is now the one parked bucket, map reordered to match domain.CanonicalBuckets()). NEW PROSE on what the config gates: the mid-run tools API, the three Yonote lanes, the mem0 lifecycle, and the Context Pack documented as deliberately having NO config surface (order and budgets are package constants). Defaults spot-verified against internal/config/config.go before commit.
Stored rows — what this pane was built from, as read
issues 1 row
id ah-efe.2
content_hash ee6d9e1db341436bcc0f1713a251ccfa45fc1d47a01f9dbd02f7f0efcd7caef2
title SPEC section 12: config surface missing Stage 3-4 + Yonote blocks; ask-user wrongly marked future work
description Section 12 lacks archive_dir, task_types on_success/on_changes_requested + routing.max_auto_routes, agentsview, yonote (claim_budget, publish_collection_id, nested qa block), mem0, tools_api, and the designer/validator/fixer roles — all shipped and validated in internal/config + config.example.yaml (which agree with each other; only SPEC lags). Also line 784 still calls the ahub tool ask-user CLI-over-HTTP variant future work, directly contradicting delivered ah-0ge.6 and SPEC section 5 principle 5 — delete the stale parenthetical. SPEC-gap audit 2026-07-20.
design
acceptance_criteria
notes
status closed
priority 3
issue_type chore
assignee NULL
estimated_minutes NULL
created_at 2026-07-19T23:38:12Z
created_by Eugene Blikh
owner bigbes@gmail.com
updated_at 2026-08-04T23:38:07Z
closed_at 2026-08-04T23:38:07Z
closed_by_session
external_ref NULL
spec_id
compaction_level 0
compacted_at NULL
compacted_at_commit NULL
original_size NULL
sender
ephemeral 0
wisp_type
pinned 0
is_template 0
mol_type
work_type
source_system
metadata �{}
source_repo
close_reason Done in 54b2176. Section 12 had drifted ~2 stages behind the code. ADDED: archive_dir; the on_success/on_changes_requested routing keys and routing.max_auto_routes; the designer/validator/fixer roles and their design→review→fix task types; and the whole agentsview, yonote (claim_budget, publish_collection_id, nested qa), mem0 and tools_api blocks — all of which already existed in internal/config and config.example.yaml, which agreed with each other. Each got its own validation bullet with the real default (archive_dir → <work_root>/archive, max_auto_routes → 4, claim_budget → 90s, qa.bucket → ready, qa.poll_interval → 60s, tools_api → ON via a *bool), plus a lead-in naming the shared presence pattern the optional integration blocks follow. CORRECTED two outright errors: the parenthetical calling the ahub tool ask-user CLI-over-HTTP variant future work (it shipped in 07bd9d4/03f4496 — the file channel and the mid-run channel are now presented as two transports over identical board state), and the bucket-map comment calling blocked/question parked when §10 has made them real states since Stage 4 (triage is now the one parked bucket, map reordered to match domain.CanonicalBuckets()). NEW PROSE on what the config gates: the mid-run tools API, the three Yonote lanes, the mem0 lifecycle, and the Context Pack documented as deliberately having NO config surface (order and budgets are package constants). Defaults spot-verified against internal/config/config.go before commit.
event_kind
actor
target
payload
await_type
await_id
timeout_ns 0
waiters
hook_bead
role_bead
agent_state
last_activity NULL
role_type
rig
due_at NULL
defer_until NULL
no_history 0
started_at 2026-08-04T23:32:44Z
is_blocked 0
labels 1 row
issue_id ah-efe.2
label milestone:v0.1.0
dependencies 1 row
id a07cc2ee-350b-571f-8b1e-af33a6bb9800
issue_id ah-efe.2
type parent-child
created_at 2026-07-20T02:38:11Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id ah-efe
depends_on_wisp_id NULL
depends_on_external NULL
events 6 rows
id 019f7cbe-91b9-7c2d-8f6c-810e841ebece
issue_id ah-efe.2
event_type created
actor Eugene Blikh
old_value
new_value
comment NULL
created_at 2026-07-20T02:38:11Z
id 019f7cda-2c3f-7e5f-99ad-94cb8d1182bb
issue_id ah-efe.2
event_type label_added
actor Eugene Blikh
old_value NULL
new_value NULL
comment Added label: milestone:spec-refresh
created_at 2026-07-20T03:08:20Z
id 019f7cdb-f62c-7877-aa9b-c0838483e14e
issue_id ah-efe.2
event_type label_removed
actor Eugene Blikh
old_value NULL
new_value NULL
comment Removed label: milestone:spec-refresh
created_at 2026-07-20T03:10:18Z
id 019f7cdc-faee-76c6-ac79-790b0958dd30
issue_id ah-efe.2
event_type label_added
actor Eugene Blikh
old_value NULL
new_value NULL
comment Added label: milestone:v0.1.0
created_at 2026-07-20T03:11:24Z
id 019fcf1f-524b-74be-9542-15abd8801050
issue_id ah-efe.2
event_type status_changed
actor Eugene Blikh
old_value {"id":"ah-efe.2","title":"SPEC section 12: config surface missing Stage 3-4 + Yonote blocks; ask-user wrongly marked future work","description":"Section 12 lacks archive_dir, task_types on_success/on_changes_requested + routing.max_auto_routes, agentsview, yonote (claim_budget, publish_collection_id, nested qa block), mem0, tools_api, and the designer/validator/fixer roles — all shipped and validated in internal/config + config.example.yaml (which agree with each other; only SPEC lags). Also line 784 still calls the ahub tool ask-user CLI-over-HTTP variant future work, directly contradicting delivered ah-0ge.6 and SPEC section 5 principle 5 — delete the stale parenthetical. SPEC-gap audit 2026-07-20.","status":"open","priority":3,"issue_type":"chore","owner":"bigbes@gmail.com","created_at":"2026-07-19T23:38:12Z","created_by":"Eugene Blikh","updated_at":"2026-07-19T23:38:12Z","labels":["milestone:v0.1.0"]}
new_value {"status":"in_progress"}
comment NULL
created_at 2026-08-05T02:32:44Z
id 019fcf24-3fc8-7845-af76-454fc201721c
issue_id ah-efe.2
event_type closed
actor Eugene Blikh
old_value
new_value Done in 54b2176. Section 12 had drifted ~2 stages behind the code. ADDED: archive_dir; the on_success/on_changes_requested routing keys and routing.max_auto_routes; the designer/validator/fixer roles and their design→review→fix task types; and the whole agentsview, yonote (claim_budget, publish_collection_id, nested qa), mem0 and tools_api blocks — all of which already existed in internal/config and config.example.yaml, which agreed with each other. Each got its own validation bullet with the real default (archive_dir → <work_root>/archive, max_auto_routes → 4, claim_budget → 90s, qa.bucket → ready, qa.poll_interval → 60s, tools_api → ON via a *bool), plus a lead-in naming the shared presence pattern the optional integration blocks follow. CORRECTED two outright errors: the parenthetical calling the ahub tool ask-user CLI-over-HTTP variant future work (it shipped in 07bd9d4/03f4496 — the file channel and the mid-run channel are now presented as two transports over identical board state), and the bucket-map comment calling blocked/question parked when §10 has made them real states since Stage 4 (triage is now the one parked bucket, map reordered to match domain.CanonicalBuckets()). NEW PROSE on what the config gates: the mid-run tools API, the three Yonote lanes, the mem0 lifecycle, and the Context Pack documented as deliberately having NO config surface (order and budgets are package constants). Defaults spot-verified against internal/config/config.go before commit.
comment NULL
created_at 2026-08-05T02:38:07Z