Skip to content

chore: adopt scion-sdk 0.10.1 and finish the ecosystem rename - #38

Merged
Knucklessg1 merged 4 commits into
mainfrom
chore/scion-0101-rename
Nov 13, 2026
Merged

Knucklessg1 merged 4 commits into
mainfrom
chore/scion-0101-rename

Conversation

@Knucklessg1

Copy link
Copy Markdown
Member

What

Moves the connector to scion-sdk 0.10.1 (its scion-sdk pin (scion-sdk>=0.10.1,<1.0.0) to >=0.10.1,<0.11) and finishes the rename of the old ecosystem names (agent-utilities to meristem, epistemic-graph to medulla, agent-connector-sdk to scion-sdk, graph-os to arbora).

Why

The previous floor was uncapped or on an older line; a fresh install resolves scion-sdk 0.10.1, which removed the pre-layer module paths and the separate HTTP client factories, so the published release fails to import. Doing the rename in the same change means the connector is gated once.

Impact

Imports now use paths that exist in 0.10.1 (build_http_client(options, async_=...) and the relocated modules). No aliases or fallbacks remain. Ontology namespace IRIs and CHANGELOG history are untouched.

Verification

  • tests/test_scion_sdk_0_10_imports.py checks that every scion_sdk module and imported name resolves on the installed release.
  • Every import was also checked statically against the 0.10.1 wheel.
  • Full local gate before merge.

Row: none (adopt scion-sdk 0.10 import paths).

🤖 Generated with Claude Code

Knucklessg1 and others added 4 commits November 12, 2026 12:48
Moves this connector onto scion-sdk 0.10.1 (its scion-sdk pin (scion-sdk>=0.10.1,<1.0.0) to >=0.10.1,<0.11),
which removed the pre-layer module paths and collapsed the HTTP client
factories into build_http_client(options, async_=...). A fresh install of
the previous release resolved the newest SDK and failed to import, so the
imports are updated to the paths that exist in 0.10.1, the lock is
regenerated, and a test now asserts that every scion_sdk import (module and
name) resolves on the installed release.

The same change finishes the rename left in this repository:
agent-utilities is now meristem, epistemic-graph is medulla,
agent-connector-sdk is scion-sdk and graph-os is arbora, in code, docs,
config, tests and file names. Hard cutover, no aliases. CHANGELOG history is
left as written and ontology namespace IRIs are untouched.

Spec: none (adopt scion-sdk 0.10 import paths)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…up to core (scion-sdk 0.11)

The connector's ontology now lives under the connector module of the one
ontology base and every class declares a core parent through rdfs:subClassOf,
so the pack loads in the engine instead of being rejected as an orphan or as a
core conflict. The SDK floor moves to 0.11 and the lock is regenerated. Where
the shared connector standard reported more, the same change fixes it: committed
files the standard provides centrally are removed, and a missing tool-use
contract, link, location, role or agent prompt is added.

Impact: ontology IRIs of this connector change to the new base; consumers read
them from the served ontology resource.

Verification: the connector-standard gate from pipelines main passes on this
tree, and the repository test suite was run on a build worker.

Spec: none (ontology namespace move and class roll-up to core; no new requirement)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
# Conflicts:
#	microsoft_agent/ontology/microsoft.ttl
#	pyproject.toml
#	uv.lock
…up to core (scion-sdk 0.11)

The connector's ontology now lives under the connector module of the one
ontology base and every class declares a core parent through rdfs:subClassOf,
so the pack loads in the engine instead of being rejected as an orphan or as a
core conflict. The SDK floor moves to 0.11 and the lock is regenerated. Where
the shared connector standard reported more, the same change fixes it: committed
files the standard provides centrally are removed, and a missing tool-use
contract, link, location, role or agent prompt is added.

Impact: ontology IRIs of this connector change to the new base; consumers read
them from the served ontology resource.

Verification: the connector-standard gate from pipelines main passes on this
tree, and the repository test suite was run on a build worker.

Spec: none (ontology namespace move and class roll-up to core; no new requirement)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Knucklessg1
Knucklessg1 merged commit 577befa into main Nov 13, 2026
16 checks passed
@Knucklessg1

Copy link
Copy Markdown
Member Author

Pre-merge test run: PASSED

What this is: the full test and lint suite of this repository, run before merge on the tested tree below, because the hosted checks are not the gate for this change. Impact: the change is cleared to merge.

Tested tree: the pull request head 78169a059ee7. Diff range 2e43b82a9fe7..78169a059ee7. CI shape read from .github/workflows/connector.yml: config .pre-commit-config.yaml, stages pre-commit.

Check Ran on Result Time
pre-commit (light hooks) local machine ok: 12 hook runs over pre-commit 35s
tests (pytest -q tests, full suite) separate build machine ok: 375 passed, 37 warnings in 50.43s 1m40s

Total time 1m42s. Verification: each check above was run on the tested tree and the result is the exit status of the repository's own commands.

@Knucklessg1
Knucklessg1 deleted the chore/scion-0101-rename branch November 13, 2026 00:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant