docs(rfc): WS-FRONTEND-PRIMEVUE planning — F1 audit, RFC v1.0, Amendment A-1, sync conf expansion #20
Reference in New Issue
Block a user
Delete Branch "audit/primevue-migration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Planning artifacts for the WS-FRONTEND-PRIMEVUE migration sprint. No application code changes; documentation and tooling configuration only.
What's in
5d9399b) —dev-docs/MIGRATION-AUDIT-PRIMEVUE.md, exhaustive Vuetify+Vuexy inventory, datatable mapping, bundle baseline, form layer surface areae2d9797) —dev-docs/RFC-WS-FRONTEND-PRIMEVUE.md, full migration plan with sub-packages F2-F6, AD-1 through AD-12, FormField API in Appendix A0d4afcd) — TEST-INFRA-001 inserted before F2, F5 dual-tier scope, R-11 risk, DoD-16 through DoD-20. Trigger: empirical lessons from timetable-stabilization253f8a3) —.claude-sync.conf22 → 33 entries, closes the post-commit hook gap discovered during the amendment commitWhat this enables
After merge,
chore/test-infra-001can be reviewed against an updated main. F2 work begins afterchore/test-infra-001merges.No application code
Pure planning + tooling. No risk of regression in features. CI status unchanged (no CI exists yet — see TEST-INFRA-002 in BACKLOG).
🤖 Generated with Claude Code