Merge commit 'baa0695c60153bc997ebf8b11adcfbdd2cbc1962' into work/reports-ui

# Conflicts:
#	src/main/resources/templates/projects/detail.html
#	src/main/resources/templates/projects/form.html
#	src/main/resources/templates/projects/leadership.html
#	src/main/resources/templates/projects/members.html
This commit is contained in:
sechmachine
2026-08-15 03:34:26 +07:00
34 changed files with 994 additions and 48 deletions
+18 -2
View File
@@ -4,7 +4,7 @@
- **Requirement IDs:** `ARC-002`, `ARC-005``ARC-007`, `OPS-018``OPS-020`, `TST-001``TST-010`
- **Scenario IDs:** `I1-PRJ-01``I1-PRJ-05`
- **Test class/method:** `com.lab.labtimesheet.feature.project.repository.ProjectPersistenceStructureTest#projectPersistenceUsesTheRequiredLayerPackagesAndSpringDataJpa`
- **Implementation commit:** `25a855e`
- **Implementation commits:** `25a855e`, `af0eb3c`
## Protected behavior
@@ -70,6 +70,22 @@ export PATH="$JAVA_HOME/bin:$PATH"
[INFO] BUILD SUCCESS
```
## Iteration 1 Javadoc retrofit verification
No behavioral RED was manufactured for documentation. The initial Project-scoped doclint run
reported 29 warnings for missing type comments, an implicit public advice constructor, and
accessor comments without main descriptions. After documenting every Project-owned production
type and declared public/protected API, the same scoped command passed:
```text
export JAVA_HOME=/opt/homebrew/opt/openjdk@25
export PATH="$JAVA_HOME/bin:$PATH"
./mvnw -DskipTests -Dmaven.javadoc.failOnWarnings=true -Ddoclint=all -Dsubpackages=com.lab.labtimesheet.feature.project javadoc:javadoc
[INFO] BUILD SUCCESS
[INFO] Total time: 2.579 s
```
## External-test boundaries
This check does not prove database mappings, transaction behavior, MVC routing, or runtime authorization; those remain covered by PostgreSQL and MockMvc tests.
This check does not prove database mappings, transaction behavior, MVC routing, or runtime authorization; those remain covered by PostgreSQL and MockMvc tests. Whole-application fail-on-warning Javadoc remains an integration responsibility after every feature owner completes the approved Iteration 1 retrofit; this evidence deliberately scopes generation to the Project-owned package.