Conversation
…acy paths"aliases
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
This PR merges the release/v1.0.0-finalize branch into develop.
It consolidates architectural alignment, authorization hardening, performance fixes, and release posture preparation before tagging the first stable version.
This is a structural stabilization step, not the final public release tag.
Key Changes
Domain & Authorization
Canonical membership model alignment
Repository-driven authorization checks
Removal of in-memory permission validation
404 concealment for non-participants
Chat history contextual authorization fix
Performance
Critical N+1 removals
Fetch strategy improvements
Reduced lazy traversal overhead in list endpoints
Configuration
Hardened release profile (ddl-auto=validate)
Dev/release profile separation
Actuator exposure tightened
Testing
Expanded service and domain test coverage
Security behavior validated
Clean database validation workflow confirmed
Type of change
Validation
Commands run:
Docs impact
Security impact
Repository-based authorization
404 concealment
Chat contextual hardening
Release config hardening