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

Inline comments:
In `@apps/web/app/`(marketing)/download/page.tsx:
- Line 72: Replace the arbitrary opacity bracket syntax in the span's className
(the token bg-white/[0.05] used in the element with class "inline-flex
items-center px-5 py-2 font-mono text-sm font-semibold rounded-full ...") with
the simpler Tailwind slash form bg-white/5 so it uses the idiomatic standard
opacity scale instead of an arbitrary value.

In `@apps/web/app/`(marketing)/pricing/page.tsx:
- Around line 30-32: The NumberTicker is forcing integer formatting for the
annual price which will round values when
proPricing.intervals.annual.amountCents isn't divisible by 100; update the
NumberTicker usage to allow the correct decimal precision (remove or change
decimalPlaces={0}) and compute/display annualPrice and monthlyPrice with
necessary decimal precision (monthlyPrice and annualPrice from
proPricing.intervals.*.amountCents / 100) or pass a dynamic decimalPlaces based
on whether amountCents % 100 === 0 so NumberTicker shows cents when needed.

In `@apps/web/app/docs/`[[...slug]]/page.tsx:
- Around line 13-28: This file defines a local mdxComponents object that
duplicates the shared registry; instead import and reuse the shared registry
export (defaultMdxComponents) and either use it directly or merge additional
local overrides via spreading (e.g., const mdxComponents = {
...defaultMdxComponents, Card, Cards, Callout, Step, Steps, Tab, Tabs,
Accordion, Accordions, File, Folder, Files, TypeTable };), removing the
duplicated definition so the single source of truth (defaultMdxComponents) is
used for MDX rendering.

In `@apps/web/components/Footer.tsx`:
- Around line 137-149: The Footer component duplicates anchor markup for social
links; extract the repeated anchor rendering into a small helper component or
function (e.g., SocialLink or renderSocialLink) and use it in both places where
socialLinks.map(...) is used to ensure consistent props (href, target,
rel="noopener noreferrer", aria-label, className, and icon). Update both
occurrences to call the helper with the social object (or its fields) so hover
styles and accessibility attributes stay in one place and prevent future drift.

In `@packages/api/drizzle/0005_slippery_the_fury.sql`:
- Around line 1-5: Remove the file-based SQL migration that alters the
shared_notes table (the statements adding tags, backlinks, word_count,
notebook_name and the index idx_shared_notes_user_public); this migration must
not live under packages/api. Delete this SQL artifact and instead apply the
schema changes via the project's configured drizzle-kit push workflow (update
the canonical Drizzle schema model or run the push command so the change is
recorded in the push-managed schema), ensuring no file-based migration remains
in packages/api.

In `@packages/api/drizzle/meta/0005_snapshot.json`:
- Around line 1-1008: The checked-in Drizzle snapshot (the JSON containing
tables like "devices", "magic_links", "newsletter", "plugin_catalog",
"shared_notes", "subscriptions", "sync_log", "users", etc.) must be removed from
the API package so the codebase has a single schema source of truth; delete the
file representing the snapshot and revert any changes that add it
(packages/api/drizzle/meta/0005_snapshot.json), keep your schema changes in
schema.ts, and then apply them using drizzle-kit push to generate migrations
instead of committing migration metadata into the repo.

In `@packages/api/src/routes/share.ts`:
- Around line 35-38: The schema currently allows negative values for the field
defined as wordCount (z.number().int().default(0)); update the validator to
reject negatives by adding a non-negative constraint (e.g., use .nonnegative()
or .min(0) on the z.number().int() chain for wordCount) so any incoming value is
validated before persisting, keeping the default(0) in place; locate the
wordCount schema entry alongside tags and backlinks in the share route and apply
the constraint there.
- Around line 25-27: The route-level CORS override in share.use('/public/*',
cors({ origin: '*' })) won't work; move the exception into the app-level CORS
setup in the main app (the global cors(...) configured in index.ts) by adding
conditional logic to its origin option that returns '*' for paths starting with
'/share/public/' and otherwise enforces the restricted-origins/credentials:true
behavior; update the app-level cors origin function to inspect req.path (or
req.url) and return '*' for that prefix so preflight and actual requests receive
the correct headers and remove the route-level cors call from share.use.

---

Outside diff comments:
In `@apps/desktop/src/renderer/components/NoteEditor.tsx`:
- Around line 167-176: In handleShareOnWeb, avoid sending an empty string for
notebookName when notebook data is still loading; instead guard so we only call
window.readied.share.create when notebook is resolved (or pass undefined/null to
explicitly indicate missing value). Update the share invocation in
handleShareOnWeb (and the similar use at the other occurrence around line 183)
to either early-return if notebook is loading, or set notebookName: notebook ?
notebook.name : undefined (not ''), and ensure UI disables the share action
while notebook query is pending so metadata is not silently dropped.