| Make school-adapter contribution onboarding actually usable The downstream warehouse docs now guide contributors through an Alpha-to-Beta adaptation path instead of assuming they already understand the repository internals. This also vendors the upstream browser-extension tester into the repo so technical users can start debugging scripts immediately without hunting for external tooling. Constraint: New contributors were getting blocked because the old docs explained repo structure better than the actual adaptation workflow Constraint: Downstream onboarding must stay compatible with upstream warehouse conventions while documenting Qingyu-specific realities Rejected: Link to upstream docs only | still leaves Qingyu-specific bridge behavior and repo workflow unclear Rejected: Keep the tester external-only | increases friction and makes the contribution path feel incomplete Confidence: high Scope-risk: moderate Reversibility: clean Directive: If Qingyu bridge APIs change, update docs/SCRIPT_API.md and tools/CourseImporterTestTool together Tested: Verified docs/tool files exist; validated tools/CourseImporterTestTool/manifest.json parses as JSON Not-tested: Manual browser-extension installation and end-to-end tester execution after vendoring | 6 个月前 |
| Clarify repository boundaries for adapter contributors The repository docs had drifted toward product-style language and blurred the boundary between the adapter resources and the browser workbench. This rewrites the entry-point documentation so contributors can immediately see what is a formal resource surface, what is a browser-side workflow tool, and where final deliverables belong. Constraint: Repository remains an adapter resource warehouse with browser tooling as a workflow aid Rejected: Rewrite the repo as a browser-extension-first product page | misstates repository scope Confidence: high Scope-risk: narrow Reversibility: clean Directive: Keep repository-facing docs declarative; avoid conversational framing in permanent documentation Tested: Manual review of README, CONTRIBUTING, workbench README, and repository map links Not-tested: Remote rendering on GitHub markdown pages | 5 个月前 |
| Turn the adapter extension into a usable workbench Restructure the browser extension around a Side Panel workbench, split AI into a dedicated workspace, improve preview and debug flows, add context export helpers, harden prompt routing, and normalize app-style course payloads so AI-generated scripts do not fail the bridge on missing legacy aliases. This commit also updates the docs to match the new generate/validate/submit flow and reduces the need for manual page-jumping during adapter development. Constraint: Keep the tool dependency-free and compatible with the existing bridge contract Rejected: Keep AI docked in the same scrolling page as the main workbench | caused persistent layout/scroll conflicts Rejected: Rely on prompt wording alone to enforce legacy bridge fields | not reliable enough once app-style payloads enter the repair loop Confidence: medium Scope-risk: broad Reversibility: clean Directive: The bridge still has legacy canonical fields (day/position/weeks); if app-facing schemas evolve further, preserve alias normalization at the bridge boundary Tested: node --check tools/CourseImporterTestTool/popup.js; node --check tools/CourseImporterTestTool/background.js; node --check tools/CourseImporterTestTool/injected_bridge.js; HTML parse checks; manual normalization smoke test in node vm Not-tested: Full browser-side manual smoke test across Chrome/Edge with live school pages | 6 个月前 |
| Turn the adapter extension into a usable workbench Restructure the browser extension around a Side Panel workbench, split AI into a dedicated workspace, improve preview and debug flows, add context export helpers, harden prompt routing, and normalize app-style course payloads so AI-generated scripts do not fail the bridge on missing legacy aliases. This commit also updates the docs to match the new generate/validate/submit flow and reduces the need for manual page-jumping during adapter development. Constraint: Keep the tool dependency-free and compatible with the existing bridge contract Rejected: Keep AI docked in the same scrolling page as the main workbench | caused persistent layout/scroll conflicts Rejected: Rely on prompt wording alone to enforce legacy bridge fields | not reliable enough once app-style payloads enter the repair loop Confidence: medium Scope-risk: broad Reversibility: clean Directive: The bridge still has legacy canonical fields (day/position/weeks); if app-facing schemas evolve further, preserve alias normalization at the bridge boundary Tested: node --check tools/CourseImporterTestTool/popup.js; node --check tools/CourseImporterTestTool/background.js; node --check tools/CourseImporterTestTool/injected_bridge.js; HTML parse checks; manual normalization smoke test in node vm Not-tested: Full browser-side manual smoke test across Chrome/Edge with live school pages | 6 个月前 |
| Turn the adapter extension into a usable workbench Restructure the browser extension around a Side Panel workbench, split AI into a dedicated workspace, improve preview and debug flows, add context export helpers, harden prompt routing, and normalize app-style course payloads so AI-generated scripts do not fail the bridge on missing legacy aliases. This commit also updates the docs to match the new generate/validate/submit flow and reduces the need for manual page-jumping during adapter development. Constraint: Keep the tool dependency-free and compatible with the existing bridge contract Rejected: Keep AI docked in the same scrolling page as the main workbench | caused persistent layout/scroll conflicts Rejected: Rely on prompt wording alone to enforce legacy bridge fields | not reliable enough once app-style payloads enter the repair loop Confidence: medium Scope-risk: broad Reversibility: clean Directive: The bridge still has legacy canonical fields (day/position/weeks); if app-facing schemas evolve further, preserve alias normalization at the bridge boundary Tested: node --check tools/CourseImporterTestTool/popup.js; node --check tools/CourseImporterTestTool/background.js; node --check tools/CourseImporterTestTool/injected_bridge.js; HTML parse checks; manual normalization smoke test in node vm Not-tested: Full browser-side manual smoke test across Chrome/Edge with live school pages | 6 个月前 |
| Turn the adapter extension into a usable workbench Restructure the browser extension around a Side Panel workbench, split AI into a dedicated workspace, improve preview and debug flows, add context export helpers, harden prompt routing, and normalize app-style course payloads so AI-generated scripts do not fail the bridge on missing legacy aliases. This commit also updates the docs to match the new generate/validate/submit flow and reduces the need for manual page-jumping during adapter development. Constraint: Keep the tool dependency-free and compatible with the existing bridge contract Rejected: Keep AI docked in the same scrolling page as the main workbench | caused persistent layout/scroll conflicts Rejected: Rely on prompt wording alone to enforce legacy bridge fields | not reliable enough once app-style payloads enter the repair loop Confidence: medium Scope-risk: broad Reversibility: clean Directive: The bridge still has legacy canonical fields (day/position/weeks); if app-facing schemas evolve further, preserve alias normalization at the bridge boundary Tested: node --check tools/CourseImporterTestTool/popup.js; node --check tools/CourseImporterTestTool/background.js; node --check tools/CourseImporterTestTool/injected_bridge.js; HTML parse checks; manual normalization smoke test in node vm Not-tested: Full browser-side manual smoke test across Chrome/Edge with live school pages | 6 个月前 |
| fix: resolve workspace card overlapping and improve overlay panels - Remove flex:1 from workbench-page to let content size naturally - Fix overlay panel CSS specificity with !important - Convert AI dock and settings to absolute overlay panels - Add workflow step completion tracking - Reduce editor/preview min-heights for better fit in side panel Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> | 5 个月前 |
| fix: resolve workspace card overlapping and improve overlay panels - Remove flex:1 from workbench-page to let content size naturally - Fix overlay panel CSS specificity with !important - Convert AI dock and settings to absolute overlay panels - Add workflow step completion tracking - Reduce editor/preview min-heights for better fit in side panel Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> | 5 个月前 |
| Make school-adapter contribution onboarding actually usable The downstream warehouse docs now guide contributors through an Alpha-to-Beta adaptation path instead of assuming they already understand the repository internals. This also vendors the upstream browser-extension tester into the repo so technical users can start debugging scripts immediately without hunting for external tooling. Constraint: New contributors were getting blocked because the old docs explained repo structure better than the actual adaptation workflow Constraint: Downstream onboarding must stay compatible with upstream warehouse conventions while documenting Qingyu-specific realities Rejected: Link to upstream docs only | still leaves Qingyu-specific bridge behavior and repo workflow unclear Rejected: Keep the tester external-only | increases friction and makes the contribution path feel incomplete Confidence: high Scope-risk: moderate Reversibility: clean Directive: If Qingyu bridge APIs change, update docs/SCRIPT_API.md and tools/CourseImporterTestTool together Tested: Verified docs/tool files exist; validated tools/CourseImporterTestTool/manifest.json parses as JSON Not-tested: Manual browser-extension installation and end-to-end tester execution after vendoring | 6 个月前 |