Repository navigation
attune-harness 1.0.0rc1
Pre-release-
Prepare
1.0.0rc1package metadata and capture the candidate saved-state
fixture from a clean, installed local writer wheel. The fixture retains exact
record bytes and reader/replay/refusal cases; publication and the observed
candidate period are separate release steps. -
Pin each CLI argument's accepted choices and default in the 1.0 surface
fixture, including the working-directory default forspec intake --project.
Reconcile current-main signed-plugin and Voyage qualification claims with
their bounded platform and recorded-response evidence. -
Read a single memory configuration with both native recall roots and saved
storage:memory recallsets aside the saved section whilememory saved
continues to use it. -
Executable plugins can read selected installed wheel metadata through the
bounded import closure, supporting offline Voyage SDK and compiled dependency
imports without exposing site-packages or undeclared distribution metadata. -
Preserve the host-owned
dispatchingstage when a provider adapter reports
an interrupted subprocess, refusing automatic replay without exposing child diagnostics. -
Legacy Codex build timeouts can retain an explicit operator stop observation
for one bounded retry, without inventing historical process evidence. -
Add a signed Python plugin
runbinding with explicit grants, a declared
import closure, bounded subprocesses, and unresolved receipts when host
evidence changes. MCP and review wrap results as untrusted data.
Network plugins await host-owned provider journals; platform qualification
claims remain unchanged. -
Add the empty active deprecation register and opt-in envelope notice helper
for the stable compatibility promise. Pin actual retrieval MCP listings by
protocol version and the A2A local profile. No current form is deprecated;
the candidate saved-state freeze remains pending executable-plugin completion. -
End the legacy memory adapter transition (D28):
reader: adapteris now
refused with "Memory reader must be 'native'". Native formats remain frozen
as read; offline worker and native read envelopes replace adapter fixtures. -
Preserve optional deferred opportunity-review checkpoints on saved tasks,
with visible resume guidance andmemory saved list --pending-review.
Task completion does not clear a pending review. -
Add explicit
memory savedsave, inspect, search, revise, withdraw, complete
and reindex commands. Local POSIX files retain history and retry identities;
optional Redis indexing reports pending work without losing durable saves. -
Codex build proposals isolate user configuration and plugin integrations.
Stopped native timeouts retain process evidence and support one explicit,
checkpoint-bound retry while preserving the failed attempt. -
Raise the complete-checkout snapshot limit to 2,048 entries for build and
repair, consistently across capture and validation. Files, directories and
Git metadata remain checked; the 16 MiB tree and 64 KiB edit limits remain. -
Preserve attributed design feedback and a current discussion question in task
briefings, with consistent section labels and accessible definition controls.
Keep presentation revision, task inspection time and report time distinct;
historical/stale/completed tasks withhold the retained question. -
Add a Saved Tasks entrance through explicit
status --include-taskinputs.
Human briefings separate context, goal, desired end state and current focus;
optional attributed summaries stay bound to their continuation revision.
Local reply controls prepare text for an assistant without sending, approving
or executing it. Default JSON and saved task authority remain unchanged. -
Add opt-in
status --format markdown|htmlreturn-to-work views for saved
feature-work tasks.--continuation FILEadds an explicitly supplied stopping
point, attributed external progress and a comparison with retained request scope.
Current task guidance takes precedence; supporting evidence stays inspectable.
Default JSON output and task execution semantics remain unchanged. -
Add the workspace MCP profile, Spec intake/presentation CLI, and local Claude
and Codex plugin candidates. Lifecycle gates remain a separate prerequisite;
the Spec skill stops at that boundary. No marketplace release is claimed.