banana-claws: drift hardening + async contract enforcement (v0.1.4 → v0.1.5)

Article content

banana-claws shipped two tightly related reliability milestones this cycle.

1) Foundational-image drift hardening + provenance (v0.1.4)

What shipped:

• Fail-fast behavior for edit/variant intent when no baseline image resolves.
• Deterministic baseline resolution policy + provenance fields:
  • baseline_source_kind
  • baseline_resolution_policy
• Baseline rails defaults for attachment-driven edits (low variation + lock palette/composition).
• Provider metadata + drift diagnostics persisted in queue result records for auditability.

Receipts:

• PRs: https://github.com/ironystock/banana-claws/pull/10 ↗ (opens in a new tab) , https://github.com/ironystock/banana-claws/pull/11 ↗ (opens in a new tab)
• Commits: d237a9a (metadata persistence), 21fdc7d (drift hardening)
• Release: https://github.com/ironystock/banana-claws/releases/tag/v0.1.4 ↗ (opens in a new tab)

Why it matters:

This turns “drift” from hand-wavy model behavior into auditable workflow state.

2) Async queue contract enforcement (v0.1.5)

What shipped:

• Explicit async handoff path: queue_and_return.py (enqueue + immediate ack + background worker).
• Request completion helper: summarize_request.py.
• Worker telemetry fields:
  • handoff_mode
  • same_turn_drain_detected
• CI async contract test to enforce immediate-return behavior.

Receipts:

• PR: https://github.com/ironystock/banana-claws/pull/13 ↗ (opens in a new tab)
• Commit: 8d7bd40
• Release: https://github.com/ironystock/banana-claws/releases/tag/v0.1.5 ↗ (opens in a new tab)

Why it matters:

Operators get lower perceived latency and a verifiable contract that inference moved out of the foreground turn.

Cross-links

• Project page: /projects/banana-claws/
• Launch baseline: /posts/banana-claws-launch-queue-workflow-and-branding-foundation/