Skip to content

Releases: stef-k/CogniRelay

CogniRelay v1.4.8

26 Apr 17:23
fe998b9

Choose a tag to compare

CogniRelay v1.4.8 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.8 is a focused packaging compatibility patch for the shipped
last-mile adapter skill. It fixes the cognirelay-continuity-authoring skill
from v1.4.7 so common skill loaders can accept it directly from
agent-assets/.

Highlights

  • Added YAML frontmatter to the shipped cognirelay-continuity-authoring
    skill.
  • Preserved the existing skill body and responsibility split: CogniRelay is the
    substrate, the running agent authors semantic continuity fields, and hooks or
    adapters do not infer semantic meaning.
  • Added a flexible regression test that validates the frontmatter block without
    overfitting line positions.

Compatibility Notes

  • Runtime version is now 1.4.8.
  • Existing HTTP, MCP, graph, schedule, continuity, UI, and adapter-hook behavior
    is unchanged.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools agent-assets
./.venv/bin/python -m unittest tests/test_agent_assets_289.py -v
./.venv/bin/python -m unittest discover -s tests -v

CogniRelay v1.4.7

26 Apr 16:49
c7de85c

Choose a tag to compare

CogniRelay v1.4.7 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.7 ships the last-mile adapter kit for agent-authored
continuity integration. It is a distribution and integration-quality release:
the runtime API remains stable except for the added help topic, while operators
now get copyable assets for safe agent startup/retrieval and continuity saves.

Highlights

  • Added agent-assets/ with a copyable cognirelay-continuity-authoring
    skill and real stdlib-only Python hooks for retrieval and continuity save
    flows.
  • The retrieval hook performs read-only startup orientation and optional
    bounded context retrieval, surfacing graph and schedule orientation without
    mutating continuity, tasks, or schedule items.
  • The continuity save hook supports facts, template, dry-run, write,
    readback, and doctor modes with deterministic JSON output, placeholder
    rejection, local-only dry-run diffs, and readback verification.
  • Added the runtime help topic last-mile-adapter, available over HTTP and MCP
    through system.topic_help.
  • Updated agent onboarding and the documentation index so cold-start agents can
    discover the shipped adapter kit and the responsibility split.

Compatibility Notes

  • Runtime version is now 1.4.7.
  • Existing HTTP, MCP, graph, schedule, continuity, and UI behavior is unchanged
    except for the added help topic and documentation/assets.
  • The adapter hooks are shipped as copyable assets. They do not become server
    runtime behavior and do not infer semantic continuity content.
  • Scheduling guidance remains bounded: agents may create one-shot reminders
    explicitly when needed, but the adapter hooks do not create, acknowledge,
    retire, execute, or mutate schedule items.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools agent-assets
./.venv/bin/python -m unittest tests/test_agent_assets_289.py -v
./.venv/bin/python -m unittest tests/test_help_214_slice1.py tests/test_help_243_runtime_onboarding_limits.py tests/test_mcp_216_slice3_help.py -v
./.venv/bin/python -m unittest discover -s tests -v

CogniRelay v1.4.6

26 Apr 09:19
ffd8337

Choose a tag to compare

CogniRelay v1.4.6 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.6 is a focused MCP startup compatibility patch for standard
request metadata. It fixes clients that send MCP-reserved params._meta during
startup or request-method calls.

Highlights

  • tools/list now accepts object-valued params._meta and returns the tool
    catalog instead of failing with unexpected tools/list param.
  • initialize, tools/list, tools/call, and runtime MCP help/reference
    request methods now accept and ignore object-valued params._meta.
  • Actual tool arguments remain strict application payloads. _meta inside
    tool arguments is not treated as request metadata.
  • The regression suite now replays the previously failing startup path:
    initialize with clientInfo.title, followed by tools/list with
    params._meta.

Compatibility Notes

  • Supported MCP protocol versions remain 2025-06-18 and 2025-11-25.
  • clientInfo implementation metadata compatibility from v1.4.5 is preserved.
  • Non-object params._meta fails deterministically with -32602 Invalid params.
  • Unknown non-metadata request params still fail deterministically.
  • No MCP tool schema, HTTP route, schedule, graph, continuity, or UI response
    shape changed.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -v

