You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Added a daily GitHub Actions workflow that proposes dated public verification
updates in a pull request for explicit maintainer approval.
Added a manual known-issue mode that can propose a yellow popup status for
selected supported controls without exposing raw reports in the extension.
Added report and work-in-progress status modes, a single refreshable daily
verification PR, and automatic protection against scheduled green updates
overwriting a yellow live status.
Added GitHub Actions CI for the root extension package. The workflow installs
dependencies with npm ci, runs npm test, validates extension package
metadata, and verifies generated dist/ bundles are committed.
Added workflow linting, site build checks, high-severity npm audit gates, and
Dependabot version-update automation for GitHub Actions, extension
dependencies, and website dependencies.
Added RELEASE_CHECKLIST.md to make version synchronization, automated tests,
manual Meta-platform smoke tests, Chrome Web Store packaging, privacy review,
and post-release steps explicit.
Added ARCHITECTURE.md documenting the Manifest V3 runtime model, build flow,
settings/config flow, blocking strategy, platform modules, tests, and
platform-change risks.
Added docs/QA_FIXTURES.md with stable smoke-test IDs and evidence statuses
for high-risk fixes and releases.
Added manifest permission and host-permission drift validation to the
extension package checks.
Added release ZIP dry-run tooling that verifies the Chrome Web Store package
shape and writes a SHA-256 checksum.
Added secret scanning configuration for CI and optional local pre-commit use.
Added this changelog so future release notes are kept in the repository before
they are copied to Chrome Web Store and GitHub Releases.
Added ignore rules for local-only notes and temporary release/test artifacts
so they are not accidentally included in release changes.
Added public Verification Status pages at /status and /status/history,
plus a display-only /status.json feed for compact public status summaries.
Added a popup Public Verification summary link to the Status page.
Added public verification guardrails for reviewed proof, redacted screenshots,
opt-in credit, and automation that can flag or downgrade but cannot mark a
live feature verified.
Changed
Restored the popup to the focused privacy-control layout by removing Labs and
the feature survey.
Simplified popup status to the latest dated status record: green for working,
or yellow for reports, confirmed issues, and review states.
Made the latest merged status authoritative indefinitely and consolidated the
website and popup feed onto one canonical committed JSON source.
Added the exact website host permission required for the popup's status fetch
and kept green verification blocked until the published Store build matches.
Redesigned the popup with a low-glare dark palette, clearer control grouping,
calmer active states, and improved text and icon contrast.
Removed the outdated Facebook Hide Seen information tooltip so the control
remains focused and uncluttered.
Added a delayed status-pill description sourced from the latest public status
title, without repeating the compact verification date.
Updated the extension version to 2.0.4 across package metadata,
Manifest V3 metadata, bundled privacy patterns, and generated scripts.
Changed the popup trust surface so public Verification is the only
persistent trust row, while local refresh guidance appears only when a
supported tab needs reload.
Simplified the popup Labs vote list, aligned control label weight, and
kept the Release 1 survey choices focused on non-content-retention ideas.
Aligned README, website, privacy, and feedback-form copy around local
request/payload inspection and optional external feedback forms.
Documented the popup's display-only public status feed and clarified that it
does not send messages, tab URLs, settings, or social media activity to
Ghostify.
Clarified the privacy-policy justification for the local declarativeNetRequest permission.
Updated the website Compatibility section, footer, and FAQ to point users to
public verification status without putting Status in the hero.
Fixed
Added platform-specific popup status checks so Instagram, Messenger, and
Facebook readiness no longer passes on core hooks alone.
Replaced unsupported issue-form upload fields with safe screenshot/video
guidance.
Verification
Automated: run npm test, npm run validate:extension, root/site
high-severity audits, site build, and npm run package:extension before
release.
Manual: complete the Instagram, Messenger, and Facebook smoke matrix in RELEASE_CHECKLIST.md before Chrome Web Store upload.
Credits
Public user credits must only be added when the user explicitly gave
permission.