@xiaozhiclaw/qlogicagent-core 0.6.2 → 0.6.3

package/README.md

@@ -118,10 +118,16 @@ text or a Host/transport model projection; the full structured receipt remains i
 
 `qlogic_update_plan` accepts `CorePlanInput`:
 
-- `create`: `steps` and `issues`, with stable step/issue IDs.
-- `read`: the Host-issued `planId`, including after a worker/process restart.
+- `create`: `steps` and `issues`, with stable step/issue IDs; optional `notes`
+  preserve decisions, constraints and blockers with evidence references.
+- `read`: the Host-issued `planId`, including after a worker/process restart;
+  optional `stepIds`, `cursor` and `limit` allow scoped, paged retrieval.
 - `update`: `planId`, last `expectedRevision`, and the complete replacement
   `steps` and `issues`. Empty `issues` explicitly clears resolved issues.
+- `patch`: `planId`, last `expectedRevision`, and explicit upsert/remove lists
+  for steps, issues and notes. Omitted lists leave existing records unchanged.
+  The Host may call the pure `applyCorePlanPatch` helper on its locked snapshot
+  before atomically saving the next revision and invocation receipt.
 
 Steps contain `description`, `status` (`pending`, `in_progress`, `completed`,
 `blocked`, `cancelled`), optional `dependsOn` step IDs and `evidenceRefs`.
@@ -134,6 +140,9 @@ an error with the current revision; the Agent reads and reconciles before retryi
 The Host must deduplicate writes by the original invocation; Core neither owns
 a plan database nor retries unknown effects. A progress status or evidence
 reference proposed by the model does not prove business completion.
+Plan notes remain Host-owned durable facts; context compression cannot replace
+their storage. Project selected notes and resource references through
+`runtime.prepareContext`, and provide authorized reads of the complete records.
 
 `qlogic_request_confirmation` accepts `CoreConfirmationInput`: a Host-issued
 immutable `operationRef`, human-readable `summary`, explicit `targets`
@@ -283,6 +292,12 @@ same safe checkpoint without new input, resetting no budget, deadline or receipt
 Products must atomically reopen their dispatch projection for this exact transition.
 
 Original completed-model replay uses the immutable stored messages and digest.
+Provider `length` / `max_tokens` finishes without tool calls persist the partial
+answer and an output-capacity continuation checkpoint, then request the remaining
+work against the original objective. This is a new recorded model request, not a
+retry of unknown inference. `pendingOutputText` survives process restart and joins
+the final answer. Caller-supplied budgets and pause/cancel controls still apply;
+the default has no task-wide round, request-count or duration cap.
 Current product retrieval is refreshed for subsequent new rounds only. A digest
 mismatch is reconciliation, never permission to pay for a replacement inference.
 An explicit amendment consumes the previous final no-tool response once before