@jrpool/kilotest 59.1.1 → 59.1.2

package/docs/decisions/009-qai-integration.md

@@ -1,40 +0,0 @@
----
-date: 2026-09-14
-status: accepted
----
-
-# QAI integration
-
-## Context and problem
-
-The QAI application (at `https://github.com/jrpool/qai`) is a small standalone Node.js server deployed at `https://kilotest.com/qai`. QAI is a tutorial showing users how to connect AI platforms (specifically, Claude on `claude.ai`) to Kilotest's MCP server. The `kilotest` repository already provides a tutorial showing users how to use Kilotest itself. The two-repository split was required by an organizational constraint that no longer applies. QAI's own purpose (teaching users how to connect an AI platform to Kilotest) makes it naturally a part of Kilotest's tutorial content. Should QAI remain a separate deployment, or be folded into Kilotest?
-
-## Considered options
-
-1. **Keep separate:** QAI remains an independent repository with its own deployment, continuous integration, and process management.
-2. **Merge into Kilotest:** Port QAI's tutorial content and comment-collection infrastructure into Kilotest as a second tutorial module, retire QAI as a separate deployment, and simplify the Caddyfile and process management.
-
-## Decision
-
-**Merge into Kilotest**, because:
-
-- QAI is fundamentally tutorial content for Kilotest, not an independent application. Keeping it in a separate repository obscures this relationship.
-- Merging eliminates duplicate infrastructure: both repositories use the same comment-storage pattern, alert environment variables, build configuration, and type-checking standards. A single repository reduces maintenance burden.
-- The existing `web/tutorial/` pattern in Kilotest provides a proven, documented template for modules combining an HTML page with a comment-collection form and email alerts. QAI's infrastructure was originally designed by copying this pattern; reusing it directly instead of maintaining a reimplementation aligns the codebase with DRY principles.
-- Simplifying the Caddyfile and process management reduces the risk of configuration drift, and makes the deployment easier to reason about.
-- Merging improves the documentation standard. QAI includes 9 ADRs and architectural/requirements/deployment documentation that enriches Kilotest's own documentation, which initially had only 2 ADRs.
-
-### Confirmation
-
-To confirm that the implementation is correct:
-
-1. All tests pass with 100% coverage, and linting and type-checking produce no errors.
-2. The new QAI tutorial page and comment form are reachable and functional at their new `/tutorialAI.html` path.
-3. The old QAI paths (`/qai`, `/qai/comments`) redirect correctly to the new paths.
-4. Comments submitted to the new form are stored correctly and trigger email alerts as configured.
-
-## Historical context
-
-QAI was initially developed as an independent deployment partly because Kilotest had not yet implemented monitoring and alerting infrastructure. By the time QAI reached deployment, both QAI and Kilotest had similar comment-collection and alerting patterns. Keeping QAI separate after this convergence created unnecessary duplication. This merge resolves that architectural drift and reestablishes Kilotest as the canonical location for all Kilotest-related tutorial content.
-
-The separate `jrpool/qai` repository is preserved as a historical archive in `jrpool`'s account and can be kept as read-only history for reference.

package/docs/decisions/QAI-HISTORICAL-CONTEXT.md

@@ -1,42 +0,0 @@
-# QAI historical context
-
-This document preserves pointers to documentation and development history from the `jrpool/qai` repository, which was integrated into Kilotest as part of the decision documented in [ADR 009](./009-qai-integration.md).
-
-## QAI architectural decisions (superseded or historical)
-
-The following ADRs from QAI are not ported to Kilotest, but their reasoning and historical context are preserved in the `jrpool/qai` repository for reference:
-
-- **003-initial-routing.md**: QAI originally chose to deploy as an independent service on a separate port, separate from Kilotest's port 3000. This was driven by course requirements and the need for QAI to have evaluable infrastructure of its own. ADR 009 documents the superseding decision to integrate QAI into Kilotest's deployment.
-
-- **004-prerelease-versions.md**: QAI used prerelease versioning (0.1.0, etc.) during initial development. This versioning scheme is not carried forward to the integrated Kilotest; Kilotest's own version scheme applies to all content.
-
-- **005-infrastructure-health.md**: QAI originally required its own external monitoring with UptimeRobot because Kilotest lacked health monitoring infrastructure. This constraint is now resolved; Kilotest's unified monitoring and alerting (covered in ADR 005-observability.md) applies to both the tutorial content and any other components.
-
-## QAI development history
-
-Sprint reports, peer reviews, and development progress documentation are preserved in the `jrpool/qai` repository:
-
-- `docs/progress-reports/` contains sprint reviews and reflections from the course development of QAI (sprints 3–5).
-- `docs/reviews/` contains peer review feedback on QAI's initial implementation.
-
-This historical record is retained in `jrpool/qai`'s git history and is not duplicated in Kilotest's codebase.
-
-## Branch protection and CI configuration
-
-QAI's GitHub branch-protection ruleset (`docs/rulesets/qai-main.json`) enforced requirements similar to those already in place for Kilotest. Kilotest's own branch protection, documented in `docs/SERVICE.md`, supersedes QAI's configuration, and the separate QAI ruleset file is not ported.
-
-## QAI domain-specific documentation
-
-The following documents from QAI are superseded by the integration:
-
-- **`requirements.md`**: Documented QAI's specific functional requirements. These remain valid for the integrated tutorial, but are now framed as part of Kilotest's tutorial offerings rather than QAI-specific product requirements. Tutorial requirements are documented in the code comments and inline in `web/tutorialAI/index.ts` rather than as a separate file.
-
-- **`architecture.md`**: Described QAI as an independent deployment. With integration, QAI's architecture is now part of Kilotest's architecture, and the former QAI-specific architectural overview is superseded by Kilotest's architecture and API design documented in the main codebase and in [ADR 001 (API design)](./001-api-design.md).
-
-- **`deployment.md`**: Documented QAI's guest deployment on Kilotest infrastructure and its PM2 configuration. With QAI integrated into Kilotest, a single deployment configuration applies to both. PM2 and infrastructure details are now documented in `docs/SERVICE.md` with no separate QAI-specific deployment doc.
-
-- **`repository.md`**, **`project-vision.md`**: Project-management framing specific to QAI as a university-course project. These provide historical context but are not carried forward to Kilotest's documentation.
-
-- **`future.md`**, **`ai-implementation-review.md`**: Point-in-time project status and review artifacts. Historical context and any actionable ideas are incorporated into the main codebase and Kilotest's backlog; the original documents are not ported.
-
-- **`manual-verification.md`**: Documented QAI's testing and deployment verification procedures. Kilotest's unified test suite and continuous-integration configuration now cover the integrated tutorial content. Some manual verification procedures from QAI (such as form submission and alerting) are mirrored in Kilotest's `smokeTest.ts` and existing test suites.