Feedback Status Update Script

Updated: 2026-03-25

Purpose

Provide an explicit, auditable way to update production feedback item status through the Bizcom admin API.

This script exists because:

• scripts/fetch-feedback.sh is read-only
• nightly feedback hygiene should not rely on vague manual steps
• status write-back must be explicit and reviewable

Script

scripts/update-feedback-status.mjs

Actual path:

• scripts/update-feedback-status.mjs

What it does

1. reads Bizcom admin credentials from the secure workspace file
2. logs into https://bizcom.ph
3. captures the CSRF token from login response
4. sends PATCH /api/admin/feedback/:id
5. prints the updated feedback item JSON

Supported statuses

• new
• acknowledged
• in_progress
• resolved
• dismissed

Usage

node scripts/update-feedback-status.mjs \
  --id <feedback-id> \
  --status in_progress \
  --notes "Tracked in PR #143; merged to staging, pending validation"

Safety rules

• Only update feedback status after verifying GitHub and release state when relevant
• Do not mark resolved without production evidence unless an explicit policy says otherwise
• Prefer dismissed for stale/duplicate/superseded reports rather than leaving them as new
• Record the reason in notes when status meaning may not be obvious later

Recommended nightly usage pattern

1. fetch production feedback
2. verify GitHub state
3. decide status changes
4. apply only the changes that are clearly justified
5. update durable docs with what changed and why

Current limitation

This script performs one update per invocation. That is intentional for now: lower blast radius, easier auditing, simpler failure handling.