Release Notes - v0.11.0¶

Release Date: 2026-07-25

Overview¶

v0.11.0 connects Aha Studio to the ProductContext signal pipeline with a new OmniSignal provider, and rounds out release metadata support in the MCP server with a description field backed by Aha's Release.Theme.

Highlights¶

OmniSignal Aha Provider - A new omnisignal package implements omnisignal.Provider for Aha Ideas, normalizing votes, categories, score, and linked feature data into vendor-neutral enhancement_request signals
Release Description Field - update_release accepts a description parameter, and get_release/list_releases now return it, powered by aha-go v0.8.0's Release.Theme support

Installation¶

# Install AQL CLI
go install github.com/grokify/aha-studio/cmd/aha-studio@v0.11.0

# Install MCP Server
go install github.com/grokify/aha-studio/cmd/aha-mcp-server@v0.11.0

What's New¶

OmniSignal Aha provider¶

Aha Studio now ships an omnisignal package that registers an Aha provider with plexusone/omnisignal, converting Aha Ideas into vendor-neutral enhancement_request signals for the ProductContext signal pipeline:

import (
    "github.com/plexusone/omnisignal"
    _ "github.com/grokify/aha-studio/omnisignal" // Register Aha provider
)

provider, err := omnisignal.New("aha", omnisignal.Config{
    BaseURL: "https://company.aha.io",
    APIKey:  os.Getenv("AHA_API_KEY"),
})

The provider preserves vote counts, categories, and score as signal metadata, maps Aha workflow status to signal status (new/processing/archived/ignored), derives a severity heuristic from vote count, applies capability-ref mappings from idea categories, and attaches linked feature info (aha_feature_id, aha_feature_ref, aha_feature_name) when an idea is tied to a feature. Each signal is fingerprinted via signal.ComputeFingerprint for downstream deduplication.

This is the first phase of the OmniSignal adapter scoped in the Roadmap; feature and release signal types are not yet implemented.

Release description support¶

update_release now accepts a description parameter, and get_release/list_releases return a description field in their responses. This maps to Aha's Release.Theme field, exposed via aha-go v0.8.0's WithReleaseTheme option:

{
  "tool": "update_release",
  "arguments": {
    "reference_num": "PROD-R-1",
    "description": "Focused on onboarding and activation improvements"
  }
}

Dependency Updates¶

Upgraded github.com/grokify/aha-go to v0.8.0 (Release.Theme, DescriptionObject fix)
Upgraded github.com/plexusone/omnisignal to v0.2.0 (curated signals, consolidation)
Upgraded github.com/plexusone/signal-spec to v0.2.0 (metadata constants, fingerprinting)
Removed local development replace directives now that all three dependencies are published

Documentation¶

Added CLAUDE.md and docs/specs (ARCHITECTURE.md, PRD.md, TRD.md, PLAN.md, ROADMAP.md) documenting repo conventions and design
Updated README.md badge shields

Commits¶

Commit	Type	Description
`aa63f9b`	feat(omnisignal)	Add Aha provider for signal integration
`84a0024`	feat(mcp)	Add release description/theme support
`da3404d`	chore(deps)	Update aha-go, omnisignal, signal-spec
`412afc7`	docs	Add CLAUDE.md and project specs
`921d1a4`	docs	`README.md`: update shields

Full Changelog¶

See the CHANGELOG for complete version history.