release: 0.5.0b2

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

## Changelog

### Added
- Verbose validation warns when a SPARQL type or existence check follows a direct relation that has no `sh:node` auto-load. Without that declaration the related instance is not in the graph, so a valid link can fail the check. The warning covers `a`, `rdf:type`, full type IRIs, and hyphenated or URI property paths. Runs without verbose stay quiet.

### Fixed
- Upgrading the validation records container no longer flips required identity properties to optional. `ruleSetId`, `ruleSetVersion`, and `jobRunId` on `DataQualityValidationRecord` stay non-nullable, as do `ruleSetId`, `ruleSetVersion`, `ruleId`, and `runId` on `RuleEngineResult`. The previous full-property update sent the default optional flag and failed on projects where those fields were already required.
- Historic job status listing returns every matching HistoricJobQueue node. The previous 1000-node cap hid later queued, running, and superseded jobs, so a version-change enqueue could miss the previous job in the status list and the queue manager could skip jobs past that page.

### Changed
- Usage guides state that forward relation targets load only when `sh:node` declares them, and reverse neighbours only when `neat:reverseDirectRelation` declares them. Raising `auto_load_depth` alone does not load undeclared neighbours.
