- Shipped
- October 5, 2026 at 4:36 AM UTC
- Author
- Kamo
- Commit
- 9d839e5
Appends TEAM to CharterLevel (after DEFAULT; ORG from CP03 comes next, R1-11) and states in its Javadoc that resolution order is CharterLayer.rank, never the declaration order. CharterItems.validate needs no change: TEAM is neither ROLE nor MEMBER, so it follows the job title's rules. Tests: a team may hide and lock; every section validates at TEAM as at JOB_TITLE; two peer TEAM layers between a job title and a member (first in list order wins a SPECIFIC key and the conflict names the other, ADDITIVE unions, a team hides a job-title item, the member hides a team item, peers cannot hide each other); the L|/I| lines of a team-less chain's canonical stamp text equal the lines captured on main (no hash pinned, R1-1); a TEAM layer adds only its own lines. CharterEnumsTest names the levels in any order (R1-11).