CogniRelay v1.4.5

26 Apr 08:57
87f6c19

Choose a tag to compare

CogniRelay v1.4.5 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.5 is a focused MCP startup compatibility patch. It fixes
standards-compatible clients whose initialize request includes optional
clientInfo implementation metadata.

Highlights

  • initialize now accepts standard MCP implementation metadata fields under
    clientInfo: title, description, websiteUrl, and icons.
  • The exact observed Codex startup payload with clientInfo.title now succeeds.
  • The compatibility fix is not Codex-specific; it applies to the supported MCP
    protocol versions 2025-06-18 and 2025-11-25.
  • Immediate tools/list after successful initialize remains supported.

Compatibility Notes

  • Top-level initialize.params remains strict: protocolVersion,
    capabilities, and clientInfo.
  • clientInfo.name remains required when clientInfo is present.
  • Unknown clientInfo fields still fail deterministically with
    -32602 Invalid params.
  • No MCP tool schema, HTTP route, schedule, graph, continuity, or UI response
    shape changed.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -v

CogniRelay v1.4.4

26 Apr 08:33
5e6d4c0

Choose a tag to compare

CogniRelay v1.4.4 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.4 is a focused patch release for Codex MCP startup
compatibility after the v1.4.3 protocol-version bridge.

Highlights

  • MCP sessions are now ready for request methods immediately after a successful
    initialize.
  • Codex clients that call tools/list right after initialize, without first
    sending notifications/initialized, can complete startup.
  • notifications/initialized remains accepted after initialize, so clients
    that send the notification keep working.

Compatibility Notes

  • MCP protocol-version compatibility from v1.4.3 is preserved:
    initialize accepts 2025-06-18 and 2025-11-25.
  • Unsupported or malformed initialize requests still do not mark a session
    ready.
  • Request methods before any successful initialize still fail with the
    existing not-initialized behavior.
  • No MCP tool schema, HTTP route, schedule, graph, continuity, or UI response
    shape changed.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -v

CogniRelay v1.4.3

26 Apr 07:39
e26ae68

Choose a tag to compare

CogniRelay v1.4.3 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.3 is a focused patch release for MCP startup compatibility
with currently deployed Codex clients.

Highlights

  • MCP initialize now accepts both protocol versions 2025-06-18 and
    2025-11-25.
  • Successful MCP initialization echoes the accepted client-requested protocol
    version, so older compatible clients can complete startup.
  • Unknown protocol versions still fail deterministically with
    Unsupported protocol version and a supported-version list.
  • /.well-known/mcp.json, discovery metadata, and MCP docs now advertise both
    supported initialize protocol versions while keeping 2025-11-25 as the
    preferred/latest version.

Compatibility Notes

  • No MCP tool, JSON-RPC method, HTTP route, schedule, graph, continuity, or UI
    response shape changed outside MCP initialize protocol negotiation metadata.
  • The bounded MCP posture remains intact: initialize,
    notifications/initialized, ping, tools/list, tools/call, and the
    existing post-bootstrap help/reference request methods are unchanged.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -v

v1.4.2

26 Apr 06:58
d0166c9

Choose a tag to compare

CogniRelay v1.4.2 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.2 is a focused patch release for two post-v1.4.1 fixes:
durable audit redaction for context retrieval and shipped-doc rendering in the
operator UI documentation browser.

Highlights

  • context.retrieve audit events no longer persist raw task text or task-text
    prefixes in durable logs/api_audit.jsonl rows.
  • Context retrieval audit rows now record deterministic task_hash and
    task_length_bytes metadata while preserving result counts and loaded
    continuity selectors.
  • /ui/docs now reads the allowlisted documentation shipped with the running
    application checkout instead of looking for those files in the configured
    data repository.

