From 3e233b0df6237d0535823f4b279209bde48df293 Mon Sep 17 00:00:00 2001 From: Mike Kell Date: Sat, 11 Apr 2026 11:15:37 -0400 Subject: [PATCH] Master Development Brief updated after Stage 1A merge --- docs/development/master_development_brief.md | 47 ++++++-------------- 1 file changed, 13 insertions(+), 34 deletions(-) diff --git a/docs/development/master_development_brief.md b/docs/development/master_development_brief.md index 0184def..ae4aad4 100644 --- a/docs/development/master_development_brief.md +++ b/docs/development/master_development_brief.md @@ -77,20 +77,28 @@ Rules: - Price-only product edit landed. - Search/filter/sort refinement landed. - Name-only product edit landed. +- ✅ Description-only product edit landed (Stage 1A complete — merged `feat/description-only-edit` → `main` at `cebac4c`, 2026-04-11). ### Current narrow edit capabilities on `main` - update product status through controlled workflow - update product price only - update product name only +- update product description only ### Latest known validation state on `main` - `flutter analyze` clean - `feature_wordpress` tests passing - `kell_web` dashboard tests passing -- latest reported count for `feature_wordpress`: `195/195 passed` +- latest reported count for `feature_wordpress`: `212/212 passed` - latest reported count for `kell_web` dashboard tests: `10/10 passed` +- baseline commit: `cebac4c` (2026-04-11) + +### Next recommended branch + +**`feat/category-only-edit`** — Stage 1B: Category-only product edit. +Branch from `main` at `cebac4c`. Follow the same narrow single-field edit pattern established by price, name, and description edits. --- @@ -126,41 +134,12 @@ Use one branch per edit slice: - `feat/description-only-edit` - `feat/category-only-edit` -#### Stage 1A — Description-only product edit +#### ~~Stage 1A — Description-only product edit~~ ✅ COMPLETE -##### Goal +> Merged `feat/description-only-edit` → `main` at `cebac4c` (2026-04-11). +> All artifacts delivered: repository contract, fake/WP repo implementations, use case, controller action/result handling, preview panel inline description edit UI, and targeted tests (212 total `feature_wordpress` tests passing). -Allow updating product description only. - -##### Requirements - -- Inspect the existing price-only and name-only edit implementations first. -- Mirror the narrow pattern for description update. -- Add one repository method or equivalent narrow path only if needed. -- Fake and WP repositories evolve in parallel. -- Use existing controller result/feedback patterns. -- Keep WooCommerce payload logic in WP repo only. -- Do not expose any other editable fields. -- Keep description editing plain and controlled. -- Do not add a rich text editor. - -##### Expected artifacts - -- repository contract update -- fake repo implementation -- WP repo implementation -- use case -- controller action/result handling -- preview panel inline description edit UI -- targeted repo/controller/widget tests - -##### Definition of done - -- product description updates end-to-end in FAKE and WP modes -- no generic update API introduced -- tests/analyze clean - -#### Stage 1B — Category-only product edit +#### Stage 1B — Category-only product edit ← **NEXT** ##### Goal