Task: Build the Reporting lines screen

A tenant administrator reads the reporting shape as a tree, selects a person, and changes or clears their manager with a recorded reason.

• The screen runs in ores.web on the accepted variant A: the indented tree with the selected person beside it.
• The tree states each person, the manager each reports to in the panel, the depth, and how many report to them directly.
• The manager picker cannot offer the person or anybody who reports to them, so a ring cannot be asked for from the screen.
• Saving states a reason and a note, and sends the narrow write with the account version the panel read, so a concurrent change is refused as a conflict and stated.
• A person who reaches no root is stated rather than drawn as a root.
• The gaps the journey still records are stated: the office is not readable, the approval is not held, and the line has no history here.
• The screen passes its own tests, and the route table test reaches it from the people list.

1. Draw the tree from the shape read the group's server task landed, with expand and collapse, and the selected person in the panel beside it.
2. Take the manager candidates from the tree itself: everybody except the person and their branch.
3. Read the selected person's account for the version the narrow write states back, so a change made elsewhere is refused rather than overwritten.
4. State the gaps that remain on the screen, as the story's acceptance requires.
5. Add the route, the entry point on the people list, and the labels.

• The manager candidates come from the tree, not from a read. The picker offers everybody in the shape except the person and their branch, computed from the same answer the tree is drawn from. The server refuses a ring too; the screen refusing to ask for one is what keeps the two honest rather than relying on the refusal.
• The version the write states comes from the account read, not the tree. The tree read answers the shape and no version, so selecting a person reads their account for it. That read is the administrator's ordinary account read, and a failure there states that the write will carry no version rather than pretending to have one.
• The journey's remaining gaps are drawn, not hidden. The story's acceptance is that every gap a journey records is closed or stated on the screen, so the panel at the foot names the three that remain rather than leaving a reader to find them.
• The entry point is the people list. The administrator arrives from the roster they were already reading, so the button sits on that screen's header rather than in the member's account menu.

Done 2026-10-09.

Reporting lines runs in ores.web on the accepted variant A:

Verification. The web suite passes, 479 tests in 46 files, five of them this screen's own and the route reaching it. The three TypeScript packages typecheck, and compass lint passes.

Limitation. As with the member's screen, this one is not walked by hand against a running installation: the environment's database was recreated for the group's SQL change, so no tenant with a reporting line exists to sign in as. The read and the write it drives are covered by the server suite and the BFF cases, and the screen by its own.