Compatibility Notes

  • No POST /v1/context/retrieve request or response shape changed.
  • Retrieval ranking, continuity behavior, graph context, schedule context, MCP
    protocol behavior, and operator UI routes are unchanged.
  • The audit detail shape for context_retrieve changed intentionally:
    detail.task was removed and replaced by safe hash/length metadata.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -v

v1.4.1

25 Apr 21:26
5bd5033

Choose a tag to compare

CogniRelay v1.4.1 Release Notes

Release date: 2026-04-26

CogniRelay v1.4.1 is a focused patch release for the agent onboarding and
runtime help surfaces introduced in v1.4.0.

Highlights

  • Clarified the thread-scoped context.retrieve example so agents use
    subject_kind="thread" plus subject_id for primary retrieval scoping.
  • Clarified that top-level thread_id is valid for task and schedule lookup
    examples, but not for primary context.retrieve scoping.
  • Added explicit due schedule inspection examples for both thread_id filters
    and subject_kind=thread plus subject_id filters.
  • Kept MCP system.tool_usage on its existing compact response shape while
    improving the summary guidance.

Compatibility Notes

  • No runtime API behavior changed.
  • No MCP protocol shape changed.
  • No schedule, graph, continuity, UI, or route semantics changed.
  • The GET /v1/capabilities version field remains the capability schema
    version ("1").

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -v

v1.4.0

25 Apr 20:12
d76c482

Choose a tag to compare

CogniRelay v1.4.0 Release Notes

Release date: 2026-04-25

CogniRelay v1.4.0 completes the post-#218/#236 roadmap. The release turns the
post-hardening work into shipped agent-facing runtime surfaces, stronger
operator inspection tools, and coherent docs/help/discovery metadata.

Highlights

  • Runtime onboarding and help: agents can discover onboarding sections,
    startup guidance, route identifiers, validation limits, and help topics
    through bounded HTTP and MCP help surfaces.
  • Agent-facing derived graph context: context.retrieve now includes
    bounded bundle.graph_context by default, and startup continuity.read
    includes a compact top-level graph_summary after the base read succeeds.
  • One-shot schedules and reminders: the new SQLite-backed schedule store
    supports reminders and task nudges through HTTP and MCP, with UTC-only
    timestamps, pull-based due evaluation, and scoped schedule_context in
    startup and context orientation responses.
  • Expanded read-only operator UI: the local UI now includes graph, task,
    context retrieval, documentation, and schedule inspection pages, in addition
    to the continuity-oriented surfaces.
  • Coherent docs and discovery: payload reference, API docs, MCP docs,
    onboarding, runtime help, discovery descriptors, capabilities, and the UI docs
    browser now describe the same shipped behavior.

Compatibility Notes

  • The GET /v1/capabilities version field remains the capability schema
    version ("1"). New feature keys were added without changing the schema.
  • The durable continuity capsule write cap remains 20 KB. Graph and schedule
    information are derived response adjuncts, not stored capsule data.
  • Schedule reminders are one-shot only in this release. Recurrence, background
    scheduler loops, SSE/push delivery, arbitrary command execution, webhooks, and
    automatic task/continuity mutation remain out of scope.
  • Non-startup continuity.read remains graph-free by default. Startup reads
    receive graph_summary; context retrieval receives bundle.graph_context.

Verification

Release preparation should pass:

git diff --check
./.venv/bin/python -m ruff check app tests tools
./.venv/bin/python -m unittest discover -s tests -v

v1.3.1

17 Apr 06:35
18aa142

Choose a tag to compare

Fixed

  • MCP HTTP initialize requests now accept standard JSON-RPC payloads in the request body instead of failing with a 422 due to an incorrect payload query parameter binding.
  • Strengthened MCP regression coverage so the generated /v1/mcp HTTP contract requires a JSON request body and no longer advertises payload as a query parameter.

Validation

  • ./.venv/bin/python -m unittest tests.test_mcp_rpc -v
  • ./.venv/bin/python -m ruff check app/main.py tests/test_mcp_rpc.py
  • ./.venv/bin/python -m unittest discover -s tests -v