feat(product-manager): subscription types and ODCS/ODPS documents, with Dr.Egeria commands

[dwolfson]

Summary

Three commits (plus an issues-log commit), reviewable one at a time.

1. SDK (ProductManager): the eleven product-manager calls the refreshed .http documents that the SDK lacked (the audit's product-manager section went from 11 missing to 0):

• create_one_time_subscription / create_periodic_subscription / create_ongoing_update_subscription add a subscription type to a digital product and return the GUID of the governance action process that creates subscriptions of that type.
• publish_data_contract_string / publish_data_product_string send an ODCS / ODPS document to an integration daemon's Bitol listeners.
• import_data_contract[_string] / import_data_product[_string] catalog an ODCS agreement / ODPS digital product.
• generate_data_contract / generate_data_product.
• The string endpoints take text/plain, so _async_make_request gains a keyword-only as_text flag. It uses the existing, previously unused text_headers, the default is unchanged, and it survives the 401 retry.

2. Dr.Egeria commands (Digital Product Manager family): Create Subscription Type, Import Data Contract, Import Data Product, Publish Data Contract, Publish Data Product.

• All five are safe to re-run, which I checked in Egeria's source and then live. They have no Update form.
• Create Subscription Type produces the governance action process that the Automation family's Initiate Subscription runs.
• Documents are read from a Document File path, resolved against the markdown file (new input_path in the processing context), not inline, because YAML's --- and # lines are horizontal rules and headings to the extractor.
• Import and Publish are added to STANDARD_VERBS; without that the headings silently fall through as prose.
• The notification interval has its own attribute, Subscription Notification Interval (minutes). The Governance Officer family's Notification Interval is milliseconds and attribute names are global, so reusing it would have sent values off by 60,000x.
• Specs edited via the Spec Editor API. validate_compact_specs, refresh_specs --merge-reports and the attribute-consumption audit are clean. docs/dr_egeria_manual.md updated.

3. get_governance_action_processes_by_name (Product Catalog view service's governance-definitions/by-name), which finds the process Initiate Subscription runs. There is no Product Catalog client, so it lives on ProductManager with its own URL.

Live verification (2026-10-05, dev quickstart platform, through the real dr_egeria --process CLI)

	result
Create Subscription Type, all three kinds (ONE_TIME, PERIODIC, ONGOING_UPDATE with a monitored resource)	works; run twice, exactly one process per type afterwards (idempotent)
Import Data Contract / Import Data Product	work; re-importing returned the same GUIDs (updated in place)
generate_data_contract	reads back the full ODCS document with its schema
get_governance_action_processes_by_name	used to verify the above
Publish Data Contract / Publish Data Product, generate_data_product, the import_* bean (dict) forms	not exercised live (publishing needs an integration daemon with a Bitol listener)

Everything the check created was removed and verified gone by GUID.

A first live attempt exercised nothing: the shared checkout was on the wrong branch, so the CLI answered "No processor registered" (a warning, exit code 0). It was caught, the scripts now preflight the branch, and the run above is the real one.

Found along the way (logged, not fixed here)

• ISSUE-126: ProductManager and DigitalBusiness never call CollectionManager.__init__, so 27 inherited collection methods raise AttributeError on them.
• ISSUE-127: CollectionManager.delete_collection(cascade=True) silently never sends cascadeDelete (same shape as ISSUE-62). Egeria also refuses to delete a DataStructure that has a member DataField even with cascade, so an imported contract must be removed child-first.

Test plan

• SDK: 16 micro-tests (URL, verb, body, content type, return value; as_text verified through the real _async_make_request with only httpx stubbed)
• Dr.Egeria: 20 micro-tests through the real dispatcher with a fake client, incl. validation failures, relative-path resolution, and the new verbs being extracted as commands
• Full tests/micro-tests passes locally (906 collected)
• scripts/omvs_audit.py --service product-manager: 0 missing, 0 mismatched
• Live: the table above

🤖 Generated with Claude Code