Skip to content
This repository was archived by the owner on May 29, 2026. It is now read-only.

docs(audit): record parafering audit umbrella rule (closes #406)#495

Merged
rubenvdlinde merged 1 commit into
developmentfrom
feature/migrate-parafering-to-or-audit
May 19, 2026
Merged

docs(audit): record parafering audit umbrella rule (closes #406)#495
rubenvdlinde merged 1 commit into
developmentfrom
feature/migrate-parafering-to-or-audit

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

(re-opened of #412 — accidentally closed by harness force-push; same branch, same content)

Implements migrate-parafering-to-or-audit — adoption-only scope per investigation.

Investigation finding

The spec assumed procest had a ParaferingAuditListener + ParaferingAuditAppendOnlyValidator + paraferingAuditEntry schema. None exist. The Listener dir contains only DeepLinkRegistrationListener + KpiCacheInvalidationListener, and Application.php has no audit-listener registrations.

Parafering audit today lives as an in-object auditTrail array on the voorstel inside ParaferingService. The spec's framing doesn't match the code.

What this PR does

Records the umbrella rule in the spec so any future parafering-audit work routes through OR's AuditTrailMapper::createAuditTrailEntry() per ADR-022. The in-object array migration is a follow-up — it needs concurrent reader updates in views + a controller-side ObjectEntity resolution step that the current ParaferingService array-only API doesn't provide.

Scope adjustment documented inline in tasks.md.

Closes #406.

@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 42b0c81

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
composer ✅ 100/100
npm ✅ 420/420
PHPUnit
Newman ⏭️
Playwright

Quality workflow — 2026-05-19 03:35 UTC

Download the full PDF report from the workflow artifacts.

… needed)

Implements migrate-parafering-to-or-audit — adoption-only scope per investigation.

Investigation finding:
- No `ParaferingAuditListener.php` exists.
- No `ParaferingAuditAppendOnlyValidator.php` exists.
- No `paraferingAuditEntry` schema in procest_register.json.
- `Application.php` has no audit-listener registrations.
- Parafering audit currently lives as an in-object `auditTrail` array on
  the voorstel inside `ParaferingService`.

The spec's framing (separate listener + parallel schema + append-only
validator) does not match procest's code. Future parafering audit work
MUST route through OR's `AuditTrailMapper::createAuditTrailEntry()` per
the umbrella consume-or-audit-trail-fleet-wide (ADR-022).

The in-object `auditTrail` array migration is a follow-up — it needs
concurrent updates to readers in views and a controller-side ObjectEntity
resolution step the current array-only ParaferingService API doesn't
provide.

Tasks updated to reflect the codebase-vs-spec gap.

Closes #406
@rubenvdlinde rubenvdlinde force-pushed the feature/migrate-parafering-to-or-audit branch from 6e2b355 to 4a16f70 Compare May 19, 2026 03:46
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 32e729f

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
composer ✅ 100/100
npm ✅ 420/420
PHPUnit
Newman ⏭️
Playwright

Quality workflow — 2026-05-19 03:51 UTC

Download the full PDF report from the workflow artifacts.

@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 00c60de

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
composer ✅ 100/100
npm ✅ 420/420
PHPUnit
Newman ⏭️
Playwright ⏭️

Coverage: 0% (0/81 statements)


Quality workflow — 2026-05-19 04:10 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde rubenvdlinde merged commit e34236c into development May 19, 2026
48 checks passed
@rubenvdlinde rubenvdlinde deleted the feature/migrate-parafering-to-or-audit branch May 19, 2026 05:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant