docs(issues): ISSUE-158 correction; ISSUE-112 and ISSUE-117 pass on Egeria main

[dwolfson]

Three PYEGERIA_ISSUES.md updates. Docs only; no code changes.

ISSUE-158 correction

The entry (added in #465) said a caller-built DataQualityRuleProperties body is refused by pyegeria before it reaches the server. That is true only for updates:

• validate_new_element_request has its property-class check commented out, so create_governance_definition sends the body to Egeria unchanged.
• validate_update_element_request checks a dict body's class against GOV_DEF_PROPERTIES_LIST, so update_governance_definition refuses a DataQualityRule body.

ISSUE-112 re-test: pass on Egeria main 05a5e982

Resource Explorer re-tested the client-side secrets fix on 2026-10-20, using two throwaway secrets-store graphs:

• Read-only store (YAMLSecretsStoreProvider): save_client_side_secret now raises OMAG-COMMON-400-034 and writes no file. Before the fix it reported success without writing anything.
• Writable store (YAMLSecretsFileProvider): the save succeeds and writes the file.

All throwaways were removed afterwards.

ISSUE-117 soft-delete (Memento) path: pass on Egeria main 05a5e982

Resource Explorer re-tested the original failing case on 2026-10-20. A throwaway CSV asset was made the target of a real, executed engine action, by starting the "Actor, Places and Products" evaluation-subscription process with the asset as destinationDataSet. A cascade delete with forLineage false then succeeded, and the asset with its anchored Connection and Endpoint read back as soft-deleted. Nothing was left live or half-deleted. An engine action that was never started, linked to the asset directly, makes Egeria purge instead, so it doesn't reach this path.

🤖 Generated with Claude Code