v1.3.0

[1.3.0] — 2026-08-21

Added

• Hawamesh — notes attached to exact text on a page. Select any text, click the small Hamesh
  mark that appears beside it, and write an ordinary note: the selected words are highlighted in the
  brand accent, and hovering them brings the note back. Selecting text on its own still does nothing
  but select text — the mark is only an offer, and nothing opens until it's clicked. Contextual notes
  are ordinary Hamesh notes throughout: same storage, same viewer, same edit/delete/pin/folders, same
  Notes Library rows (now showing the attached text), same search (which also matches that text), and
  the same Open Note flow, which scrolls to the anchored words and flashes them. Hovering highlighted
  text shows the very same pill a video marker shows — a dot and the note's first line, without the
  timestamp — and the pointer turns into a hand over it; clicking opens the full note.

• Text anchors survive page changes, and refuse to guess. An anchor stores the exact text, the
  words either side of it, its original position, and DOM paths for instant restoration. On a later
  visit Hamesh tries the fast path first, then recovers by context. When it can't tell two candidate
  occurrences apart, it highlights neither: the note keeps its text and simply reports that its
  location couldn't be found this time. Highlights are painted with the CSS Custom Highlight API, so
  nothing on the page is wrapped, moved, or modified.

• Settings → Text notes, with the feature and its automatic selection mark switchable
  independently. Turning either off never touches stored notes or anchors — highlights come straight
  back when it's switched on again. With the mark off, the new Alt+T shortcut (rebindable in
  Chrome's own shortcuts page, alongside Alt+H and Alt+V) creates a contextual note from the current
  selection, and does nothing when there is no valid selection.

• What's New. A page of Hamesh's own history, in English and Arabic, at the foot of the Notes
  Library's sidebar. Every version gets a couple of lines about what changed for you — not the
  developer changelog. Hamesh opens it once, in a background tab, the first time it runs after
  updating itself; a dot marks it in the sidebar until it's read. It never opens itself on a fresh
  install, on a browser update, or on a reload of the same version.

• Local backup. Settings → Backup exports every note and folder to a dated JSON file on your
  own device, and imports one back. Importing never deletes anything: it adds what's missing,
  refreshes anything the file has a newer copy of, and leaves everything else alone — so restoring
  an old backup can't undo newer notes, and importing the same file twice does nothing the second
  time. A file that isn't a Hamesh backup, or one written by a newer version, is refused with a
  reason instead of half-imported. Nothing leaves your device; the file is yours to keep wherever
  you like.

Changed

• Settings rows are now marked with icons. Language, Appearance, both Text notes toggles, and
  each shortcut carry a small glyph before the label — and a shortcut's glyph is the mark of what it
  creates (the margin mark, the play triangle, the text-note lines), so the rows are tellable apart
  at a glance rather than by reading each one. Appearance now shows the same three icon choices in
  the Notes Library's Settings page that the popup's Settings pane already used.

Fixed

• The note actions menu ("⋮") could open and vanish immediately. It closed on any scroll
  outside itself — and clicking the trigger focuses it, which makes the browser scroll whichever
  ancestor it must to reveal it, including the hidden-overflow containers the folder tree's collapse
  animation relies on. Whether the menu stayed open came down to whether that scroll landed before
  or after the panel rendered, so it intermittently looked like clicking "⋮" did nothing. The menu
  now follows its trigger when the page moves instead of closing, and only closes when the trigger
  actually leaves the viewport.

• Hovering a Hamesh mark on a page made it see-through. Markers are drawn as an opaque chip
  precisely so they stay legible over any host content, but the hover state filled them with
  --hm-accent-tint — a token that is opaque in light appearance and a 16%-alpha overlay in dark, so
  in dark appearance hovering dissolved the chip and the page showed straight through it. Hover now
  uses a fill that is opaque in both appearances, and does more than recolor: the hairline turns
  accent and the chip lifts 1px onto a deeper shadow, so it reads as something pressable. Pressing it
  collapses the lift and fills solid.

v1.2.3

[1.2.3] — 2026-08-13

Added

• Video-note markers can align to a custom video player's own timeline. Until now only the
  built-in YouTube integration placed markers on the player's real scrubber; every other site fell
  back to Hamesh's own rail. A site with its own HTML5 player can now opt in — by marking a container
  with data-hamesh-player that holds the <video> and a data-hamesh-timeline element on its
  scrubber, and setting data-hamesh-controls="hidden" while its controls fade — and get the same
  on-timeline placement and controls-synced visibility as YouTube. Matching is strictly opt-in via
  those attributes and never a host allowlist or bare markup, so no site's behavior changes unless it
  adds them.

