Updated Tech Spec Backend Gradebook (markdown)
Add ТЗ structure/template to all 14 Tech Spec pages (backend + design) Each page now has the section skeleton to fill in (purpose, functional requirements, API endpoints, DB structure or screens/wireframes, acceptance criteria) instead of just a title stub. Sections in brackets are prompts, not content - teams still write everything specific to their own module themselves. Backend and Design templates differ (DB/API focus vs screens/API-consumer focus) and both point to the API Contract Guide for the shared 4.1 section.
Add backend/technical Tech Spec pages for each module Getting Started already asked teams to write a full ТЗ (specification.md) covering functional/non-functional requirements, API endpoints and DB schema, but the only per-module wiki pages that existed were the "Tech Spec Design" ones (UI/design side). Added a parallel "Tech-Spec-Backend-<Module>" placeholder page for each of the 7 modules, matching the same minimal one-line style as the existing Design pages (a title, not pre-written content) — the backend team fills it in via their own ТЗ, same as with the design pages.