resources/js/layouts/PhotoLayout.ts (1)

30-46: Minor: align is computed but unused for the "list" branch.

The align variable on line 30 is always computed even when layout is "list", which returns before using it. Consider moving the early return above the align computation to avoid the dead code path, or simply leave as-is since the cost is negligible.

Also, a slightly cleaner way to get element children:

🔧 Optional simplification

 		const align = isLTR() ? "left" : "right";
 
 		// For list view, reset the container height to auto and clear child inline styles
 		if (layoutState.layout === "list") {
 			photoListing.style.height = "auto";
 			// Clear positioning styles from children that were set by other layouts
-			const gridItems = [...photoListing.childNodes].filter((item) => item.nodeType === 1) as HTMLElement[];
-			gridItems.forEach((item) => {
+			photoListing.querySelectorAll<HTMLElement>(":scope > *").forEach((item) => {
 				item.style.position = "";
 				item.style.top = "";
 				item.style.left = "";
 				item.style.right = "";
 				item.style.width = "";
 				item.style.height = "";
 			});
 			return;
 		}

resources/js/components/gallery/albumModule/PhotoListView.vue (1)

26-31: Unused toggleBuyMe emit declaration.

toggleBuyMe is declared in defineEmits but is never emitted anywhere in this component. Either remove it or wire it to a handler from PhotoListItem.

docs/specs/4-architecture/features/014-photo-list-view/plan.md (1)

449-452: Missing trailing hr + last-updated footer.

As per coding guidelines, Markdown files should end with an <hr> line followed by *Last updated: [date]*. The header metadata includes the date, but the footer is also required.

📝 Suggested addition at the end of the file

 4. **Persistence** – Add optional localStorage persistence for layout preference
+
+---
+
+*Last updated: 2026-02-24*

As per coding guidelines: "At the bottom of documentation files, add an hr line followed by 'Last updated: [date of the update]'".

docs/specs/4-architecture/features/014-photo-list-view/spec.md (1)

389-392: Missing trailing hr + last-updated footer.

Same as the plan document — add the required footer per coding guidelines.

📝 Suggested addition at the end of the file

 4. List toggle button should use PrimeVue icons (pi-list) for consistency with album list view
+
+---
+
+*Last updated: 2026-02-24*

As per coding guidelines: "At the bottom of documentation files, add an hr line followed by 'Last updated: [date of the update]'".

resources/js/stores/LayoutState.ts (1)

5-8: Nit: double space in concatenated class strings.

BASE ends with a trailing space and HOVER_STROKE starts with a leading space, producing a double space when concatenated (e.g., "...scale-150 group-hover:stroke-black..."). This is harmless for CSS but slightly messy.

🧹 Optional cleanup

-const BASE = "my-0 w-5 h-5 mr-0 ml-0 transition-all duration-300 group-hover:scale-150 ";
-const HOVER_STROKE = " group-hover:stroke-black dark:group-hover:stroke-white ";
+const BASE = "my-0 w-5 h-5 mr-0 ml-0 transition-all duration-300 group-hover:scale-150";
+const HOVER_STROKE = " group-hover:stroke-black dark:group-hover:stroke-white";

Then adjust the getter concatenation to add spaces where needed:

-			return BASE + HOVER_STROKE + (this.layout === "square" ? "stroke-primary-400" : "stroke-neutral-400");
+			return BASE + HOVER_STROKE + " " + (this.layout === "square" ? "stroke-primary-400" : "stroke-neutral-400");

docs/specs/4-architecture/features/014-photo-list-view/tasks.md (2)

175-182: T-014-20 appears already implemented — mark it [x]?

PhotoListItem.vue already includes aria-label, role="row", and tabindex="0" (lines 8-10 of the component). This task could be checked off, per the guideline to mark tasks as soon as they pass verification.

As per coding guidelines: "Mark each task [x] in the feature's tasks.md as soon as it passes verification. Do not batch task completions."

---

114-136: Test tasks ordered after implementation tasks.

The coding guidelines specify that task checklists should order "tests before code". Currently I7–I9 (test increments) follow I1–I6 (implementation increments). Consider whether re-ordering to place at least the unit test scaffolding/fixture tasks before or alongside their corresponding implementation tasks would better align with the guidelines for future features.

This isn't blocking for this PR since the plan was structured this way, but worth noting for consistency.

As per coding guidelines: "Maintain a per-feature tasks checklist… that mirrors the plan, orders tests before code."

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro