danhaywood opened a new pull request, #3913:
URL: https://github.com/apache/causeway/pull/3913

   ## Summary
   - Forward-port roadmap step 10b from maintenance commit `473454f2447`.
   - Add one semantic observation per invoked action/view primer, preserving 
sequential sibling scopes without aggregate or unmatched spans.
   - Retain bounded domain-facing names, complete static canonical metadata and 
resolved action parameter signatures.
   - Preserve natural parentage/JDBC ownership, request admission, fail-fast 
behavior, original failures and absent/no-op integration behavior.
   - Add focused and Boot/agent exported-trace regressions, documentation, 
synced specs and archived OpenSpec artifacts.
   
   ## Validation
   - 66 focused registry, hook, identity and lifecycle tests passed after the 
implementation checkpoint.
   - Full Wicket UI/viewer suite passed 113 executed tests, with five existing 
skips.
   - All 23 tracing/JPA tests passed after the checkpoint.
   - Export checks cover per-callback siblings, action/view ancestry, JDBC 
descendants, preparation ordering, failure followed by success and 
inactive/absent-exporter modes.
   - Both guide pages rendered; strict OpenSpec validation and whitespace 
checks passed.
   - These checks ran before the subsequent rebase onto main; they have not 
been rerun after that rebase.
   
   ## Scope
   - Builds on priming-hook PR #3912, now merged; this PR contains only primer 
observations.
   - No public SPI, dependency, configuration or tracing pipeline was added.
   - Fixtures exercise the real registry, request admission and Wicket 
lifecycle with controlled metamodel/callback collaborators and H2 SQL, not a 
complete ORM-backed application/browser deployment.
   - Independent metamodel diagnostics and mixin prefiltering remain separate 
roadmap items.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to