SkillWeave v1.5.10

SkillWeave v1.5.10 delivers the native execution surfaces built since v1.5.9: an identity-verified lifecycle store and durable execution stream, native methodology, write-scope, skill, verification, cancel and budget enforcement through the authoritative run path, the route-lock and MCP control/authority surfaces, and a release-publishing path that carries one honest identity to both forges. Every entry below is derived from the shipped commits and cites them.

Features

• Native Lifecycle Store: unified native lifecycle state with transactional run persistence, CAS kill and legal lane transitions; durable completion and cancellation intent reconciled on resume, with atomic lifecycle/event co-commit (07f9c0d, d3fdca0, 8ef1d28, b219c84).
• Execution Identity Boundary: host-owned execution identity with a sealed authority store and live one-shot capabilities for protected writes (aa60644, 71db98e).
• Execution Write-Scope: WorkContract execution write-scope enforced with real isolation at the launch boundary (5726d4e).
• Native Methodology Execution: methodology execution through the authoritative run path (2baff64).
• Durable Stream Evidence: disk-backed stream evidence with immutable facts and cursor replay (cb7c1b1, d95b3c2).
• Cancel/Resume Lifecycle: native identity-verified process lifecycle for cancel and resume, with durable cancellation reconciliation before the signal boundary (05e5470, 3122520).
• Artifact Semantics Verification: mandatory verification of artifact-specific semantics before a successful methodology pass (b03832f, d2987e0).
• Native Execution Envelope: three-field native execution envelope with no silent Ralph substitution, failing closed at the executor/generator/receipt seams (74ffd37).
• Bounded Adaptive Scheduling: bounded adaptive scheduling with a role-based model policy (802e6ca).
• Scoped Headless Adapter: scoped headless OpenClaude adapter that composes typed headless events into execute and guards the launch seam (11df945, 00b5e3a).
• Bounded Repair: classified bounded repair bound to the methodology controller, failing closed on provider quota and unclassifiable failures (e235924, 04f0df6).
• Adapter Facade: common adapter facade with an interchangeable search/tool registry, a format-reader API and the adapter guide (a77bdc5, ea9d24e).
• MCP Agents & Mailbox: durable harness-neutral handoff and agent mailbox, with the full tool surface served over both transports and atomic, idempotent mailbox posts under races (a7b6f5c, 700e671).
• MCP Control Surface: control surface delegating to the shared run service, structured refusals, first-run store creation and a scoped Streamable HTTP serving path (559ac08, 912287d).
• Installed CLI/MCP Entries: installed CLI and MCP entries wired to the durable native streaming collector, with entry dispatch and publish command semantics repaired (02db9fa).
• Budget Reservation Enforcement: QuotaRefused, allowed_routes, nested-scope budget and task aggregate, with the reservation guard wired into async/restart and installed ingress paths (6a863b4, 011e0db).
• Route-Lock: route-decision-v1 contract payload, pinned-policy verification, egress confinement composed with worker/scope wrap, and route-proof enforcement through the CLI, MCP and reservation entrypoints (ff72f05, f36a3ea, 6ae7b87).
• MCP Authority: MCP authority made server-owned in the middleware, every tool gated, the start scope bound and the SDK envelope consumed (548a15e, 0900a20, fc891ae).
• SDK Contract CI: Core/SDK contracts qualified against the installed wheel, with the gate pinned to the SDK head that ships _authority (66cab70, 3b73d86).
• Version & Support Truth: the versioned execution/support matrix published, with version, search and setup claims computed from evidence (c2e4679, 5484a7a, 9aa6c02).

Fixes

• Council Search: DuckDuckGo Lite parser, error states, fallback gating and formatted context repaired against cold-review findings (baf6d10, 648429e).
• Council Launcher: Perplexity MCP search lifecycle and result normalization repaired, forwarded credentials redacted from server-originated text, and a refused launcher refused at the consumer boundary (5ded7c1, 43db148, dff8e34).
• Credential Resolver: credential resolver hermetic isolation fixed with guard tests (c61e9a7).

Infrastructure

• Publish Identity: skill manifests point at the authorized SkillWeave-AI publish identity (416f167).
• Publish Manifest: publish manifest owner/repo and identity aliases resolved (9ac4ea5).
• Capacium Action Pin: Capacium publish action pinned to commit SHA 7a09969, audited v1 (e1ae85c).
• Publish-Manifest Contract Test: contract test added for the Capacium target state (f2ae58c).
• Install-Free Mirror: mirror resolves its destination from .ops.yaml without requiring an install (3c73871).
• Mirror Configuration: mirrors bound to SkillWeave-AI, with pinned ops-engine v3.4.2 provisioned before dependency checks (7aabc1b, 9b245c8).
• Reproducible Provisioning: reproducible Core provisioning with a base/optional boundary and an entrypoint smoke (47fbc5d).
• License Metadata: Apache license metadata qualified for PEP 639 (c095001).

SkillWeave v1.5.9

SkillWeave v1.5.9 delivers the Contract Authority framework, cross-repo contract CI, work contracts, methodology registry, bounded repair, assay methodology, and infrastructure fixes for the release pipeline.

Contract Authority

• Cross-Repo Contract CI: Fail-closed contract validation against the published SDK 0.2.0 schema set, with a drift counterproof job that proves one-byte schema drift turns the gate red.
• Core → SDK 0.2.0 Migration: Core now validates against the published skillweave-sdk contract set instead of inline schemas.
• Council AttributedResponse: copy(), asdict() and pickle now survive round-trips without losing attribution metadata.
• Skill Inventory Fixes: Resolved 6 inventory test failures caused by the contract migration.

Features

• Work Contracts: Discriminated SubjectRef variants (repository, content, configuration, deployment, incident) with WorkContract binding authority, write scope, irreversible actions, verification, rollback, and budget. Exact-brief contract via SHA-256 digest.
• Methodology Registry: Versioned registry for REX, Ralph, Gauntlet, and Assay methodologies with compatibility matrix. Legacy execution_model values migrate deterministically.
• Assay Methodology: Append-only state machine (PIN → HYPOTHESIS → PROBE → MEASURE → CLASSIFY → REMEDIATE → PASS/HOLD) with conservative, moderate, and unicorn autonomy policies.
• Bounded Preflight Repair: Versioned PreflightFailure contract with grounded repair engine. Repairs are 1:1 substitutions preserving write scope; repeated fingerprints, target drift, and authority expansion trigger holds.
• Blueprint Data Contracts: PRDs crossing storage, process, adapter, telemetry or public-API boundaries now require exact versioned data contracts instead of prose.
• Discovery Trace Graph: Digest-bound trace from discovery Markdown to epics/tasks/deferrals. Silent loss of mandatory problems, missing links, and post-grounding digest drift all fail closed.
• Grounding Manifest: Bounded, deterministic, read-only scanner producing digest-bearing manifests with language detection, symbol citations, and gap tracking.
• Blueprint Ticket Handshake: Authority-aware planning ticket handshake with four terminal states (linked, created, not_applicable, needs_authority) and duplicate-title prevention.
• CMS Operate Profile: Provider-neutral CMS Ops profile with Blueprint-always contracts, generic roles, and conditional skip-reasons.
• Edition Contracts: Consent boundary export and Community/Pro contract separation.
• Telemetry: Privacy-safe local empirical telemetry with shape-based path detection (not vendor-prefix denylist), disabled and local-only by default.
• Repository-Scoped Lane Contracts: RepositoryTarget binding for lane contracts.
• Durable Async Run Lifecycle: start/inspect/kill with durable state.
• Evidence-Backed Lane Outcome Resolution: Lane outcomes resolved from evidence, not stdout.

Infrastructure

• Release Pipeline: Flattened release_title_policy fields to .version.yaml root level for ops-engine parser compatibility. Updated TITLE_GATE_PY regex to match root-level keys.

SkillWeave v1.5.8

SkillWeave v1.5.8 completes the Generic Lifecycle execution capability. It introduces a modular routing adapter, dedicated worker messaging channels, deterministic blocker slicing, and massive vertical and horizontal testing expansions for both Software Delivery and Research Synthesis pipelines.

Highlights

• Generic Harness Adapter: Replaced hardcoded OpenClaude references with a HarnessAdapter interface and an agnostic AdapterRequest contract, paving the way for multi-harness routing (e.g. Faigate / OmniRoute).
• Worker Direct Messaging: Agents now emit structured DirectMessage records via a dedicated file-based JSONL channel (SW_MSG_CHANNEL), decoupling worker signals from fragile stdout log scraping.
• S3-Gate Validation Slicing: Blocker parsing now fails closed if (lane_id, domain) matches multiple records identically, preventing runaway spawn loops when blockers are ambiguous.
• Contract Reality Check: Delivered a 20-criterion alignment map mapping the PRD requirements to their implementations and testing coverage.
• Extensive Validation Profiles: Added exhaustive Golden Scenarios for the generic lifecycle, fully modeled research and software delivery profiles, and breadth integration tests.

SkillWeave v1.5.7

SkillWeave v1.5.7 introduces the fully integrated Lifecycle Closeout system, bringing robust transactionality, tamper-evident telemetry, and durable retrospective persistence to the pipeline.

Highlights

• Transactional Closeout: Workspaces are now removed via an idempotent, fsynced journal. Duplicate mutations are prevented, and crashes during the mutation window are handled gracefully.
• Tamper-Evident Telemetry: Privacy validations now cover both keys and values, proactively redacting secrets and absolute paths from the telemetry stream.
• Durable Retrospectives: Retrospective synchronization is now fully atomic (mkstemp -> os.replace), ensuring no torn reads or data loss during sync.
• Strict Evidence Boundaries: Missing or incomplete evidence now strictly forces a hold instead of silently closing out.
• Remediation Slicing: Introduced a new byteplus-deepseek-pro escalation pathway to slice multi-domain failures into disjoint micro-lanes and repair blocking gates autonomously.

SkillWeave Changelog

SkillWeave v1.5.6

SkillWeave introduces a universal CLI entry facade and a comprehensive operator onboarding ecosystem. These additions provide a unified interface to start, continue, inspect, or onboard, while securely persisting operator profiles and state contexts.

Highlights

• Universal CLI Router: skillweave start, continue, inspect, and onboard subcommands are now fully routed and validated through the shared EntryService contract.
• Onboarding Profile Generation: Captures and persists operator intent, role, and autonomy boundaries in durable, encrypted YAML profiles.
• Strict Integration Testing: New harnesses test end-to-end integration across entry facades, adapters, profile verification, and CLI router parity.
• Product-Neutral Release Gating: Forgejo release workflows are now entirely decoupled from hardcoded product titles; release_title_policy is loaded dynamically from .version.yaml.

SkillWeave v1.5.5

SkillWeave can now prepare multi-repository workspaces and operator dispatches
without hiding the ownership, lifecycle, or exact acceptance criteria behind
them. The release makes those boundaries inspectable before an ops worker is
allowed to write, and rejects incomplete or ambiguous contracts instead of
guessing.

Highlights

• Workspace manifests are validated strictly, provisioned from exact base
  revisions, and released or cleaned up only with explicit ownership receipts.
  Foreign, dirty, or currently active worktrees are refused rather than removed.
• A read-only multi-repository inventory exposes worktree state before cleanup,
  including the reason an entry cannot be touched.
• Operator dispatches now have a preview and observer surface before ops starts,
  criterion-aware events, and consistent heartbeat and terminal semantics for
  both inline and fan-out execution.
• Dispatch contracts require every requested acceptance criterion exactly once.
  Missing, duplicate, empty, or out-of-range criterion groups fail closed, while
  valid non-empty regrouping remains supported.

Reliability

• Workspace lifecycle, cleanup receipts, observer previews, profile effects,
  event streams, and exact-once dispatch criteria are covered by unit,
  integration, contract, and release-gate tests.
