Skip to content

chore: back-merge main after v0.3.0 release#48

Closed
fvadicamo wants to merge 1 commit into
developfrom
chore/backmerge-v030
Closed

chore: back-merge main after v0.3.0 release#48
fvadicamo wants to merge 1 commit into
developfrom
chore/backmerge-v030

Conversation

@fvadicamo

Copy link
Copy Markdown
Contributor

Back-merge main into develop after release merge (PR #44). Keeps histories in sync per branching convention.

- Optional enrollment mode for LMS integrations (FEAT-003)
- Widget UX: collapsible sources, a11y, i18n, snippet fix
- Phase 2 stabilization: BUG-010, BUG-011, DEBT-002/003/008
- Sync main history, 3 critical bug fixes from v0.2.0 review
- Version 0.3.0, CHANGELOG, docs update (18 new config vars, ERR-LEARN codes)
- Commit signing guide, quality gate, branching rules in CONTRIBUTING

Reviews: PRs #42-#47, 30+ comments addressed (CodeRabbit, Gemini)
Tests: 576 passed, integration + NFR gates green
Refs: FEAT-003, BUG-010, BUG-011, DEBT-002, DEBT-003, DEBT-008
@fvadicamo fvadicamo added this to the v0.3.0 milestone Mar 22, 2026
@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@fvadicamo

Copy link
Copy Markdown
Contributor Author

Not needed: develop is already an ancestor of main after the release merge. No divergence to sync.

@fvadicamo fvadicamo closed this Mar 22, 2026
@fvadicamo fvadicamo deleted the chore/backmerge-v030 branch March 22, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant