S19: consume versioned engineering resources and move landscape documentation
All checks were successful
Build, test and publish / verify (push) Successful in 8m54s
All checks were successful
Build, test and publish / verify (push) Successful in 8m54s
This commit is contained in:
23
README.md
23
README.md
@@ -1,3 +1,18 @@
|
||||
# Landscape and shared engineering
|
||||
|
||||
Architecture decisions, specifications and project onboarding are maintained in
|
||||
[landscape](http://192.168.2.28:3000/wanjakrah/landscape). Reusable tooling, skills,
|
||||
standards and the project generator are maintained in
|
||||
[engineering](http://192.168.2.28:3000/wanjakrah/engineering).
|
||||
|
||||
This project commits the engineering version recorded in `engineering.lock.json`
|
||||
under `generated/`. Ordinary builds need no other repository checkout. Regenerate
|
||||
with `mvn -N -Pregenerate-engineering validate`; CI checks the selected tag and
|
||||
commit with `python3 scripts/engineering.py --check`. To upgrade, update both tag
|
||||
and commit, follow engineering's UPGRADING.md, regenerate and review the diff.
|
||||
Project configuration in `engineering.properties`, workflows and `deploy/` remains
|
||||
application-owned. Read CODING_STANDARDS.md and AGENTS.md for project guidance.
|
||||
|
||||
# agiledancers
|
||||
|
||||
To map dance groups to performance days. The backend runs on Quarkus with Java 25.
|
||||
@@ -299,7 +314,7 @@ during the one-time transition from an in-memory release, and [S6 evidence](docs
|
||||
|
||||
Maven is the authoritative formatting path. The root build runs the actual
|
||||
Palantir Java Format **2.101.0**, Palantir style, through a custom OpenRewrite
|
||||
**8.63.4** text recipe in `tooling/format/Format.java`. The pinned
|
||||
**8.63.4** text recipe in `generated/tooling/format/Format.java`. The pinned
|
||||
`exec-maven-plugin` **3.6.3** launches that helper with JDK 25. Native import
|
||||
ordering and unused-import removal are enabled; extra Javadoc formatting is off.
|
||||
No OpenRewrite AutoFormat or additional refactoring recipes run.
|
||||
@@ -344,9 +359,9 @@ format-on-save must not override Maven's result. Other editors can invoke the
|
||||
standalone Maven apply command as an external tool.
|
||||
|
||||
Verification and measurements are recorded in
|
||||
[the S8 evidence](specs/S8-formatting-evidence.md). Reproduce the isolated failure,
|
||||
[the S8 evidence](docs/validation/S8-formatting-evidence.md). Reproduce the isolated failure,
|
||||
UTF-8, import, cache and idempotence checks with
|
||||
`python3 tooling/format/test.py`, and the sequential end-to-end build measurements
|
||||
the formatter integration test in engineering (`python3 tests/format_integration.py`), and the sequential end-to-end build measurements
|
||||
with `python3 tooling/format/benchmark.py` (requires the ordinary backend test
|
||||
prerequisites). Results are written under `target/`.
|
||||
|
||||
@@ -357,7 +372,7 @@ It defines the agreed rules, exact metric limits, manual review duties, pinned
|
||||
analysis tools, coverage policy and standalone commands. `mvn verify` runs standards
|
||||
checks and requires at least 80% module-wide backend line coverage. CI also collects
|
||||
and merges coverage from Playwright before publication. Reports are retained with
|
||||
CI diagnostics. See [S7 validation](specs/S7-validation.md) for current migration status.
|
||||
CI diagnostics. See [S7 validation](docs/validation/S7-validation.md) for current migration status.
|
||||
|
||||
|
||||
Existing-school mutations require `X-School-Revision` with the revision loaded by
|
||||
|
||||
Reference in New Issue
Block a user