issues — bigbes/agents-dev

id	content_hash	title	description	acceptance_criteria	notes	status	priority	issue_type	assignee	estimated_minutes	created_at	created_by	owner	updated_at	closed_at	external_ref	compacted_at	compacted_at_commit	original_size	metadata	close_reason	last_activity	due_at	defer_until	started_at
ah-xuc.7	62a6806491ee4096a8206ec5b958064c69d772d7f8376188ca61bbfc8a354510	httpapi: Vikunja webhook receiver with HMAC verification	POST /webhooks/vikunja as a reconciler poke. Design principle 1: a webhook only triggers an immediate iteration; polling stays the source of truth because Vikunja delivers webhooks once, without retries. Deps gain WebhookSecret string and a Webhook hook (non-blocking; cmd wires it to Reconciler.Poke). Empty secret = feature disabled: the route is not registered at all. Verification: X-Vikunja-Signature carries hex HMAC-SHA256 over the raw request body; compute over the exact bytes read and compare with hmac.Equal; missing or wrong signature = 401 with a terse body that echoes nothing back; cap the body at 256 KiB. After verification decode {event_name} best-effort for the log line only — the payload is otherwise untrusted and unused. Respond 200 fast, call the hook once per verified delivery. Exposing the loopback listener to Vikunja is infra (ah-k23), not this bead.	go test ./internal/httpapi/... green, go vet clean; tests: a valid computed signature pokes the hook and returns 200; tampered body, wrong secret, and missing header return 401 without invoking the hook; oversized body rejected; unset secret leaves the route absent and existing routes unaffected		closed	2	feature	Eugene Blikh	NULL	2026-07-13T05:15:43Z	Eugene Blikh	bigbes@gmail.com	2026-07-13T06:22:50Z	2026-07-13T06:22:50Z	NULL	NULL	NULL	NULL	�{}	61400ae; HMAC discipline verified (full-read-before-verify, uniform 401, constant-time compare); review clean	NULL	NULL	NULL	2026-07-13T05:44:26Z
ah-xuc.8	d48513a80bea7b4ebcfc74514ea6d2a7079500b44f1b1eebca7b445db6e316b7	reconcile: spec-driven claim, Triage bounce, parked buckets, per-run timeout	Claim-path integration of Stage 2. Same-package constraint: this bead owns the internal/reconcile edits for the claim path; the finalize-path bead must not start until this one is committed. iterate(): canonical buckets triage/blocked/question become parked buckets — superviseRuntime only (detached supervision persists runtime truth; no claim, no kill, no card moves, no comments). They are never claim sources and never terminal targets. Blocked and Question get real semantics in Stage 4; Stage 2 only reserves and parks them. claim(): resolve the Task Spec via internal/spec from BoardTask.Labels plus Description. A validation failure bounces: MoveToBucket(triage) first, then one diagnostic comment listing the problems verbatim plus a hint to fix the spec and drag back to Ready, then event spec_rejected — move-then-comment discipline so a persistent move failure cannot spam comments; appendEvent dedup applies. No record is persisted and the card never goes to Failed for spec problems. Warnings (unknown fields) never block: append them to the claim comment. Success path: the spec role name resolves through cfg.Roles; model override applies; the prompt renders over the frontmatter-stripped Body; resolved SkillPaths go into StartSpec.Skills; the effective timeout (spec override or config default) goes into StartSpec.Timeout and is persisted as Run.Timeout. check(): deadline enforcement uses run.Timeout when positive, else cfg.Timeout — in both the running arm and the degraded neither-state arm. Extend fakes_test.go (fake runner captures Skills and Timeout; board tasks carry Labels) and cover: each bounce class end to end, merge precedence reaching StartSpec, parked buckets neither claim nor kill while detached supervision still finalizes a finished runtime, per-run timeout enforced at the right boundary with the fake clock — both shorter and longer than the config default.	go test ./internal/reconcile/... green, go vet clean; bounce tests assert move-before-comment ordering and zero Failed transitions; parked-bucket tests assert no board writes; timeout tests cover run.Timeout smaller and larger than the config default	Additional: pre-existing gofmt drift in internal/reconcile/reconcile_test.go (comment alignment around lines 983-984 and 1345, present since before Stage 2) — run gofmt -w on the files you touch and fold the fix into this bead's commit.	closed	2	feature	Eugene Blikh	NULL	2026-07-13T05:16:00Z	Eugene Blikh	bigbes@gmail.com	2026-07-13T06:57:17Z	2026-07-13T06:57:17Z	NULL	NULL	NULL	NULL	�{}	9823250 + 06_pin commit; review merge-ready (all SPEC section-10 invariants traced clean); validator 10/10 incl. e2e byte-identical for spec-less tasks; adopt-over-bounce coverage gap closed	NULL	NULL	NULL	2026-07-13T06:23:38Z
ah-xuc.9	5c6568a5b55170ea70ba05fb8c0af96dcfaf33b977424934bdb124f8c46e5c10	reconcile: publish review branch, watchdog on stale events, Telegram notifications	Finalize-path integration of Stage 2. Starts only after the claim-path bead is committed (same package). Publish: in finalize, on the success path with moveCard set, call runner.Publish before posting the In Review comment. Zero PublishInfo = not configured, plain comment. Success adds a review link line (WebURL, falling back to RemoteURL plus branch) and appends event published. Failure degrades: the comment still posts with a push-failed line carrying the error, event publish_failed (deduped). A refinalize repeats the push — pushing an up-to-date branch is idempotent and fine. Watchdog: in the check() running arm, when cfg.StallTimeout > 0 and now minus max(st.LastEvent, run.StartedAt) exceeds StallTimeout, the run is stalled: kill and finalize with OutcomeStalled, exit -1 (share the timeoutKill shape). The neither-state arm stays deadline-only — no events are observable there. failureComment renders the stalled outcome distinctly (agent went silent, not merely slow). Notifications: Notify best-effort — log on error, never gate the flow, guard the nil notifier — after a successful move plus comment: finalize with moveCard (success and failure including timeout and stalled) and the spec bounce. Text: outcome emoji, task id and title, outcome word, cost when known, and the human task link built from vikunja web_url. Tests with fakes: the In Review comment contains the review link; publish failure still posts the comment; the stall kill fires just past the boundary and not before; a run with events flowing but past run.Timeout still dies by deadline; notify recorded after move and comment in that order; nil notifier safe; a notify failure does not fail finalize.	go test ./internal/reconcile/... green, go vet clean; ordering asserted move then comment then notify; stalled and timeout outcomes distinguishable in comments, events, and notifications	Coordinator refinement: publishing arrives via a new optional reconcile Deps field of type ports.Publisher (nil-guarded like Notifier); finalize publishes only when the field is non-nil. cmd wires the runner into it in ah-xuc.10.	closed	2	feature	Eugene Blikh	NULL	2026-07-13T05:16:07Z	Eugene Blikh	bigbes@gmail.com	2026-07-13T07:35:20Z	2026-07-13T07:35:20Z	NULL	NULL	NULL	NULL	�{}	d5d1efc + 64a7216 (review fix: bounded publish ctx via publish_timeout knob, zero-delta recorder covers publish/notify); reviewer merge-ready after fix, validator 10/10 with all 24 subtests by name	NULL	NULL	NULL	2026-07-13T06:57:43Z
ah-ydx	8735805091c14831debfbdb26c8f324f6832e8b80ebcc313e05201a7bd3c85f8	Stage 3: mem0 memory lifecycle + Context Pack	Per SPEC SS14.3: mem0 REST client (X-API-Key, scoping user_id=proj:<slug>/global, run_id=task:<id> — agent_id filter is buggy upstream); load cascade on claim -> .task/CONTEXT.md section; save on Done; post-run summarizer role; Context Pack builder (task+thread+parent-chain+memory+git, ~40k char budget, deterministic order, truncate-from-tail).			open	3	epic	NULL	NULL	2026-07-12T23:36:28Z	Eugene Blikh	bigbes@gmail.com	2026-07-12T23:36:28Z	NULL	NULL	NULL	NULL	NULL	�{}		NULL	NULL	NULL	NULL

~bigbes/agents-dev · issues