release 0.5.0

## Bump
- [ ] Major
- [ ] Minor
- [ ] Beta
- [x] Patch
- [ ] Skip

## Changelog

### Added
- First stable 0.5 release. It includes the 0.5.0 prereleases: constraint display names (`shaclName`, `failedConstraintNames`), record views for Flows, filterable `ruleId`, edge-view SHACL, focus RuleSet binding, reverse auto-load for MultiReverseDirectRelation, and the packaged Atlas rule-authoring agent.
- Atlas skill `dq-shacl-rule-audit` reviews existing SHACL for wrong class or space URIs, reverse versus forward relations, missing auto-load stubs, and prose that overclaims uniqueness or presence. An audit-only request does not submit or test rules.
- Usage guide for chunk size and auto-load limits. `chunk_size` is how many focus instances one call validates. `max_reverse_relations_per_query` (default 1000) caps the reverse list for the whole chunk, not per focus. A reverse Consistency miss that passes for one instance is often that cap. Lower `chunk_size` on a reverse-heavy view as a mitigation.
- A time series schedule filter accepts `type: numeric` or `type: string`. Omitting `type` still selects both.

### Fixed
- Each view binds to the RuleSet whose focus target class is that view. Neighbour stubs, including shapes named ExistenceShape, do not attach that RuleSet to the neighbour view. Records `ruleSetId` and `ruleSetVersion` come from that focus RuleSet, not from `quality.rules` order.
- A reverse type check fails when nothing points at the focus node. When several neighbours exist, a wrong type on any of them fails the check. Reverse auto-load quotes external ids and keeps each node's view.
- A Consistency SPARQL check uses `sh:name` on its property shape. Numeric aggregates (`datapoints_min`, `datapoints_max`, `datapoints_average`, and `datapoints_aggregate` except `count`) skip a string time series. Count and existence checks still run.
- Publishing a ruleset does not start a second historic job while one run for that view is still active. A partial Records post does not advance the historic or sync cursor past instances that were not stored.
- Atlas post-deploy verify rejects a remote agent with runtime 1.x or missing packaged skills.

### Changed
- Forward targets load only when `sh:node` declares them. Reverse neighbours load only when `neat:reverseDirectRelation` or recognized reverse SPARQL declares them.
- Redeploy the validation function, re-apply the records container and record views, and run Data Product sync or deploy. Redeploying the validation function does not upsert Atlas. Call `deploy_atlas_rule_authoring` or enable `atlas_rule_authoring` on infrastructure deploy, with verify, so the agent runtime and packaged skills match this release.