• The reviewed release candidate passed the complete 1.5.5 product and planning
  gates before entering the release branch.

Upgrade

pip install --upgrade skillweave. Existing profiles remain compatible; use the
new preview and workspace inventory surfaces to inspect generated work before an
operator dispatch begins.

Full changelog: CHANGELOG.md · Diff: v1.5.4...v1.5.5

SkillWeave v1.5.4

The path that publishes a tagged release to the Capacium Exchange was wired for
Trusted Publishing but never asked for a token, so every tag since v1.3.12
reached the CLI with an empty credential and refused. This release turns that
path on. No runtime or skill code changes.

Fixed

• The Capacium publication step now requests a short-lived publish token through
  OIDC (id-token: write plus use_oidc: true) instead of arriving with an
  empty CAPACIUM_API_TOKEN. No long-lived Capacium secret is stored in the
  repository; the Exchange derives the publisher owner from the OIDC claims and
  issues a token scoped to exactly that owner and repository.

Changed

• The version-sync helper fetched by the release gate is pinned to ops-engine
  v3.4.2, the same release the release workflow installs as its engine, so the
  repository names one ops-engine version rather than two. The helper is
  byte-identical across v3.0.0, v3.4.0 and v3.4.2, so the gate's verdict is
  unchanged.
• The check-manifest diagnostic output is English, matching the rest of the
  repository's tracked files. Only strings moved; its exit-code contract is
  unchanged.

Upgrade

pip install --upgrade skillweave. src/ and skills/ are identical to 1.5.3,
so nothing you call changes.

Full changelog: CHANGELOG.md · Diff: v1.5.3...v1.5.4

SkillWeave v1.5.3

Every release from 1.3.12 to 1.5.2 was tagged on both forges while only Forgejo
carried a release object, so the public "latest release" stood at 1.3.11 for nine
days, and the notes that did exist were raw commit dumps. This release replaces
the machinery that produced that and repairs the history it damaged. No runtime
or skill code changes.

Highlights

• A release is published to every declared forge, or the run goes red. There is no
  longer a path where one forge succeeds quietly and the other is skipped.
• The release body is the changelog entry for the tag. A version with no entry is
  refused, instead of falling back to commit subjects.
• The changelog carries all 41 released versions again, each with a date.

Added

• .ops.yaml declares the release destinations and this repository's tracker
  prefixes. No forge repository, API host or CI variable survives as a literal in
  the workflow layer.
• Three gates that run before any release object exists on either forge: the
  release title, the presence of a changelog entry, and whether that entry still
  addresses an internal tracker rather than a reader.
• The canonical tag is pushed onto the mirror before publication, and both tags
  are peeled and compared after it, so the release API cannot invent a tag at the
  mirror's default-branch head.

Changed

• Publication is handed to the ops-engine release handler, pinned to 3.4.2 and
  version-gated after install. The workflow no longer reimplements it.
• The mirror destination is read from repository variables with a double match and
  an existence and permission preflight, instead of being assumed reachable.

Fixed

• Release notes are no longer a commit-log dump assembled with printf, which
  left every line separator as a literal backslash-n: the 1.5.2 body was 4356
  characters rendering as four lines.
• The release history deleted at the 1.4.0 bump is restored — 597 lines, covering
  everything at or below 1.3.13.
• Six tagged versions that never carried a changelog entry have one.
• pytest-asyncio is declared. Without it a clean environment runs the async
  suites as unknown marks and 32 tests fail without the code being at fault.

Upgrade

pip install --upgrade skillweave. src/ and skills/ are identical to 1.5.2,
so nothing you call changes. Installing from source also needs the sibling SDK
checkout installed first; the dependency on it has never resolved from an index.

Full changelog: CHANGELOG.md · Diff: v1.5.2...v1.5.3

SkillWeave v1.5.2

SkillWeave v1.5.2 — a substrate that survives upgrades, and a mirror that proves its destination

SkillWeave keeps two kinds of state that used to share a directory: what a team authors and
tunes, and what a run generates. This release separates them, so upgrading the package no
longer overwrites a tuned catalogue and generated state never ships and never tracks.
Alongside it, the mirror to the public GitHub remote proves its destination exists before it
pushes anything, instead of discovering the problem halfway through.

Highlights

• A tuned catalogue under skillweave.config/ survives package upgrades; generated output
  under .skillweave/ is git-excluded and stays out of the repository.
• The mirror refuses an unproven destination, so a misconfigured remote is a failed gate
  rather than a silent no-op.
• A packaging-only version bump now touches two files instead of sixteen.

Added

• Three-tier substrate model — package defaults ship under skillweave/assets/, durable
  input lives under skillweave.config/, and generated output under .skillweave/, which is
  git-excluded.
• Generic substrate contract — every area declares direction (input or output),
  durability (authored or generated, with ephemeral as a first-class value) and
  disclosure (public or private). A backing-store seam resolves an area's store from that
  declaration rather than from the presence of a .git directory, so a durable area in a
  non-git workspace syncs through the configured organisation planning repository. Where no
  store is reachable, the area is reported at risk instead of silently accepted.

Changed

• One mirror workflow — the visibility gate, the release-tag version gate and the mirror
  job are a single workflow ordered by needs, with a destination guard that proves the
  GitHub destination is reachable before any push rather than failing inside one.
• Decoupled member pins — the bundle and the runtime carry the train version, while the
  capabilities[] member pins and the thirteen skill capability files are informational and
  may lag the bundle together. A bundle bump can be packaging alone, so a plain bump moves
  only pyproject.toml and the root capability.yaml and leaves the pins where they are. A
  pin never diverges from its own member file; that consistency is owned by
  scripts/check-manifest.py, not by the release gate.
• Onboarding teaches the substrate rule — it writes the anchored /.skillweave/ gitignore
  exclusion, records the private planning-repository answer, and refuses to leave substrate
  content tracked when the origin remote is public.

Fixed

• Hermetic test suite — tests that depended on untracked local state (sibling checkouts,
  the git-excluded .skillweave/ tree) now skip with an explicit reason when that state is
  absent, so a fresh clone reproduces a green suite.

Upgrade

pip install --upgrade skillweave. Existing .skillweave/ trees keep working. To move a
tuned catalogue out of the generated tier, relocate the authored files to
skillweave.config/: the resolver reads that tier first and package defaults fill the gaps.

Full changelog: CHANGELOG.md · Diff: v1.5.0...v1.5.2

SkillWeave v1.5.0

SkillWeave v1.5.0 — execution that survives a crash

Long agent runs fail in the middle, and until now recovering one meant parsing transcripts.
This release reconstructs a run's execution graph from persistent context instead, bounds
token budgets per profile, and escalates irreversible decisions to an operator before any
state is mutated rather than after.

Highlights

• A crashed orphan, worker or coordinator is recovered from persistent context, not from
  transcript parsing.
• Token budgets are declared per profile and enforced, so a crash loop cannot double-charge.
• Irreversible choices escalate before the mutation, not after it.

Added

• Crash recovery — orphan, worker and coordinator recovery reconstruct execution DAGs from
  persistent context rather than brittle transcript parsing.
• Context limits and checkpointing — configurable token profiles (for example 120k
  no_new_task, 150k checkpoint, 170k stop) bound execution budgets.
• Operator agent escalation — operator_agent carries strict deterministic decision
  scopes; an irreversible choice escalates before state is mutated.
• Persistent policy — idempotent compensation, backoff and retry budgets, so a crash loop
  does not double-charge tokens.
• Remote workspace sandbox — distributed execution honours the skillweave-workspace
  contract without leaking orchestration state.
• Soak and endurance testing — multi-hour degradation limits, and a DoubleStartGuard
  against a second process starting over a live run.

Upgrade

pip install --upgrade skillweave. Token profiles ship with defaults; set them explicitly if
your runs are long enough to approach a context ceiling.

Full changelog: CHANGELOG.md · Diff: v1.4.0...v1.5.0