Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/portal/README.md`:
- Line 25: The README entry describing how to open the share modal is
inconsistent: update the route fragment documented alongside data-portal="share"
to match the PR objective by replacing `#/portal/share` with `#/share` (so the
docs show Share modal can be opened with `data-portal="share"` (or `#/share`));
ensure both the inline fragment text and any other references in the same file
that mention `#/portal/share` are changed to `#/share`.

In `@apps/portal/src/app.js`:
- Around line 953-956: The share route mapping returning {page: 'share'} is
never reached because fetchLinkData's linkRegex only matches hashes like
/portal/..., so hashes like "#/share" bypass it; update fetchLinkData to
recognize the "#/share" fragment (either by expanding linkRegex to include
^#\/share(?:\/|$) or adding an explicit check for hash.startsWith('#/share')) so
that when the hash is "#/share" it returns the same path === 'share' result and
triggers the modal; refer to fetchLinkData and linkRegex as the places to change
and ensure the code path that builds {page: 'share'} is returned for "#/share".

In `@apps/portal/test/unit/components/pages/share-modal.test.js`:
- Around line 95-100: The test assertions in the ShareModal unit test check
button order incorrectly; update the expectations that read the actions array
(from container.querySelector('.gh-portal-share-actions').children) so they
assert the actual DOM order: actions[0] = 'copy', actions[1] = 'email',
actions[2] = 'twitter', actions[3] = 'facebook', actions[4] =
'gh-portal-share-more' (adjust the expect(...).toHaveClass calls accordingly in
the share-modal.test.js test that references the actions array).

In `@ghost/i18n/locales/de-CH/portal.json`:
- Around line 58-59: The de-CH locale file has empty translations for the new
share-modal keys (e.g., "Copied" and "Copy link" in portal.json and the other
empty entries noted); populate each empty string with the correct Swiss German
translations (or explicit passthrough if they are brand names) so the UI doesn’t
fallback to source strings—update the keys "Copied", "Copy link" and the other
empty keys mentioned (lines referenced in the review) with appropriate localized
text, preserving the JSON key names and punctuation.

In `@ghost/i18n/locales/en/portal.json`:
- Line 33: Add the missing translation keys "Bluesky" and "More options" to
every locale's portal.json and to the shared context.json metadata so
translations and fallback behavior remain consistent; for each locale file add
the same key names (use the English strings or empty "" placeholders as
appropriate) and in context.json add corresponding entries for "Bluesky" and
"More options" so tools that read context/metadata can detect them.

In `@ghost/i18n/locales/hu/portal.json`:
- Around line 58-59: Add Hungarian translations for the actionable UI strings in
the portal.json locale: set "Copied" to "Másolva", "Copy link" to "Link
másolása", and "Share" to "Megosztás"; ensure you update both occurrences
referenced in the file (the keys "Copied", "Copy link", and "Share") so the
user-facing copy is consistently localized across the portal.

In `@ghost/i18n/locales/nn/portal.json`:
- Around line 58-59: The nn locale file has empty values for several UI strings
causing fallback to keys; update portal.json by supplying Norwegian Nynorsk
translations for the keys "Copied", "Copy link", "Facebook", "LinkedIn",
"Share", "Threads", and "X (Twitter)" (the exact entries shown in the diff) so
they are not empty, or explicitly mark/annotate them as intentional placeholders
before merging; ensure you edit the nn/portal.json entries for those keys to
contain the correct Nynorsk strings.

In `@ghost/i18n/locales/sl/portal.json`:
- Around line 58-59: Add the missing "Bluesky" translation key to the Slovenian
portal locale so t('Bluesky') used by ShareModal resolves; update the JSON in
sl/portal.json to include the entry "Bluesky": "" alongside the existing social
platform keys (e.g., "Facebook", "LinkedIn", "Threads", "X (Twitter)") so the
ShareModal component in apps/portal/src/components/pages/share-modal.js finds
the key.

In `@ghost/i18n/locales/sr-Cyrl/portal.json`:
- Around line 58-59: Fill in Serbian Cyrillic translations for the empty generic
UI action keys in ghost/i18n/locales/sr-Cyrl/portal.json — specifically provide
proper SR-Cyrl values for "Copied" and "Copy link" and for the other empty
entries referenced (the empty generic action keys around the same modal at the
other noted locations). Update those JSON values with concise Serbian-Cyrillic
strings (keeping brand names unchanged if present) so the new Share modal does
not display mixed-language UI.

---

Nitpick comments:
In `@ghost/i18n/locales/ca/portal.json`:
- Around line 58-59: The new share-related keys in the Catalan locale ("Copied"
and "Copy link" and the other empty share labels present in portal.json) are
empty and must be populated; update the translation strings for the keys
"Copied", "Copy link" (and any other blank share-related keys referenced in the
file) with correct Catalan equivalents so the share modal displays localized
text instead of falling back to the default language, keeping the key names
unchanged.

In `@ghost/i18n/locales/context.json`:
- Around line 70-71: The i18n context entries for the share labels are blank;
add concise translator context strings for the keys "Copied" and "Copy link"
(and the other identical keys elsewhere) so translators understand intent and
tone — e.g., indicate whether "Copied" is a confirmation message shown after
copying a link and whether "Copy link" is a button/action label; update the
context.json entries for the "Copied" and "Copy link" keys (and matching keys
found in the same file) with those brief explanatory notes.

In `@ghost/i18n/locales/he/portal.json`:
- Around line 58-59: Several new share-related locale keys (e.g., "Copied" and
"Copy link") were added with empty values; replace those empty strings with
explicit non-empty Hebrew defaults (or clear English placeholders if Hebrew
translations are not ready) for "Copied", "Copy link" and the other newly added
share-related locale keys in this locale file so the UI never falls back to a
blank label; keep the same quoting/JSON style as surrounding entries and follow
existing translation conventions when providing the values.

In `@ghost/i18n/locales/zh-Hant/portal.json`:
- Around line 58-59: Replace the empty strings for the user-facing share/action
keys (e.g., "Copied", "Copy link" and the other modal action keys referenced in
the review) with proper Traditional Chinese (zh-Hant) translations so the
localized UI doesn't show blank or English labels; update the values for the
keys "Copied" and "Copy link" (and the other empty action keys at the locations
noted) with suitable zh-Hant strings that match the tone of the portal UI.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/portal/src/components/pages/share-modal.js`:
- Around line 383-385: getShareUrl currently falls back to window.location.href
which may include hash fragments like "#/share" and leak modal routing state;
update getShareUrl so when getCanonicalUrl() is falsy it returns the current
location without any hash fragment (i.e., strip everything from the first '#' in
window.location.href or use the URL API to construct a href that omits
location.hash) before returning the fallback; keep references to getShareUrl and
getCanonicalUrl so the change is applied in that function.
- Around line 324-326: The metadata helpers in ShareModal (e.g.,
getCanonicalUrl) are querying the iframe's empty document; change them to read
from the host page by using window.parent for DOM and location access (e.g.,
replace document.querySelector(...) with
window.parent.document.querySelector(...) and window.location.href fallback with
window.parent.location.href) and update all metadata getter functions and their
usages (the functions around getCanonicalUrl and where their results are used
around lines 446-453) to use window.parent so the canonical URL, title,
description and image come from the parent page.

In `@ghost/i18n/locales/cs/portal.json`:
- Line 33: The JSON entries for new share labels are left empty (e.g., the
"Bluesky" key in portal.json) so Czech users get fallback source strings; open
ghost/i18n/locales/cs/portal.json and fill each empty string value (including
"Bluesky" and the other empty share-label keys reported) with proper Czech
translations, preserving the exact JSON keys and punctuation, escaping any
special characters, and keeping trailing commas/format consistent; after
updating, run the project's i18n/JSON linter or formatter to ensure valid JSON
and that keys remain unchanged.

In `@ghost/i18n/locales/es/portal.json`:
- Around line 59-60: The Spanish locale file is missing translations for share
action keys causing English fallbacks: add appropriate Spanish strings for the
keys "Copied" and "Copy link" (present at the shown lines) and for the other
empty keys at lines 137 and 178 (the other share/action strings in portal.json)
by updating ghost/i18n/locales/es/portal.json so each empty value is replaced
with the correct Spanish translation, preserving the exact JSON key names and
surrounding punctuation.

In `@ghost/i18n/locales/fa/portal.json`:
- Around line 59-60: The Persian locale file is missing translations for UI
action labels; update the JSON entries for the keys "Copied" and "Copy link"
(and the other empty keys referenced at the same locations) with proper Persian
strings so they don't fall back to the default locale; edit the values for
"Copied", "Copy link" (and the empty keys at the other referenced positions) to
use correct Persian translations, preserve surrounding punctuation/quote
structure and valid JSON formatting, and run a quick lint/parse to ensure no
trailing commas or syntax errors.

In `@ghost/i18n/locales/fr/portal.json`:
- Line 33: Populate the missing French translations for the newly added Share
modal labels by replacing the empty string values for the listed keys (e.g.
"Bluesky" and the other empty entries at the same locations) with appropriate
French text; edit the fr/portal.json entries for "Bluesky" and the other empty
share-related keys referenced in the comment so they contain proper French
labels (ensure wording matches existing portal terminology and pluralization/
casing used elsewhere), then run a quick UI check to confirm there are no
fallback English strings in the Share modal.

In `@ghost/i18n/locales/gd/portal.json`:
- Around line 59-60: The Gaelic (gd) locale file has empty UI strings for the
share actions — fill the empty values for the keys "Copied" and "Copy link" (and
the other empty keys at the indicated spots around lines 137 and 178) with
proper Gaelic translations, or if translation is not available, explicitly
annotate those keys as pending (e.g., add a clear "TODO: translate" comment or
placeholder value) so the missing translations are tracked; update the values
for the keys "Copied", "Copy link" and the other empty keys referenced to either
their correct Gaelic strings or a standardized pending-locale marker.

In `@ghost/i18n/locales/is/portal.json`:
- Around line 59-60: Translate the empty user-facing action labels in the
Icelandic locale by providing Icelandic strings for the keys shown (e.g.,
"Copied" and "Copy link") and for the other empty entries referenced at lines
137 and 178; update the JSON values for those keys in portal.json (use
appropriate Icelandic phrases such as “Afritað” for "Copied" and “Afrita tengil”
for "Copy link") so the locale no longer falls back to the default language.

In `@ghost/i18n/locales/it/portal.json`:
- Around line 59-60: Fill the empty Italian translation values for the share
action labels: set "Copied" to "Copiato" and "Copy link" to "Copia link", and
also complete the other two empty entries mentioned (the keys at the empty lines
around 137 and 178) with appropriate Italian strings; ensure you preserve the
JSON key names exactly, use proper capitalization/punctuation consistent with
existing locale entries, escape any special characters, and run the repo's
i18n/json linter to validate the file.

In `@ghost/i18n/locales/ko/portal.json`:
- Line 33: Fill the empty Korean translations for the new Share modal keys
(e.g., the "Bluesky" key and the other empty share-label keys added for the
Share modal) so the UI isn’t mixed-language; locate the empty entries (the
"Bluesky" key and the other newly added share keys indicated in the review) and
replace each empty string with the proper Korean translation, keeping the JSON
key names intact and ensuring punctuation/quoting stays valid.

In `@ghost/i18n/locales/pt-BR/portal.json`:
- Line 33: Several share-modal keys in pt-BR locale (for example the "Bluesky"
key and other empty share strings in portal.json) are left as empty strings
causing fallback to source text; open ghost/i18n/locales/pt-BR/portal.json,
locate the empty share-related keys (e.g., "Bluesky" and the other empty entries
mentioned) and replace each "" value with the correct Brazilian Portuguese
translation that matches the source intent (preserve punctuation/capitalization
and any placeholders), then save and run a quick smoke check of the portal share
modal to confirm translations appear.

In `@ghost/i18n/locales/ru/portal.json`:
- Line 33: Several new RU locale keys in portal.json are left empty (e.g.,
"Bluesky" plus the other new share-related keys added at the same commits),
which causes English fallbacks; populate each newly added string value with the
correct Russian translation for the corresponding share modal labels/buttons
(find and update the empty keys such as "Bluesky" and the other newly added
empty keys in the same JSON object) so the Russian UI shows translated text
instead of English fallbacks.

In `@ghost/i18n/locales/si/portal.json`:
- Line 33: The new Sinhala locale has empty values for share-label keys (e.g.,
"Bluesky", and the generic labels "Copied", "Copy link", "More options",
"Share") so the UI falls back to English; open ghost/i18n/locales/si/portal.json
and provide Sinhala translations for those keys (and the other empty keys
mentioned at positions corresponding to lines 59-60, 89, 128, 137, 178, 216,
246), ensuring brand names like "Bluesky" remain unchanged (passthrough) while
all generic labels receive proper Sinhala text.

In `@ghost/i18n/locales/th/portal.json`:
- Line 33: Several share modal translation keys in
ghost/i18n/locales/th/portal.json (e.g., "Bluesky" plus the other empty keys at
lines mentioned) are empty; provide Thai translations for each of the new
share-related keys so the UI renders Thai text. Open portal.json and replace the
empty string values for the keys "Bluesky" and the other blank share modal keys
(the entries referenced at lines 59-60, 89, 128, 137, 178, 216, 246) with
appropriate Thai translations that match the English source text, keeping the
JSON key names unchanged and preserving punctuation and any interpolation
placeholders.

In `@ghost/i18n/locales/zh-Hant/portal.json`:
- Around line 59-60: The file has empty Traditional Chinese values for the
share-related keys "Copied" and "Copy link" (and two other empty string keys
later in the file at the noted positions); fill them with proper zh-Hant
translations (e.g., "已複製" for "Copied" and "複製連結" for "Copy link") and likewise
provide appropriate Traditional Chinese strings for the other empty keys found
at the two later positions so all portal share/action labels are fully
localized; update the values for the keys "Copied" and "Copy link" (and the
other empty keys at the indicated locations) in
ghost/i18n/locales/zh-Hant/portal.json.

---

Duplicate comments:
In `@ghost/i18n/locales/hu/portal.json`:
- Around line 59-60: The Hungarian locale file is missing translations for
several user-facing action labels; update the portal.json entries for the keys
"Copied" and "Copy link" (and the other empty action-label keys noted at the
same file positions) by providing appropriate Hungarian strings (e.g., "Másolva"
for "Copied", "Link másolása" for "Copy link") so users see localized UI text
instead of falling back to English; edit the existing keys in portal.json and
ensure the values are properly quoted JSON strings.

In `@ghost/i18n/locales/nn/portal.json`:
- Around line 59-60: The nn locale file has empty values for the share action
keys—fill in Nynorsk translations for the JSON keys "Copied" and "Copy link"
(and the other two empty keys shown at lines 137 and 178) so these user-visible
actions do not fall back to the source locale; update the corresponding string
values in ghost/i18n/locales/nn/portal.json with accurate Nynorsk phrases while
keeping the JSON keys unchanged.

---

Nitpick comments:
In `@ghost/i18n/locales/context.json`:
- Line 33: The context.json entries for new share keys (e.g., "Bluesky" and the
other newly added share keys) are currently empty; add concise translator
metadata for each key in context.json describing where and how the string is
used (e.g., "Label for sharing via Bluesky social network", whether it's a
button/tooltip, and any placeholder/noun/gender/pluralization notes) so
translators know context and constraints; update the entries for all new share
keys (the same set referenced in the review) with short, clear descriptions that
include intended UI location (button/label/menu), any variable placeholders, and
preferred tone/register.

In `@ghost/i18n/locales/el/portal.json`:
- Line 33: Several share-label JSON keys (e.g., "Bluesky", and the other empty
keys noted at positions 59-60, 89, 128, 137, 178, 216, 246) are empty, causing
English fallback; open the portal.json locale object and provide Greek
translations for each empty share-related key (for example fill "Bluesky" with
the Greek equivalent), ensuring every empty string is replaced with an
appropriate Greek label so the Share modal displays fully localized text for the
el locale.

In `@ghost/i18n/locales/hi/portal.json`:
- Line 33: The listed share-string keys in portal.json (e.g., "Bluesky" and the
other empty keys at the mentioned locations) are empty and must be replaced with
Hindi translations; open ghost/i18n/locales/hi/portal.json, locate the keys
"Bluesky" (and the other empty entries referenced) and replace each "" with an
appropriate Hindi translation that matches the share-modal context (short,
UI-friendly labels), preserve JSON string escaping and punctuation, run a
JSON/l10n validation or build to ensure no syntax errors, and optionally add a
comment or note for a native reviewer if unsure about nuance.

In `@ghost/i18n/locales/ro/portal.json`:
- Line 33: Fill in Romanian translations for the new Share modal keys in
portal.json — notably the "Bluesky" key (and the other empty share-modal keys
referenced in the review) by replacing the empty strings with proper Romanian
text, keeping the JSON keys unchanged; ensure you preserve existing
formatting/commas and escape any special characters, validate the JSON after
editing, and run the locale lint/CI to confirm there are no missing translations
or syntax errors.

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@apps/portal/src/components/pages/share-modal.js`:
- Around line 401-403: getShareUrl currently returns getCanonicalUrl() or
getHostWindow().location.href which can include hash fragments like
"#/portal/share"; update getShareUrl so that when falling back to
getHostWindow().location.href it strips the hash fragment (i.e. use
location.href.split('#')[0] or construct from getHostWindow().location.origin +
pathname + search) and return that cleaned URL; keep getCanonicalUrl() path
unchanged and only modify the fallback branch in the getShareUrl function.

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@apps/portal/src/components/pages/share-modal.js`:
- Around line 401-403: getShareUrl currently falls back to
getHostWindow().location.href which can include hash fragments; change the
fallback to build the URL from getHostWindow().location.origin +
getHostWindow().location.pathname + getHostWindow().location.search to strip any
hash. Update the getShareUrl implementation to use getHostWindow().location
(origin/pathname/search) when getCanonicalUrl() is falsy, and adjust related
unit tests that asserted the old href behavior to expect the hash-free URL
instead.