refactor(aidd-dev): reserve test for automated technical tests

[blafourcade]

Problem

The technical aidd-dev:06-test action finds untested behavior and writes tests, but its contract does not distinguish unit, integration, and automated end-to-end tests or summarize the project\u2019s existing coverage. A developer can therefore receive new tests without a clear view of which critical behavior remains unprotected.

Implementation-independent browser acceptance QA is now owned by aidd-qa, delivered through #908 and PR #917. The remaining test-journey overlap and caller migration are owned by #919, not by this task.

Scope

• Restrict the technical test action to project-owned automated tests.
• Classify covered behavior as unit, integration, or automated E2E according to project conventions.
• Detect and run the existing project coverage command when one is configured.
• Summarize the relevant coverage result without inventing a percentage when the project provides none.
• Report critical behavior in scope that remains uncovered, with the reason it was not covered.
• Preserve the project\u2019s existing test framework and conventions.
• Update focused documentation, catalogs, and structural assertions affected by this narrower contract.

Acceptance criteria

• The technical test action creates or updates only project-owned automated tests.
• Generated tests are classified as unit, integration, or automated E2E using project conventions.
• An existing coverage command is executed and its relevant result summarized.
• No coverage percentage is fabricated when the configured tooling does not provide one.
• No test or coverage dependency is installed without explicit authority.
• Critical behavior left uncovered is reported with a reason.
• Existing test commands and conventions remain the source of truth.
• Focused contract tests distinguish technical automated testing from acceptance QA.

Relations

• feat(aidd-qa): create an implementation-independent QA plugin #908 and PR feat(aidd-qa): create an implementation-independent QA plugin #917 delivered the independent aidd-qa plugin.
• feat(aidd-orchestrator): add independent acceptance QA before draft pull requests #919 owns the decision, caller migration, and any removal or retention of test-journey. This task follows that decision and does not duplicate it.

Out of scope

• Functional acceptance QA and browser recordings.
• Deciding or migrating test-journey, owned by feat(aidd-orchestrator): add independent acceptance QA before draft pull requests #919.
• Fixing application code to make a test pass.
• Installing or replacing a test or coverage framework.