Fixed

• On a custom HTML5 player with its own scrubber and no native <video controls>, video-note markers
  were drawn on the fallback rail below the video and only appeared while the video was paused or
  directly hovered — such a player fell through to the generic HTML5 adapter, which has no native
  timeline to align to. Players adopting the opt-in convention above now get their markers on the
  timeline itself, shown whenever the player's own controls are.
• Marker visibility didn't keep up with a player whose controls fade via a data attribute: the
  visibility observer watched only the player container's class (YouTube's .ytp-autohide), so a
  player signalling through data-hamesh-controls — whose overlays also sit over the <video>,
  keeping pointer events from reaching it — left its markers out of sync. The observer now watches
  that attribute alongside class.

v1.2.2

Release v1.2.2

What's Changed

• chore(deps): Bump jsdom from 29.1.1 to 30.0.1 by @dependabot[bot] in #47
• chore(deps): Bump @testing-library/jest-dom from 6.9.1 to 7.0.0 by @dependabot[bot] in #48
• chore(deps): Bump postcss from 8.5.18 to 8.5.23 by @dependabot[bot] in #49

Full Changelog: v1.2.1...v1.2.2

v1.2.1

[1.2.1] — 2026-08-01

Fixed

• The note composer and video quick-note textareas weren't actually receiving focus on open, despite having
  autoFocus — typing required clicking into the textarea first. Root cause: their floating card mounts
  visibility: hidden to measure its size before positioning, and React's autoFocus only fires once, on that
  very first (still hidden, so unfocusable) commit. Fixed at the shared positioning hook level so both cards
  focus correctly once actually visible.
• Every website with no cached favicon showed Chrome's own generic gray placeholder image instead of Hamesh's
  intended fallback — Chrome's _favicon endpoint returns that placeholder as a normal HTTP 200, not an error,
  so it could never be distinguished from a real favicon. Now detected by comparing the response bytes against
  a live probe, and replaced with a globe icon in Hamesh's own accent color.
• The Alt+H / Alt+V keyboard shortcuts could silently stop working, regardless of which key combination was
  bound — root-caused to a Chromium reliability gap in chrome.commands.onCommand event delivery to a Manifest
  V3 background service worker. Shortcut handling now lives in a keydown listener in the content script
  itself, which needs no delivery from the background worker at all. The chrome.commands-based path is kept
  as a secondary fallback for pages with no content script.

v1.2.0

[1.2.0] — 2026-08-01

Note actions menu for the Notes Library, plus a round of bug fixes to the 1.1.0 Folders feature, delivered across two PRs.

Added

• Note actions menu — pin/unpin, edit, and delete a note directly from the Notes Library, without opening
  it on its original page. A "⋮" menu on every note row now covers all four actions (the fourth, moving a note
  to a folder, was already there):
  • Available in the domain-grouped ("By site") view, the folder-tree ("By folder") view, and the Pinned
    section — previously only the on-page note viewer could pin, edit, or delete.
  • "Move to folder" stays folder-tree-only; the other two views keep a quicker, flatter action list.
  • The folder-tree menu's "Move to folder" list now marks the note's currently-assigned folder with a
    checkmark, so it's clear at a glance where a note already lives.
  • The menu repositions itself to stay fully on-screen — flips above its trigger when there's no room below,
    and nudges back in bounds horizontally — instead of rendering partly off-screen near a viewport edge.

Fixed

• A folder containing both notes of its own and a sub-folder didn't fully collapse — only the notes hid,
  the sub-folder stayed visible. Same underlying issue also let a collapsed row's own padding show through as
  a thin visible sliver. Both were the same root cause (a CSS grid collapse trick that only fully clips a
  single, padding-less child) and are now fixed for both the folder tree and the domain-grouped view.
• The "Move to…" folder menu could be clipped by the folder tree's own collapse-animation containers.
• Clicking a folder row only worked on the tiny chevron/name, despite the whole row's hover highlight
  suggesting otherwise — the whole row is clickable now.
• Each note now has a visible border for easier at-a-glance separation, and the hairline separators between
  website groups and top-level folders no longer sit flush against their neighbors.
