Pedagogical module hardening v0
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 52m
- Merged PRs (30d)
- 46
Description
## Goal
Consolidate and harden the pedagogical-module prototype after the runnable-pilot milestone, reducing temporary architecture while preserving all validated module, browser, accessibility, privacy, and evidence behavior.
## Scheduling status
Deferred. Milestone #58 and its ordered child sequence are currently authoritative. No child of #33 may be implemented and no PR for this parent may remain active until milestone #58 is completed and the next milestone is selected explicitly.
PR #62 was opened prematurely and closed without merge. Its branch and commits are not authoritative implementation history.
## Planned child increments
- [ ] Consolidate the pedagogical module validator — #34, deferred.
- [ ] Audit validator-regression gaps after consolidation — open only if #34 later identifies a separate reviewable increment.
## Scope when activated
- consolidate the layered validator into one canonical implementation;
- preserve canonical module revisions, stable step IDs, remediation, provenance, declarative layout resolution, procedure modules, semantic primitives, generated HTML checks, and exact error paths;
- replace internal-link false-positive suppression with script-aware validation rather than broad `${...}` filtering;
- migrate builders, tests, evidence tools, documentation, and CI away from `validate_module_v2`;
- restore or add regression coverage only where required to prove unchanged behavior;
- keep documentation, Actions, examples, and traceability aligned.
## Out of scope
- reopening work ahead of the current milestone sequence;
- production backend or multi-user persistence;
- arbitrary graph layout;
- Docker execution labs;
- knowledge-graph implementation;
- browser v2 import/export;
- filesystem publication or overwrite/collision policy;
- changing learner-evidence v1 or migration semantics.
## Implementation traceability
| Child issue | Status | PR / commits | Notes |
| --- | --- | --- | --- |
| Consolidate canonical validator | Deferred | #34 / no active PR | PR #62 closed without merge because milestone #58 is current. |
| Post-consolidation regression increment | Deferred | — | Open only after #34 is eventually activated and merged. |
## Completion criteria when activated
- every child is independently reviewable and linked to this parent;
- one active PR at a time;
- canonical validator behavior and exact paths are proven by tests;
- no runtime, test, documentation, or CI reference to `validate_module_v2` remains;
- learner-evidence and browser contracts remain unchanged;
- finding log complete;
- Actions green;
- two consecutive clean review rounds on each final head;
- parent traceability reflects every merged child before closure.
Contributor guide
No contributing guide indexed for this repository
Research direction
Do not begin until milestone #58 is complete and the next milestone explicitly activates this parent; child issue #34 is the planned entry point. When activated, start by tracing references to validate_module_v2 across builders, tests, evidence tools, documentation, and CI, then verify the canonical validator behavior and unchanged learner-evidence and browser contracts with regression coverage and green Actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, documentation, testing, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100