5 Commits

Include renames

Author	SHA1	Message	Date
weichen	f1302ed5b3	Enable canonical versioned Go module consumption ... Why: Allow consumers to download an immutable module revision without nested source checkouts or local path replacements. Evidence: SELF package tests and the prior canonical-path rejection are recorded in the Dev dependency-workspace task card; remote consumption is replayed against the committed candidate. Impact: Change the module identity and its Go imports while preserving API behavior. Existing historical submodule revisions remain buildable. Refs: Versioned dependencies U1/U3; feature/dependency-workspace	2026-10-13 15:47:16 +00:00
weichen	5cd67be982	Close request atomicity: locked message append, card versions, atomic rate limit, recovery holds (U3 slice 1) ... Why: the approved plan U3 (KTD3/KTD7/KTD10 plus minimal recovery isolation) requires concurrent submits to not silently overwrite, unknown-side-effect runs to never auto-resume, and the shared rate limiter to degrade conservatively instead of failing open. Evidence: full backend suite green twice-relevant paths against real PostgreSQL 18.6 and Redis (isolated instance) and on SQLite; new tests - card_version_test (concurrent single winner), recovery_hold_test + recovery_holds_test (skip/release/fail-closed CRUD), ratelimit atomic-window and degraded-fallback tests. Impact: AppendMessageWithRequest now allocates seq under the conversation advisory lock in one transaction; activity_cards gain version (v19) with SaveCardVersioned/GetCardVersion/CardVersion and cardsvc user mutations (status/pin/action/resolve-by-ref) return 409-mapped conflicts while system mirrors keep blind writes; recovery_holds (v20) with admin list/release endpoints and fail-closed resume skip; Redis limiter uses one Lua INCR+PEXPIRE script and falls back to a per-instance limit with a Degraded counter. Refs: proposals/2026-10-11-collaboration-storage-and-distribution.md U3 KTD3/KTD7/KTD10; R3/R6/R7/R8.	2026-10-11 04:37:50 +00:00
weichen	43297795f5	Keep original materials and cleared results reachable across turns ... Why: Real-run before/after evidence (phase01 card) showed later turns never re-read the uploaded source (0 original reads in plan-followup) because the attachment only existed in the current turn's injection and the context window hard default was 32000 chars - a 25k-char transcript tripped the clear-on-first request, replacing old tool results with a pointer the model has no tool to follow. MiniMax is an interleaved-thinking model whose docs require <think> blocks in assistant history; dropping them degrades later turns. Evidence: SELF - new tests TestThinkReplayWrapsAssistantHistory, TestContextWindowScalesFromTokens, TestThinkReplayEnabled, TestPersistInputTextsAndListWorkspaceInputs; go test ./internal/... passes; live before/after comparison on the golden task set recorded on the phase02 task card per the new policy clause. Impact: models.chat.contextWindow/outputReserve/contextBuffer (tokens, defaults 128k/16k/4k) drive the in-run clear threshold, converted to chars; cleared tool results spill to <sandbox>/.agent/results with readable paths; attachment parse text persists as inputs/<name>.md and the env section lists all workspace inputs every turn; context.thinkReplay (auto|on|off, auto = MiniMax) replays thinking blocks into request-side assistant history only.	2026-10-09 14:28:39 +00:00
weichen	97bc5093bd	Resume gracefully-interrupted subagents and take the RunState repair pins (N3 WP1) ... Why: InterruptRunning wrote done.json{status:interrupted} for every child, and ResumeInterruptedChildren skipped anything with done.json — graceful shutdowns never resumed (only SIGKILL-style deaths did). done markers now split by status: terminal states block resume, interrupted does not. Nested pins carry repairOrphanTail and the N6 fix. Evidence: go test -count=1 ./... green; TestResumeAfterGracefulInterruptMarker (resumed once and only once), TestResumeSkipsCompletedMarker (terminal states still block). Impact: after any restart, interrupted children with a stored request re-spawn exactly once regardless of how the process stopped. Refs: Agent-Native#30, Agent-Squad#34, N3 plan WP1	2026-10-07 15:05:57 +00:00
weichen	358cfe017c	Give subagents per-run transcripts, resume, persisted notices, and the Background request field (N2 WP5) ... Why: child runs had no independent transcript, no resume path (sealed interrupted only), in-memory completion notices lost on restart, and the subagent Background declaration had no consumer. Evidence: go test -count=1 ./... green; TestSubagentTranscriptFilesWritten (request/transcript/done files), TestResumeInterruptedChildrenRespawns (re-spawn with original task + transcript-path hint, resumed.json idempotent), TestNoticesPersistAndRedeliverAfterRestart (persist → reload → deliver → delete), migration v17 pending_notices with up/down on both dialects. Impact: per-run transcript dirs under the workspace root (auxiliary, write failures never abort spawns); interrupted children with a stored request re-spawn as background runs at startup (pre-WP5 runs stay sealed); notices survive restart; delegate factory honors Request.Background with a sync fallback when the host lacks background support. Refs: Agent-Native#29, Agent-Squad#33, N2 plan WP5	2026-10-07 14:23:39 +00:00