Repository navigation
curriculum(APP19): competency-derived TypeScript types and validated API evidence - #167
Merged
christophersesugh merged 2 commits intoNov 18, 2026
Merged
Conversation
… type/runtime evidence Signed-off-by: Christopher S. Aondona <christohybrid185@gmail.com>
christophersesugh
force-pushed
the
curriculum/app19-competency-first-reassessment
branch
from
November 18, 2026 13:13
d78af02 to
f9a81b4
Compare
Signed-off-by: Christopher S. Aondona <christohybrid185@gmail.com>
christophersesugh
force-pushed
the
curriculum/app19-competency-first-reassessment
branch
from
November 18, 2026 13:25
6d29aa8 to
cb0762b
Compare
christophersesugh
deleted the
curriculum/app19-competency-first-reassessment
branch
November 18, 2026 13:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
M3 / APP19 — competency-first academic reassessment
1. Baseline, authority and scope
mainat9ddddcc642fb373437004366def519d7a5fbfb2c, with APP1 #161, APP17 #163 and APP18 #165 merged. Branch:curriculum/app19-competency-first-reassessment. Curriculum source changed:curriculum/APP/APP19.md. CI regression repair also changes:tests/test_app_catalog.py(only the two APP19 malformed-Markdown negative tests; no normative/content change).course,core,v0.2.0draft,APP18direct prerequisite, 12 modules, 82 numbered lesson entries, 12 required outcomes, five required assessments, provisional 10–14 weeks/10–14 focused hours/week.2. Independent TypeScript exit competence and sources
Authentic exit performance: A learner who already writes and tests JavaScript (APP18) can predict structural type checking, represent absent/variant states, diagnose unsound assertions and incompatible consumers, design relational generic APIs with proportionate type transformations, maintain a strict and reproducible compiler/module boundary, validate untrusted runtime payloads, evolve an existing JavaScript module and independently defend a bounded typed library under unexpected change. The goal is testable TypeScript engineering, not maximum language-syntax coverage or an exercise per type feature.
Evidence informing the course boundary:
neverfor exhaustiveness; the learner must respond when an unseen variant is introduced.tsconfig.json, and does not implement all TypeScript transformations,pathsor module resolution for the developer.Prerequisite and specialization ownership: APP18 owns JavaScript behavior, promises, ES modules, local Node tooling and tests. APP19 owns static TypeScript modeling, compiler checking, public declaration and consumer contracts, incremental migration and type/runtime distinction. APP2 consumes this for browser APIs; APP20 adds React; APP21 handles the Node/V8/libuv/OS/service runtime; APP3 adds backend frameworks; elective APP15 adds TypeScript–Rust FFI. No DOM, server, React, Rust, remote package registry or private vendor becomes a hidden core requirement.
3. Outcome-by-outcome disposition and coverage challenges
Retain APP19-O1–O12 without rewriting their stable meaning or silently changing old completion decisions:
tscstatic checking, compiler diagnostics versus emitted/runtime JavaScript, Node-native type stripping limits and local reproducibility.neverexhaustion, assertion/predicate unsoundness,unknownand type holes.Identified evidence gap: Existing O8 explicitly says utility, mapped, conditional and template-literal types, but prior AS3 only asked for “a justified utility/mapped/conditional type”: this could pass without testing a template-literal relationship, and without demonstrating the difference between a mapped type and a canned utility type. Revised AS3 requires bounded, compiler-verifiable examples of each family; a small isolated consumer is acceptable where publishing the more complex type would damage the API. The examiner also judges when the public API should choose simpler types. O8 is not a license to make a gimmicky type-language course.
4. Module-by-module decisions and revised lesson intent
tsc/host/module/declaration workflow. Eliminate repeated type-only import, module-resolution, declaration, JavaScript interop and package-consumer treatments across two modules; retain meaningful strictness, emission, native stripping limitations and independently tested APIsActual new distribution: M1 4, M2 6, M3 5, M4 6, M5 5, M6 8, M7 8, M8 6, M9 5, M10 5 — not equal or quota-derived. The M6 and M7 modules are longer because the mechanisms and feedback are linked; splitting them again for equal counts would recreate the original problem. Each described lesson has a primary capability and an observation, counterexample or engineering task.
5. Outcome → required assessment → evidence review
Retain
APP19-AS1–APP19-AS5, all explicit public Work/Criteria/Evidence, each with different decisions:tscdiagnostics.unknowninput, report malformed/versioned data, add a new discriminant, force exhaustive consumer rework and verify adverse cases. No fake automatic runtime type guard.keyof/indexed access; distinct utility/mapped, conditional and template-literal checked examples with meaningful use or explicit exclusion from public API; two independent valid/invalid consumers, actual callback/async behavior and proportionality judgment.tsconfig; showtscstatic check and a separate live executable path (actual JS emission or appropriately supported native erasable syntax). Seed and resolve module/config/type-import failure; verify old runtime regression cases offline.Bidirectional checks: Every retained outcome is named in summative definitions; the AS3 O8 criteria now genuinely require distinct type-family evidence; the other assessment ID mappings were preserved. These criteria allow written/recorded/accessible defenses and offline local tools; they reject unfounded claims that successful
tsc,.d.ts, or Node stripping validates untrusted records. No hidden mandatory course labs or five copies of the same library.6. Cross-program effects, workload and migration
7. Findings (locator, consequence, severity, disposition)
tsc --noEmit, compiler-emitted JS,tsconfig, ambient declaration vs real runtime API and true module-resolution behavior; avoid false safety claims.drafttotested/verifiedfrom editorial checks.8. Verification completed and not completed
main: initial curriculum commit: one modified course file; after CI repair: exactly two changed files,curriculum/APP/APP19.mdandtests/test_app_catalog.py. The latter changes only broken test-fixture lookup, not curriculum requirements.OutcomesandLessonssections; all 58 individual lessons correctly numbered within each module; all twelve unique declared outcome IDs; five stable required assessment IDs;Outcomes/Work/Criteria/Evidencefor each required assessment; every outcome appears in required assessments; required top-level sections remain intact. Cross-checked existing APP19 catalog tests and repository outcome checker for no APP19-specific fixed lesson/module quota.f9a81b4):validate-app, markdownlint, inventory, internal/public links, and DCO passed. Theoutcome-curriculumworkflow executed 263 tests: two failed intests/test_app_catalog.pybefore the curriculum validator step, because test mutations assumed obsolete exact APP19-AS4 prose. After commit6d29aa8, those same tests locate the stableAPP19-AS4summary row and inject malformed backtick/pipe states irrespective of editorial wording; checks on the updated head are pending/re-running. The new repair commit needs the maintainer's DCO sign-off. Not executed locally: full Python suite, local TypeScript/Node experiments, independent learner evaluation. Do not imply academic conformance, verified readiness or CI success while checks are unfinished.9. Decision and next course
Submit for maintainer academic review and repository CI. Merge only with maintainer approval; do not merge/delete this branch or merge temporary protocol PR #150 as part of this course work. Next APP M3 course in prerequisite-valid sequence after APP19 is merged: APP4 — Databases & Data Modeling, then APP2, APP21 and subsequent core courses per #152.
Branch:
curriculum/app19-competency-first-reassessment. Base:main.CI correction after initial review (2026-11-18)
f9a81b4ran 263 unit tests and failed exactly two tests:test_app19_assessment_summary_table_rejects_unclosed_codeandtest_app19_assessment_summary_table_rejects_truncated_row. Both used hardcoded strings from the former APP19-AS4 evidence summary, so they raised before invoking the malformed-Markdown validator after the new curriculum text was authored. No content-only APP19 validation failure was reported by that run.6d29aa8updates only those two negative tests. They identify the real APP19-AS4 table row by stable assessment ID, remove a closing inline-code backtick in one mutation, and remove its final pipe separator in the other; both assert that the validator reports its expected malformed-row diagnosis. The original 4→3 pipe and even→odd backtick mutations were independently checked before pushing; the rest of the test suite is unchanged.