Bottybotsterson 6196b788fd Test harness as its own app (WscMvcTests site), sharing the same framework At Daniel's explicit direction: /self-test moves off the production site entirely, onto a second, separate IIS site/app. - test-app/public/: own site (WscMvcTests, *:8091), own web.config (routes only /self-test), own logs/ - genuinely isolated from production traffic - Default.asp duplicated into test-app/public/ (intentionally byte- identical - the bootstrap is fully generic, IIS just requires each site to have its own physical files; documented 'keep in sync' in both copies) - No framework/business-logic duplication: both sites share the exact same registered Framework/Controllers COM components. Application.wsc's /self-test route case is unchanged; only removed the production site's web.config rewrite rule that used to expose it there - production public/web.config: dropped /self-test rewrite rule; GET /self-test on production now plain 404 (nothing routes there) - tools/Setup-Site.ps1: now automates the logs/ IIS_IUSRS ACL grant (previously a manual one-off command), scoped per-site; also hardened with ='Stop' + a PhysicalPath pre-check after finding it silently continued past a real New-Website failure - tests/Test-Http.ps1: production-only now (checks /hello + confirms /self-test is genuinely unreachable there); tests/run-self-test.sh points at the new WscMvcTests site - Verified both sites end-to-end: correct routes, correct 404s for cross-site/Framework access, separate log files, idempotent Setup-Site.ps1 reruns for both sites - SPEC.md, docs/ARCHITECTURE.md, docs/DECISIONS.md, docs/TEST-RESULTS.md, README.md updated to match; README also brought current after being stale since M1		2週間前
Controllers	Add frontend-agnostic HTTP+JSON test harness (GET /self-test)	2週間前
Framework	Add frontend-agnostic HTTP+JSON test harness (GET /self-test)	2週間前
docs	Test harness as its own app (WscMvcTests site), sharing the same framework	2週間前
public	Test harness as its own app (WscMvcTests site), sharing the same framework	2週間前
test-app/public	Test harness as its own app (WscMvcTests site), sharing the same framework	2週間前
tests	Test harness as its own app (WscMvcTests site), sharing the same framework	2週間前
tools	Test harness as its own app (WscMvcTests site), sharing the same framework	2週間前
.gitignore	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2週間前
AGENTS.md	Import WSC-MVC agent starter pack (SPEC, AGENTS, IMPLEMENTATION_PLAN, CLAUDE, README)	2週間前
CLAUDE.md	Import WSC-MVC agent starter pack (SPEC, AGENTS, IMPLEMENTATION_PLAN, CLAUDE, README)	2週間前
IMPLEMENTATION_PLAN.md	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2週間前
README.md	Test harness as its own app (WscMvcTests site), sharing the same framework	2週間前
SPEC.md	Test harness as its own app (WscMvcTests site), sharing the same framework	2週間前

README.md

WSC-MVC

A small, WSC-first MVC framework for Classic ASP on IIS: VBScript Windows Script Components registered as COM, dispatched by a single thin Default.asp bootstrap. See SPEC.md for the full contract, IMPLEMENTATION_PLAN.md for milestone status, and docs/ for architecture, decisions, and test evidence — those are the authoritative, kept-current docs; this file is just an orientation map.

Layout

Two separate IIS sites, sharing one set of framework/controller COM components:

public/ — the production site's IIS physical path. Contains only Default.asp and web.config.
test-app/public/ — a second, separate site exposing GET /self-test (JSON test harness), so diagnostics aren't reachable on the production site/port. See docs/ARCHITECTURE.md.
Framework/, Controllers/ — the actual WSC components (.wsc), registered once via COM and used by both sites. Never served over HTTP by either site.
logs/, test-app/logs/ — each site's own runtime log, written by the app, never served over HTTP.
tests/, tools/, docs/ — test scripts, deployment/registration tooling, and documentation. Never served over HTTP.

Deploy and register (on the target Windows/IIS host)

powershell -File tools\Register-Components.ps1
powershell -File tools\Setup-Site.ps1
powershell -File tools\Setup-Site.ps1 -SiteName WscMvcTests -PoolName WscMvcTests -PhysicalPath <repo>\test-app\public -Port 8091

Both Setup-Site.ps1 invocations are idempotent — safe to re-run after any deploy.

Test

cscript //nologo tests\Test-Components.vbs          # WSH smoke test, no IIS needed
powershell -File tests\Test-Http.ps1 -BaseUrl http://localhost:8090   # production site

./tests/run-self-test.sh http://<host>:8091          # test-app site, plain curl+JSON, any CLI

Status

M0–M2 gated PASS with real test evidence on Windows/IIS; see docs/TEST-RESULTS.md. Next milestone: M3 (explicit route table) per IMPLEMENTATION_PLAN.md.