0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-08 11:46:35 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.7 c55ad69c41 refactor: drop requirement-file references from code, add doc rule + lint

Strip every `req <NNN>`, `req-<NNN>`, `Requirement <NNN>`,
`requirement-<NNN>`, and `docs/requirements/<NNN>-...md` mention from
non-Markdown source files. Comments anchored to requirement numbers
rot when requirements are renumbered or rewritten and conflate
present-state behaviour (which the comment should describe) with the
audit trail of how the code got there (which belongs in commit
messages, PR descriptions, and the requirement file itself).

* Document the rule in `docs/contributing/documentation.md` under
  "Comments". Code MUST describe the *why* in present-state language;
  contract enforcement lives in tests, not folklore.
* Clean 254 source files across `roles/`, `tests/`, `plugins/`,
  `cli/`, `scripts/`, `utils/`, `group_vars/`, and the repo-root
  `eslint.config.js`. Pure comment / docstring / log-message edits;
  no behavioural change.
* Add `tests/lint/repository/test_no_req_references_in_code.py` to
  enforce the rule going forward across `.js`, `.py`, `.yml`,
  `.yaml`, `.j2`, and `.sh` files. The legacy
  `test_no_stale_requirement_refs.py` is exempt as the only file
  whose purpose is to detect these very tokens.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-10 16:25:22 +02:00

__init__.py

…

application_domain_index.py

chore(ruff): enable TC + N rules

2026-05-08 18:57:07 +02:00

list.py

refactor: drop requirement-file references from code, add doc rule + lint

2026-05-10 16:25:22 +02:00

primary_domain.py

…

README.md

…

README.md

Domain Helpers 🌐

This package contains shared domain-related utility code for Infinito.Nexus.

The purpose of this folder is to keep domain logic in one predictable place so different plugins, helpers, and automation paths can rely on the same behavior. Rather than being tied to one feature, the code here supports the broader shape of how domains are interpreted, normalized, collected, and reused across the project. 🧭

Content in this package should stay:

small and composable
focused on reusable domain behavior
independent from feature-specific application flows
safe to import from multiple parts of the codebase

In short, utils/domains/ exists to make domain handling consistent, central, and easy to evolve without scattering similar logic throughout the repository. 🧩