@alliance-droid/status-feedback-system 4.3.2 → 4.3.3

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 4.3.3
+
+### Changed
+
+- Feedback rows now keep the consuming app's standard border color for authorized Admins and ProductOwners. Editable status controls remain purple.
+- The **Needs your input** cue remains visible when action is required; the redundant **You can change this status** cue has been removed.
+
 ## 4.3.2
 
 ### Added

package/README.md

@@ -330,7 +330,7 @@ Categories are fixed by the system (**Bug**, **Feature Request**) — `categoryC
 
 When you pass `getAuthToken`, **Admins and ProductOwners of the app configured for the feedback project** can accept feedback, sign off **QA / UAT → Ready for Production**, reopen it, or decline it (Won't do, Duplicate, Can't reproduce), where the current status permits the decision. No feedback-admin login or per-user assignment is needed. Reopens and declines require a reason. **Only acceptance starts automation**; engineering, release, and completion transitions remain in the admin app.
 
-Editable items have **purple status controls and row accents**, accompanied by a text cue. The sidebar's **Needs my input** filter shows Open, Considering, Waiting on reply, and QA / UAT, filtered on the server across all pages. Everyone continues to see each item's granular status.
+Editable items have **purple status controls**, while rows keep the consuming app's normal border color. A **Needs your input** cue appears only when a manager's action is required. The sidebar's **Needs my input** filter shows Open, Considering, Waiting on reply, and QA / UAT, filtered on the server across all pages. Everyone continues to see each item's granular status.
 
 Deploy the matching admin-server capabilities update first. The packaged proxy forwards the optional board bearer token; custom proxies must also forward `Authorization` on board reads and preserve `status=needs_input`. Custom lists can use the backend's per-item `canChangeStatus` and `needsInput` fields with `board.canManageStatus`.
 

package/dist/components/board/FeedbackItem.svelte

@@ -20,7 +20,6 @@
 
 <!-- svelte-ignore a11y_no_noninteractive_tabindex -->
 <article
-	class:sf-editable={canChangeStatus}
 	class="rounded-xl border border-border bg-surface p-4 transition-all {isClickable ? 'cursor-pointer hover:border-border-strong hover:bg-surface-hover' : ''}"
 	role={isClickable ? 'button' : undefined}
 	tabindex={isClickable ? 0 : undefined}
@@ -79,10 +78,8 @@
 			</div>
 
 			<!-- Meta -->
-			{#if canChangeStatus}
-				<p class="sf-action-hint">
-					{item.needsInput ? 'Needs your input' : 'You can change this status'}
-				</p>
+			{#if canChangeStatus && item.needsInput}
+				<p class="sf-action-hint">Needs your input</p>
 			{/if}
 			<div class="mt-3 flex items-center gap-3 text-xs text-foreground-tertiary">
 				{#if item.email}
@@ -112,10 +109,6 @@
 </article>
 
 <style>
-	.sf-editable {
-		border-color: #a78bfa;
-		border-inline-start: 4px solid #8b5cf6;
-	}
 	.sf-action-hint {
 		color: #6d28d9;
 		background: #f3e8ff;

package/dist/components/board/FeedbackSidebar.svelte

@@ -63,7 +63,7 @@
 
 	<div class="sf-filter-group">
 		{#if board.canManageStatus}
-			<p class="sf-editable-legend"><span aria-hidden="true"></span>Purple marks statuses you can change.</p>
+			<p class="sf-editable-legend"><span aria-hidden="true"></span>Purple status controls mark statuses you can change.</p>
 		{/if}
 		<Select
 			label="Status"

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@alliance-droid/status-feedback-system",
-	"version": "4.3.2",
+	"version": "4.3.3",
 	"type": "module",
 	"description": "Drop-in system status pages and user feedback forms for SvelteKit apps",
 	"svelte": "./dist/index.js",