Sort the directory by Ops Impact, highest first - #56

What changed

The directory, the app's first page, listed software by name, so its first page showed whatever starts with "a". It now lists the most important software first:

1. Assessed software by Ops Impact, from 5 Critical down.
2. Then by Attention, from Severe down.
3. Then by name.
4. Software nobody has assessed comes after all of that, by name. Its Ops Impact is still the placeholder default of 3, which would otherwise mix it in with software graded Medium.

The directory also gets an Ops Impact column, left of SQA Level, shown as "5 Critical" or "Not assessed". Without it the order would follow a value the page does not show. The cell opens the assessment dialog, like the SQA Level and Attention cells.

Other effects:

• The embedded directory (loose=Y) gets the same order and column.
• The Sync page keeps its order by name.
• The software ID ends every order, so pages stay fixed when two repositories hold software of the same name.

Deployment and upgrade steps

None. There is no schema or settings change, and no SQL for existing databases.

Checks

• ./gradlew build: passes.
• ./gradlew integrationTest: passes, 53 tests, against the app rebuilt from this branch.
• New test SoftwareIT.directoryListsHighestOpsImpactFirst covers the order and a second page. Against the app built from main it failed, with the list coming back in name order.
• Page: looked at screenshots of /directory and /directory?loose=Y from headless Chromium, at 1400 px and 900 px wide, with six demo entries; the order and the new column were right.
• docker compose -f build.yaml logs sim: the only errors are the ones the integration tests cause on purpose (a duplicate name, and edits without permission).

Not checked:

• Clicking the new Ops Impact cell in a browser. It has the same risk-dialog-opener link as the cells beside it.
• The Sync page in a browser, since it reads the real GitHub and GitLab APIs. Its query now asks for name order explicitly.

Decisions

• Sort by Ops Impact, not Attention: Attention combines impact with fragility, so a robust mission-critical app (impact 5, fragility 1) rates only Moderate and would fall below a fragile impact-4 app.
• Unassessed software goes last instead of sorting at its placeholder impact of 3.
• The Ops Impact column was added so the order is visible; sorting by a hidden value was the alternative.
• No option to sort by name was added. The name filter still finds software by name; a sort choice in the filter panel could follow if people miss the old order.
• Screenshot.png in the repository is not updated and lacks the new column.

Release notes

The directory lists software by Ops Impact, highest first, with unassessed software last, and shows Ops Impact as a column. No upgrade steps.

Prepared-by: Anthropic Claude Code:claude-fable-5-2

🤖 Generated with Claude Code