| 1 |
# Roadmap |
| 2 |
|
| 3 |
## Near-Term |
| 4 |
|
| 5 |
- Refine automatic layout defaults for the threat and treatment families. |
| 6 |
- Tune per-icon anchor geometry so edge contact points match the symbol |
| 7 |
silhouettes more tightly. |
| 8 |
- Expand the manual with more worked examples and troubleshooting guidance. |
| 9 |
- Complete the corrected first CTAN submission and verify the follow-up release |
| 10 |
workflow for later automated CTAN updates. |
| 11 |
|
| 12 |
## Good First Issues |
| 13 |
|
| 14 |
- Improve wording or examples in the manual. |
| 15 |
- Add more semantic failure tests for edge-case misuse. |
| 16 |
- Contribute additional example diagrams based on public CORAS scenarios. |
| 17 |
- Improve screenshot layout and release-site presentation. |
| 18 |
|
| 19 |
## Longer-Term |
| 20 |
|
| 21 |
- Improve layout heuristics without breaking the semantic API. |
| 22 |
- Evaluate broader engine coverage beyond `pdflatex` and `lualatex`. |
| 23 |
- Consider richer documentation generation if the plain `.sty` layout becomes |
| 24 |
limiting. |