• Patched five dependency vulnerabilities in dev-only build tooling (shell-quote, adm-zip, tmp, uuid,
  esbuild — none shipped in the extension bundle) and a flaky video-notes E2E assertion.

v1.1.0

[1.1.0] — 2026-08-01

Video Notes, Folders, and shortcut/settings improvements, delivered incrementally across nine PRs.

Added

• Video Notes — press Alt+V to leave a note at the current moment in a video (a dedicated
  shortcut, independent of Alt+H — see "Changed" below).
  • A small quick-note popup appears above the video: autofocus textarea, Enter saves,
    Shift+Enter for a newline, Escape cancels — never pauses or otherwise interrupts playback.
  • Saved notes show as small timeline markers. On YouTube, markers align to YouTube's own
    progress bar; on any other HTML5 <video>, Hamesh draws its own marker rail docked to the
    video (native <video controls> render in an internal browser UI Hamesh can't draw on).
  • Markers fade with the surrounding player controls and reappear on hover or while paused, and
    stay out of the way of the player's own hover/click handling.
  • Hovering a marker shows a quick preview (first line of the note + timestamp). Notes close
    together in time cluster into a single marker; clicking a cluster opens a small list to jump
    to any of them.
  • Clicking a marker jumps the video to that moment and opens the note for viewing, editing,
    deleting, or pinning — without affecting playback (a playing video keeps playing, a paused
    one stays paused, and it's never auto-played).
  • Video notes appear in the Notes Library exactly like page notes, with a timestamp badge.
    Opening one from the Library seeks to that moment and opens its viewer, same as clicking its
    on-page marker.
  • Currently supports YouTube (a first-class adapter reading its own timeline UI) and any other
    page with a plain HTML5 <video> element, via a generic adapter. Architecture supports adding
    more site-specific adapters later without touching storage or the rest of the UI.
• Folders — organize notes into user-defined, arbitrarily nested folders in the Notes Library,
  independent of the automatic by-website grouping. A "By site / By folder" switch at the top of
  the list toggles between the two views; search works in either.
  • Any note can be filed into exactly one folder, regardless of which site it came from.
  • File a note into a folder from a "⋮ Move to…" menu on its row, or by dragging it directly
    onto a folder.
  • Create nested sub-folders, rename, and delete a folder — deleting one unfiles its notes (and
    its sub-folders' notes) rather than deleting them.
  • Each note shows a small favicon in folder view, since a folder can mix notes from different
    sites (unlike a website group, which by definition can't).
• Settings moved out of the popup's slide-in pane into a permanent page in the Notes Library
  (Sidebar → Settings), alongside the existing Language/Appearance controls. A new Shortcuts
  section shows the current Alt+H/Alt+V bindings and links to Chrome's own
  chrome://extensions/shortcuts page to change them — the only place Chrome allows a shortcut to
  be rebound. The popup's own Settings pane keeps Language/Appearance for quick access, plus a new
  "Open full settings" link to the rest.

Changed

• Alt+H now always opens element selection; it no longer tries to detect whether you're
  hovering a video first. That earlier "one shortcut, context-aware" heuristic was unreliable on
  real sites — overlay UI on custom video players (play buttons, ad chrome, custom controls)
  defeated the hover detection often enough to cause real confusion between an element note and a
  video note — so video notes now use their own dedicated shortcut, Alt+V, instead.

v1.0.0

[1.0.0] — 2026-07-14

Notes Library: a dedicated page for browsing, finding, and returning to every note across every
site, delivered incrementally across three PRs.

Added

• Notes Library, opened from the popup ("Notes Library →") as a new extension page listing
  every saved note, grouped by website.
  • Each website group shows the site's favicon (read from Chrome's own local favicon cache, no
    network request; falls back to a generated monogram), a note count, and expands/collapses to
    reveal its individual notes.
  • A Continue section surfaces the most recently active pages with notes for quick
    resumption.
  • Search filters notes by content or page (press / to focus the search box, Escape to
    clear it).
  • Sort website groups by most recent activity or alphabetically.
  • Pin a note to keep it at the top of its group, toggled from the note viewer.
  • Clicking a note or Continue card opens its page in a (new or existing) tab and automatically
    scrolls to and highlights the noted element — coordinated with the content script via a
    cross-tab messaging handshake, with no polling and no fixed waits.
  • A first-run empty state, a loading skeleton, and keyboard shortcuts round out the page.
• Foundation for automated Chrome Web Store release submission: architecture decision record,
  API research, a validated docs/chrome-web-store/listing.yaml source of truth for store
  listing copy, and unit-tested release-validation tooling (pnpm release:validate). No
  workflow automates uploads or submissions yet — see docs/releases/CHROME_WEB_STORE_AUTOMATION.md.

Fixed

• The note viewer's pin toggle and close buttons rendered directly on top of the note's own
  text instead of clearing it, making the pin control very easy to miss. The card now reserves
  enough top padding for both corner buttons.
• Anchor resolution's elementFromPoint fallback path is now wrapped in the same defensive
  error handling as every other resolution strategy, preventing a possible uncaught exception in
  edge cases while restoring a note's position.

Security & privacy

• New favicon permission, used only by the Notes Library page to read a website's favicon from
  Chrome's own local favicon cache — no network request is made, and it is never used from the
  content script. See docs/chrome-web-store/PERMISSION_JUSTIFICATIONS.md.

v0.2.0

[0.2.0] — 2026-07-10

Settings for Hamesh: a Settings screen in the popup with functional
language and appearance preferences, delivered incrementally across three
PRs.

Added

• Settings screen in the popup, reachable from a new gear button next to
  the brand header, with a polished RTL-aware horizontal slide transition
  (respects prefers-reduced-motion, manages focus on navigation, closes on
  Escape).
• Language preference: choose English or Arabic from Settings. Persists
  across sessions and applies live — no reload — to the popup and every
  already-open tab, via chrome.storage.onChanged. Users with no saved
  preference keep today's behavior (follow the browser's UI language).
• Appearance preference: Match website (default — the original adaptive
  light/dark behavior, unchanged), Light, or Dark. A forced choice overrides
  the host page across every Hamesh-owned surface (popup, markers,
  composer, viewer); the host page itself is never modified. Persists and
  applies live across every open tab, same mechanism as language.
• Hamesh is now available on the Chrome Web Store; the landing page's
  install CTA links there (manual GitHub-release install is still available
  as a secondary option for developers).

Changed

• detectHostTheme now also walks down single-child DOM chains to find a
  background set on a nested app-shell wrapper element (common in
  SPA-built sites whose <body>/<html> stay transparent), and — while
  "Match website" is active — reacts live to a host page's own dark-mode
  toggle or an asynchronously loaded theme, instead of only detecting once
  at load.

Fixed

• The popup could render narrower than its intended width under Chrome's
  own popup auto-sizing, which can measure the document before the bundled
  stylesheet has applied. The width is now pinned explicitly through every
  layer, including an inline style present on the very first paint.

v0.1.0

0.1.0 — 2026-07-08

First functional MVP of the Hamesh browser extension (Chrome, Manifest V3).

Added

• Contextual notes core flow: activate (toolbar icon or Alt+H) → select a
  page element → write a note → it persists locally → a margin marker restores it
  in context on return, where it can be opened, edited, and deleted.
• Precise selection mode with an accent element outline and cursor hint, over
  any host background, without mutating host-page styles.
• Multi-signal anchoring with deterministic resolution (data-testid → id →
  aria-label → generated selector → text snippet → document position) and graceful
  fallback when the page changes.
• Isolated UI: a single React app mounted in one Shadow DOM root, isolated from
  host-page CSS and reliably layered above host stacking contexts.
• Design system integration: the approved Hamesh identity (margin-mark glyph,
  paper/ink/clay palette, IBM Plex type) as CSS tokens, with light/dark host
  adaptation.
• Bilingual + RTL: English (LTR) and Arabic (RTL) UI driven by the extension
  locale; note content uses dir="auto" for mixed scripts.
• SPA awareness: notes re-evaluate on pushState/replaceState/popstate
  and effective-URL changes.
• Accessibility: keyboard operation, visible focus rings, ARIA roles,
  non-color state cues, and reduced-motion support.
• Bilingual landing page (landing/) using the same identity.
• Tests: unit/integration (Vitest) for domain, storage, i18n, and theme; E2E
  (Playwright) driving the real extension UI through persistence, edit/delete, and
  SPA flows.

Security & privacy

• Local-only: notes live in chrome.storage.local. No backend, accounts,
  analytics, telemetry, or network requests. Least-privilege permissions
  (storage, activeTab); no input/password values are ever read or stored.