B2BEA.org Rebuild build-execution S-49

• Moved course module challenge feedback behavior from src/courses/modules/challenge-feedback.njk into /assets/js/course-module-feedback-runtime.js.
• Left the feedback template as markup with legacy inline style attributes and a deferred governed runtime asset.
• Registered /assets/js/course-module-feedback-runtime.js in CSS governance legacy inline-style allowlist because it preserves the existing coaching paragraph style string.
• Added focused course runtime governance coverage for the feedback page.

• Red test first: node --test test/courseRuntime.test.js failed on missing /assets/js/course-module-feedback-runtime.js.
• node --check src/assets/js/course-module-feedback-runtime.js: passed
• node --test test/courseRuntime.test.js: 5/5 passed
• node scripts/audit-css-governance.js: initially failed on migrated legacy inline style string, then passed after allowlist registration
• git diff --check: passed
• npm test: 113/113 passed
• npm run build: Eleventy copied 121 assets and wrote 126 files
• GitHub Actions build: passed in 24s
• Cloudflare Pages: passed

feature/b2bea-slice-49-module-feedback-runtime

https://github.com/b2bea-org/b2bea-website/pull/84

Start Slice 50 from origin/main; rescan remaining inline runtimes and continue with podcast page runtime, OroCommerce vendor page runtime, resource landing config scripts, or the larger vendor portal runtime.

• Moved course module challenge feedback behavior from src/courses/modules/challenge-feedback.njk into /assets/js/course-module-feedback-runtime.js.
• Left the feedback template as markup with legacy inline style attributes and a deferred governed runtime asset.
• Registered /assets/js/course-module-feedback-runtime.js in CSS governance legacy inline-style allowlist because it preserves the existing coaching paragraph style string.
• Added focused course runtime governance coverage for the feedback page.

Start Slice 50 from origin/main; rescan remaining inline runtimes and continue with podcast page runtime, OroCommerce vendor page runtime, resource landing config scripts, or the larger vendor portal runtime.

Machine-readable source fields