Bottybotsterson 93455d1e49 M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed - RequestContext.wsc: per-request path/method/correlationId/elapsed-time, primitive-only, no ASP intrinsics - Application.Run(ctx, ...) centralizes expected-vs-unexpected outcomes and best-effort logging to logs/app.log (lock-file mutex, no ASP Application intrinsic available by contract) - Fixed: Property Get requires a Class block, fails at WSC top level (regsvr32 exit 5) -> switched to plain Function-based getters - Fixed: FormatNumber() leaks a locale comma into correlation ids - Fixed: Randomize+Rnd() collide within the same clock tick -> switched to FileSystemObject.GetTempName() - Verified real concurrent-logging tradeoffs experimentally (retry-the-open alone made it worse; lock-file mutex is correct but a full-coverage retry budget costs ~330ms latency, so a short budget + accepted best-effort log loss under heavy load is used instead) - Investigated and resolved an inherited IUSR:(F) ACL finding under logs/ (standard NTFS CREATOR OWNER materialization, correctly scoped, not a broad grant) - All M2 SPEC/plan gate items verified PASS on real IIS; see docs/TEST-RESULTS.md and docs/DECISIONS.md		2 weeks ago
Controllers	M0/M1: environment inventory + first vertical slice (Default.asp, Application.wsc, HomeController.wsc, IIS config, tests)	2 weeks ago
Framework	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago
docs	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago
tests	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago
tools	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago
.gitignore	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago
AGENTS.md	Import WSC-MVC agent starter pack (SPEC, AGENTS, IMPLEMENTATION_PLAN, CLAUDE, README)	2 weeks ago
CLAUDE.md	Import WSC-MVC agent starter pack (SPEC, AGENTS, IMPLEMENTATION_PLAN, CLAUDE, README)	2 weeks ago
Default.asp	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago
IMPLEMENTATION_PLAN.md	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago
README.md	Import WSC-MVC agent starter pack (SPEC, AGENTS, IMPLEMENTATION_PLAN, CLAUDE, README)	2 weeks ago
SPEC.md	Import WSC-MVC agent starter pack (SPEC, AGENTS, IMPLEMENTATION_PLAN, CLAUDE, README)	2 weeks ago
web.config	M2: per-request context, central error/outcome logging, three real WSC/VBScript defects fixed	2 weeks ago

README.md

WSC-MVC Agent Starter Pack

This is a planning and agent-control package, not yet an executable framework.

Files

SPEC.md — authoritative product, architectural, security, milestone and acceptance specification.
AGENTS.md — shared instructions for coding agents.
CLAUDE.md — Claude Code entry point; defers to AGENTS.md.
IMPLEMENTATION_PLAN.md — gated execution checklist.

Start a coding agent

Copy these files to the root of the new WSC-MVC repository, then issue:

Read AGENTS.md, SPEC.md, IMPLEMENTATION_PLAN.md. Execute M0 and then the smallest testable piece of M1. Record actual commands/results and do not claim IIS tests passed unless you ran them on Windows IIS.

Choose the Windows/IIS machine as the execution host for M0/M1 wherever possible. A Linux-only agent can prepare text/config but cannot establish Windows COM/IIS behavior.