docs: documentation review for v2.14.0

Architecture, README, standards, CLAUDE.md, settings reference, indexes,
backlog, release plans and CHANGELOG checked against the code at v2.14.0:
backfeed, notifications, counts line and web actions documented; test
policy (changed area locally, full suite in CI); stale versions, statuses
and links fixed; legacy and superseded docs moved.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
PhilandClaude Opus 5.5 committed 2026-11-10 14:51:57 -07:00
1 parent caa66f7bb1
commit ceef048003
46 files changed
+476 -216

No files matched your search

+2 -4
View File
@@ -1,12 +1,11 @@
# Python Coding Standards
**Status**: Active
**Last Updated**: 2026-11-03 (v2.10.1)
**Last Updated**: 2026-11-10 (v2.14.0)
How Python code in StarPunk is written. The project rule comes first:
"Every line of code must justify its existence. When in doubt, leave it
out." Patterns specific to small helper functions are in
[utility-function-patterns.md](utility-function-patterns.md).
out."
## Base style
@@ -147,5 +146,4 @@ functions or `Test...` classes with descriptive names
## References
- [PEP 8](https://peps.python.org/pep-0008/), [PEP 257](https://peps.python.org/pep-0257/), [PEP 484](https://peps.python.org/pep-0484/)
- [utility-function-patterns.md](utility-function-patterns.md)
- [ADR-055: Error handling philosophy](../decisions/ADR-055-error-handling-philosophy.md)