Commit Graph

37 Commits (cb758c6a03b15fc643d11bca9f3db548bd537c8d)

Author SHA1 Message Date
mula.liu cb758c6a03 fix(drop): disable a spent button and mark it, so both drag paths agree
A file from the file manager arrives through the native drag channel, where wry fixes the macOS drag operation to Copy, so the cursor could never carry the refusal. The answer now lives on the button: it is disabled for the length of the gesture, shows a prohibition sign over its own label, and takes no hover feedback. A Recent row also stops being reported as 'no files' by the native enter, which had lit all three buttons for a file two of them could not serve.
2026-11-07 02:34:44 +08:00
mula.liu f625832856 fix(drop): show a forbidden cursor for spent buttons 2026-11-07 01:15:10 +08:00
mula.liu 3057c65d27 fix(drop): stop the drag-end fallback from eating the drop it waits for
0.1.11 made a dragged row do nothing on every button. The release added to
`dragEnd` landed the gesture immediately, and on macOS the native drop is
reported *after* the button is up: the fallback consumed the gesture with
`dragEnd`'s own position - which Chromium reports as the origin, not as where
the pointer stopped - and the drop that followed was read as a finished
gesture and thrown away. Three buttons, no feedback, on both platforms.

The fallback now waits, and only claims the gesture when it can actually name
a button. A release that aims nowhere stands back, so a real drop that arrives
later still runs, and `landed` keeps the two from both acting. A position of
(0, 0) is treated as no position reported, which is what it is on Chromium, and
answered with the last position the drag moved through.

A row dragged out of the window now carries the file rather than the row. Left
alone the engine photographs whatever is under the pointer, and a Recent row is
a thumbnail, a name, an age, a folder path and five hover buttons - a strip of
the list, which reads as the whole list coming along. The ghost is the file: the
picture the list already decoded, or the extension when there is no picture,
with the name under it, matching the figure the ring draws for a file it is
about to convert.

Rebuilt both 0.1.11 installers from this tree.
2026-11-07 00:53:09 +08:00
mula.liu be84d5640f release: prepare Shift 0.1.11
Versions, release docs and the ledger's version row for the two installers.

Both artifacts were built from this tree with the release key baked in, so
either one can verify the signed channel: `Shift-0.1.11-macOS-universal.dmg`
(ad-hoc signed, `hdiutil verify` valid, no notarization) and
`Shift-Setup-0.1.11-win-x64.exe` (cross-compiled, PE machine `0x8664` checked,
frontend confirmed embedded).

The Windows drop fix needs a real Windows host before it can be called done:
this forge has no second machine, and the two delivery paths that went silent
are exactly the ones only WebView2 exercises.
2026-11-06 23:14:57 +08:00
mula.liu 2bf63f2366 fix(drop): let Windows finish a row dropped on a button, and spend every button alike
A row dragged from Recent onto any of the three buttons did nothing on
Windows, and reported itself as a refusal. Both delivery paths can stay
silent on that platform, so the gesture now ends in `dragEnd`, which always
arrives and carries a point to hit-test.

The two paths are silent for two separate reasons. A Recent row is a real
file drag, and WebView2 registers its own OLE drop target on the window, so
the DOM drop never reaches the page; that target then reads only `CF_HDROP`,
which an in-page drag does not carry, so `enter_is_valid` stays false and the
native `over`/`drop`/`leave` are withheld too. `landed` keeps the fallback an
execution rather than a second one, and a release outside the window runs
nothing, because the hit-test has slack around every button and the row was
meant for Explorer.

An idle ring also stops getting in the way. It is borderless and always on
top, so one left open from a previous drop sits over the buttons; macOS
passes mouse events through its transparent pixels and Windows hands the
gesture to whichever HWND is under the pointer. Starting a row drag now puts
such a ring aside, while a ring owned by an in-flight Shift-drag gesture keeps
waiting for the release that decides its fate.

The availability rule stops being OCR's alone. `lib/dropCapabilities` answers
one question - can this button serve these files - and the button's spent
state, its candidacy while a drag is in flight, and the drop itself all ask
it, so Convert spends for a `.key` the way OCR spends for a PDF, on both
platforms, whichever drag source carried the file. Tools never spends: its
ring ends in Open, Reveal and Send. An unknown payload is not a refusal,
because spending on an empty path list would disable a gesture that works.

Two other reports this round were not about the drag at all:

- A file received over the LAN now reveals itself only when "show results in
  Finder" is on, the way a finished conversion already behaves, and a batch
  reveals once at its last file rather than once per file.
- Missing runtime components install as one request. Installs run one after
  another because the package managers hold a single lock, and one package
  answering two rows - Poppler for both PDF rows on Windows - is installed
  once. The panel re-reads the machine afterwards either way, since a batch
  that stopped at its first failure may have landed everything before it.
2026-11-06 23:13:53 +08:00
mula.liu 84c4056a0d feat(ui): spend the OCR button instead of explaining it, and unify how the app speaks
Two changes, one goal: the same gesture and the same news should look and read the
same way wherever they happen.

Dropping a file OCR cannot read used to be answered after the fact - the drop ran,
refused, and popped "文字识别仅支持图片格式". The user had to do the wrong thing
first and then be told. Now the decision happens when the drag starts: MainWindow
records the files in flight (`dragPaths`, from the native `enter` payload or from a
Recent row's `dragstart`) and marks the button spent for the whole gesture with
`is-drop-unavailable`, so the refusal is visible before the pointer is committed and
releasing on it is inert and silent. Both drag sources were verified in a production
build, including the reverse case: an image still lights the button and opens the
editor. `over` carries no paths and `dataTransfer` is unreadable during `dragover`,
so the paths have to be registered at the start - a later refactor that reads them
from the move event gets nothing.

The audit that followed found the same class of problem in the messaging, and worse:
the app said one thing three ways.

Prompts were the largest gap. A Rust-authored sentence reached the screen verbatim,
so a Chinese interface answered Convert with `Saved 1 file.`, and macOS's first-run
write-permission failure was one long English line. Rust now names the outcome or the
failure (`outcomeSaved`, `errCaptureBlocked`) and the interface words it; `translate`
still returns an unknown key unchanged, so genuine technical detail - `ffmpeg exited
with status 137` - is reported as it is rather than flattened into a generic line.
`feedback.test.ts` scans the Rust sources and fails on any code without wording in
both languages, and on any outcome the worder does not know; both directions were
checked by breaking them. It also asserts the two dictionaries list identical keys,
which was silently false before.

Durations were arbitrary: the identical share result showed for 2.6s in the ring and
3.6s in the main window, one file's `processing` message lived 12s in one branch and
120s in another, and generic errors used 2200/2400/3000/3200/3800. `FEEDBACK` is now
the only ladder, and `hold` is reserved for tasks that report progress and must not
expire mid-task.

Error text had three normalisation idioms, two inside the same file; `messageFrom()`
is the only one left. Share failures reported twice at once - a banner saying "could
not send" plus a toast naming a different reason - and now report once, in the panel,
with the real reason. The editor's failure notices wore a green check and lasted 1.4s;
a clipboard refusal was silent, and an OCR failure printed into the text box as though
it had been read from the image.

Disabled controls were dimmed at nine different opacities across the app, three
buttons were disabled in JS with no CSS at all, and several `:hover` rules answered a
disabled control. `--dimmed` plus `cursor: default` and `:not(:disabled)` hovers is now
the single treatment, and the OCR drop-target state joins it. Every transient message
is a live region, three unlabeled icon buttons are named, Escape closes the settings
sheet and the first-run panel, the main toast is raised above every sheet of its
window, and nine raw px font sizes went back onto the type ladder.

Out of scope, deliberately: the accent is still ~87 literals rather than one variable,
and the muted warm greys are still written many ways. Both need a visual pass, not a
search and replace.
2026-11-01 16:18:20 +08:00
mula.liu 75405d84c4 release: prepare Shift 0.1.10
Version and release docs for the two installers.

The ledger's drop-gesture section now says which release did what: 0.1.9 removed
the action-ring fallback and added the explaining toast, 0.1.10 removed the toast
and the panel's own drag animation. Both were written as one change until the
published 0.1.9 tree was checked, and it still had the toast and the is-dragging
rule.
2026-11-01 12:48:57 +08:00
mula.liu 45325f0a6c feat(ui): quiet the drop gesture, and refuse files OCR cannot read
Four changes to how the main window answers a drag.

The tray row said "识别图片文字…" where the window says 文字识别, and the ellipsis
made it read like a preview rather than a command. It now carries the same words
as the button, in both languages.

OCR refuses a file it cannot read instead of handing it to the format ring. The
fallback was meant to be helpful - "the format ring is more useful than a failing
OCR run" - but from the user's side it looked like the button they dropped on had
ignored their file and opened something else. A drop on OCR is now either a read
or a refusal that names the reason.

Dragging an outside file and dragging a Recent row are now the same interaction.
The panel used to scale, recolour and swap its heading when a file entered the
window from Finder, while a row dragged from the list did none of that, because
an in-webview drag raises no native drag events. The panel no longer animates at
all: the is-dragging class, its two rules, and the transition they drove are
gone, and feedback lives only on the three buttons, which both paths already
share.

Releasing off a button no longer pops the toast. 0.1.9 added it to explain why
nothing had run, but it fired at the pointer, in a place the user had not chosen
to aim at, and the buttons already show where a drop lands. Off a button,
nothing happens, silently, on both paths.

The version comparison test gains the patch-component case: 0.1.10 is the first
release whose patch number reaches two digits, and the rule was only asserted for
the minor position.
2026-11-01 12:48:36 +08:00
mula.liu b524b69fc8 release: prepare Shift 0.1.9
Version, the release docs and the engineering ledger for the two installers.

The ledger gains a section on the Runtime components panel, because the bug it
records was invisible rather than broken: a dropped `return` made macOS answer
the document-PDF row with a Pandoc pipeline it never uses, so the panel reported
a missing component with no way to install it. The section states the invariant
that a row may not read as missing unless it also offers a way forward, which is
the part a future refactor is most likely to lose again.

README sections that described dropping files as "opens the action ring" now
describe the aimed rule, and the capture-behaviour option is gone from the
Settings tour.
2026-11-01 12:04:03 +08:00
mula.liu e6818e029e feat(ui): drop onto a button, and read the panels again
Three changes to the main window, requested together.

A file drop is now aimed. The three buttons are the only drop targets and the
button you release on is the action it runs; a release anywhere else on the
panel runs nothing and says so, instead of opening an action ring nobody asked
for. This replaces the old fallback in both delivery paths - the DOM handler and
the native webview drop - because two routes to the same gesture must not have
two different rules. dropFiles therefore takes a required action rather than an
optional one, and the actions ring is still reachable from the Shift-drag
gesture and from a file type with no convertible formats.

Recent rows can be dragged back onto those buttons. A row leaves Shift as a real
file drag, so one gesture can be reported twice, once by the DOM and once by the
native events, and which arrives first depends on the engine; recentDrag.landed
lets only the first through. The hint under the buttons names the affordance,
which is otherwise invisible, and all three buttons light up as candidates for as
long as any drag is in flight - a native one via dragging, an internal one via
rowDragging, since a row drag inside the webview does not raise native events.

Type sizes are on one ladder now (--text-3xs to --text-hero) instead of being
invented per rule, which is how the settings drawer drifted down to 7-8px. 92
declarations under 12px became one. The drawer is wider, its tabs are pills, and
the runtime, share, setup and radial surfaces moved onto the same scale.

The capture-behaviour setting is removed: the CaptureAfter enum, its field, its
command and its UI. A finished capture always shows the result card, falling back
to the editor when a card window cannot be created. Stored settings that still
carry captureAfter load unchanged, because the struct does not deny unknown
fields.

Also dropped 23 i18n keys no surface used, one dead re-export in history.ts, and
a stale .home-drop p rule that was outranking the new hint and sizing it as body
copy. tsconfig now turns on noUnusedLocals, noUnusedParameters and
noFallthroughCasesInSwitch, which is what keeps the dead imports from coming
back; the tree already passes all three.
2026-11-01 12:02:24 +08:00
mula.liu 23973cee8f fix(runtime): report the bundled renderer for document PDF on macOS
0.1.8 turned the renderer branch of document_pdf_component into a bare expression,
so the component it built was discarded and every Mac fell through to the Pandoc
row. That row requires a LaTeX or Typst engine macOS never runs, so Settings ->
Runtime components read 'Pandoc PDF pipeline: missing' with no Install button,
because document-pdf has no macOS install target.

The two platforms now have their own function, like every other platform-specific
row in the file, so the fall-through is a compile error rather than a silent one.
The Pandoc half is still real on macOS - it turns a picture-bearing DOCX into HTML
for the renderer - and it keeps its own row and install target.

Two guards cover it: the row must stay bundled on macOS, and no row may read as
missing without either an install entry or a non-external source. The second
reproduces the reported symptom exactly when the fix is reverted. The matching
PDF-engine error now names what the panel actually shows on each platform.
2026-11-01 11:59:42 +08:00
mula.liu 0aa929b2f5 build: bake release key into macOS packages 2026-10-27 18:49:21 +08:00
mula.liu df35111326 release: prepare Shift 0.1.8 2026-10-27 18:45:32 +08:00
mula.liu d9bb079ec2 docs: record discovery, conversion and macOS packaging regressions 2026-10-26 20:24:21 +08:00
mula.liu 708bb5b0b1 v 0.1.7 2026-10-26 20:11:20 +08:00
mula.liu 35cca5987c release: 0.1.6 — discover peers across filtered Wi-Fi 2026-10-26 19:53:35 +08:00
mula.liu 579fc6218a release: 0.1.5 — device discovery survives an upgrade
An upgrade emptied the "Send to a device" list, with nothing in the UI to say why.
share.rs was not the cause: the last commit to touch it is b732b91, which only
recorded received files in the history library.

The cause is the macOS Local Network grant. Builds are ad-hoc signed, so every
rebuild is a new code identity, and the grant is keyed to that identity rather than
to the bundle id - 系统设置 now holds five Shift rows, one per build this machine has
run. The declared NSLocalNetworkUsageDescription was missing, so a new identity was
never asked and simply received no group traffic: beacons still went out, direct
unicast was still answered, only the list stayed empty.

That declaration is bc5d3b8. Both READMEs and the packaged macOS note now name the
permission and say what a denial looks like, because unlike Screen Recording it
produces no error - just an empty list. The Developer ID item in M5 records that
this has now actually cost a user a feature, not merely "may reset approvals".

Also ships the Updates panel button pair from 22ff93a, which was merged after 0.1.4
and never published.

Gates: cargo fmt --check clean, cargo test --lib 152 passed / 2 ignored, pnpm check
clean, pnpm test 38 passed. Channel verified by downloading both artifacts back
from the raw endpoint and re-hashing against the manifest, and by the ignored feed
test run with the release key. 55,504,368 B DMG and 24,521,557 B installer.
2026-10-26 19:14:05 +08:00
mula.liu bc5d3b80d4 fix(share): declare the local network usage description
Discovery stopped working after an upgrade without any change to share.rs: the
last commit to touch it is b732b91, and only to record received files in the
history library.

What the upgrade does change is the code identity. Builds are ad-hoc signed, so
every rebuild is a different binary to macOS, and the Local Network grant is keyed
to that identity rather than to the bundle id - 系统设置 now lists five separate Shift
rows, one per build this machine has run. The copy installed by the upgrade has an
identity macOS has never been asked about.

It also has no way to be asked: NSLocalNetworkUsageDescription was never declared,
and macOS shows no local network prompt without it. The app then simply does not
receive the group traffic, silently. The panel confirms the symptom is not specific
to Shift's port - this Mac received zero mDNS and zero SSDP packets while its own
beacons looped back fine, and unicast to a peer still works, which is how the two
other copies were found by hand.

Declaring the string lets the prompt appear for a new identity. The durable fix is
the stable Developer ID identity already tracked under M5, which stops the grant
from being lost on every single build.
2026-10-26 18:54:25 +08:00
mula.liu ed4acee2e4 docs: record the published 0.1.4 channel
Both artifacts were downloaded back from the raw endpoint and re-hashed against
the manifest rather than read from the local build output, and shift-update.sig
verifies over the manifest's exact bytes against the release public key.

The retired .pkg left the branch with this publish: the tree is rebuilt from
artifacts/ on every run, so dropping it from the build was enough.
2026-10-26 17:36:47 +08:00
mula.liu 48b24acc2f fix(release): derive the public key from either key file
A raw ed25519 private key is 32 bytes and so is its public half, so
'pubkey KEY_FILE' could not tell them apart and printed the private bytes as a
public key. Baking those into a build produces a key no signature can verify
against, and build.rs accepts any 64 hex characters, so the mistake is silent at
build time and shows up on a user's machine as an update check that cannot verify
the manifest.

Anything not named *.pub is now read as the private key it came from and expanded,
so both documented spellings of the command yield the same key.
2026-10-26 17:29:59 +08:00
mula.liu 334082cd9b release: 0.1.4 — figures survive every conversion
Three conversion fixes since 0.1.3, all found with the same two documents:

- DOCX -> PDF kept the text and dropped the pictures, because AppKit's OOXML
  reader returns an attributed string with no attachments at all. An image-bearing
  DOCX now goes through Pandoc into HTML before the same printer, which keeps
  headings, tables and figures. Image-only DOCX files still take the page-scan
  path, and a machine without Pandoc falls back to the old text-only result
  rather than failing.
- Markdown -> DOCX/RTF/HTML lost the same figures for a different reason: a
  Markdown image is a path, Pandoc has to open the file to embed it, and it
  resolves that path against its own working directory, which for a running Shift
  is nowhere near the document. It now gets --resource-path of the source folder.
- A picture that did arrive printed as a cropped fragment. The layout sizes an
  attachment from the density header in the file - 72 dpi when it carries none -
  and ignores CSS, so a 1600 px screenshot asks for 1200 points on a 595 point
  page. The renderer fits oversized attachments to the text column, scaled and
  not resampled. Markdown and HTML documents with wide images are covered too.

The Updates panel's install and discard buttons are one matched pair now, sized to
the panel's own 12px scale instead of the dense 8.5px rows of the Runtime tab they
were borrowed from, and the row drops the discard control while an install is
counting down.

Gates: cargo test --lib 152 passed / 2 ignored, pnpm check clean, pnpm test 38
passed. Artifacts verified from the built bundles, not the build log: the DMG
carries 0.1.4, x86_64 + arm64, Signature=adhoc, and its bundled doc-render places
a wide image at 499pt inside the page; the Windows exe carries the feed URL and
the release public key.
2026-10-26 17:24:22 +08:00
mula.liu 22ff93a5fc fix(updates): make install and discard read as one decision
The row under a verified download took both controls from the Runtime tab, where
rows are dense: .runtime-install is 27px tall at 8.5px text and .settings-link is
a bare 8.5px text link with no box at all. In the Updates panel, whose own status
text, artifact chip and version pill are 12px, that produced an orange pill beside
floating text - the pair did not look like one choice, and the text link did not
read as a button you could press.

They get their own .update-action now, sized to the 12px scale the panel already
uses, and both take the same box so the eye groups them. The commit variant wears
the app's existing primary gradient, so the action that does something is the loud
one and Discard stays the quiet alternative.

"放弃" also stops competing at the moment it stops meaning anything: once the
handoff script is written the app is counting down to exit, so the row collapses
to the single control still in play. update_clear only resets the status, so this
is presentation, not a saved deletion.

updateInstalling was a whole sentence inside a fixed-height pill, which is what
made that button stretch unevenly against its neighbour. It is "正在安装…" now;
the panel's own closing paragraph already says Shift will restart and interrupt a
running conversion, so the button does not have to repeat it.
2026-10-26 16:22:34 +08:00
mula.liu 9950607cd4 fix(markdown): keep images when a document with relative figures is converted
Same class of bug as the DOCX one, different cause. A Markdown image is stored as
a path, so Pandoc has to open the file to embed it - and it resolves that path
against its own working directory, which for a running Shift is nowhere near the
document. 智飞空地一体化低空应用平台技术方案.md references images/system-architecture.png
and images/production-deployment-topology.png; both came back as "Could not fetch
resource", and Pandoc replaced each figure with its alt text. The DOCX was 22 KB
with no word/media entry at all.

Passing --resource-path of the source's own folder fixes DOCX, RTF and HTML in one
line. It is additive rather than a replacement: Pandoc still searches the working
directory too, so a figure that resolved before still resolves - verified with two
images of the same relative name in two different folders, both of which landed in
the output.

md -> pdf already worked, because Pandoc leaves the path untouched there and hands
the HTML to the renderer with a base URL pointing at the document's folder; only
the routes where Pandoc must read the bytes itself were affected. md -> html was
the quieter case: --self-contained promises one portable file, and without the
figures inlined the single HTML opened as a broken image icon.

keeps_markdown_images_when_converting_to_word pins docx and rtf. It fails against
the previous build with "docx ... lost the picture", and the RTF check reads the
pngblip marker rather than assuming a zip.
2026-10-26 15:43:59 +08:00
mula.liu 19602b79f0 fix(docx): keep figures when a DOCX is printed to PDF
Two bugs, both visible in 平台技术方案(带图测试专用).docx: one figure, eleven
tables and 357 paragraphs, whose PDF came out as a text-only document.

First, AppKit's OOXML reader returns the text of a DOCX and silently drops every
inline drawing - an attributed string with zero attachments for a document with a
picture in it. That is not a rendering loss, it is a parse loss, so no margin,
print setting or layout change can recover the figure: by the time the page is
drawn, the picture is simply not in the attributed string. A DOCX whose body
contains an image is now converted by Pandoc into HTML with its media extracted
beside it, and the HTML - which Pandoc reads faithfully, headings, tables and
pictures - goes to the same printer. Image-only DOCX files keep the existing
page-scan path, which runs first, and a machine without Pandoc falls back to the
old text-only behaviour rather than failing.

Second, once pictures could arrive they printed as a cropped fragment of
themselves. The layout sizes an attachment from the density header inside the
file, assumes 72 dpi when there is none, and ignores both bounds and CSS width: a
1600 px screenshot at 96 dpi asks for 1200 points and lands on a 595 pt page.
Measured across PNG pHYs and JPEG JFIF, the placed width is exactly
pixels / dpi * 64. A plain NSTextAttachment does honour bounds, so the renderer
now replaces any oversized attachment with one that fits the text column; the
print operation scales it to the page with the text, landing at 499pt, which is
the printable width the body text already uses. Nothing is resampled, only the
size the layout asks for changes. This also fixes Markdown and HTML documents
with wide images, which had the same overflow.

Both halves are pinned by tests, and both fail against the previous build:
keeps_pictures_when_rendering_a_text_docx_to_pdf sees no image at all, and
fits_a_wide_picture_onto_the_page reports a picture placed 1066.77pt wide on a
595pt page. The second reads the Form XObject's /BBox, so it needs no content
stream decoded and no pixel compared.
2026-10-26 14:50:52 +08:00
mula.liu 58949bebd2 docs: macOS ships the DMG alone, the pkg is retired
The .pkg existed to hand a fresh machine a copy that was not quarantined, so it
opened with no prompt at all. The DMG has now been verified to work on a fresh
machine - drag to /Applications, one approval on first launch - which is the same
one approval the DMG has always needed. So the second container bought nothing
and is dropped: one artifact per platform is less to keep straight, and nothing in
the channel changes.

What the docs say instead of recommending the package: install the DMG, allow the
first launch once. In-app updates still never prompt, because Shift's own
downloader sets no quarantine flag. The macos manifest key stays a DMG for the
reason it always did - the in-app handoff mounts it with hdiutil.

scripts/macos-pkg.sh stays in the tree and RELEASE.md says plainly that it is no
longer part of a release, so the next reader does not wonder whether a publish is
missing it. The 0.1.3 branch still holds the retired package because removing it
means re-publishing; it has no manifest key, so nothing can be served it.

The packaged note is rewritten for the same reason: it told a reader to download a
file that will no longer be built, and its verification section checked the
package instead of the image.
2026-10-26 10:47:48 +08:00
mula.liu f2a1ff6d52 docs: record the macOS packaging scheme next to the artifacts
The ad-hoc signature, the two containers and their different jobs, and how to
verify a download were explained only in docs/RELEASE.md. A user who downloads
Shift-macOS-universal.pkg from the releases branch never sees that file, so the
same write-up now also ships as artifacts/README-macOS-universal.txt, beside the
per-arch Windows notes that already travelled with the channel.

Every claim was checked against the shipped artifacts rather than carried over:
the .pkg payload is Signature=adhoc, pkgutil --check-signature reports no
signature for the package itself, and shasum -c passes on the published set. The
file is force-added to the repository even though artifacts/ is gitignored, so
the scheme is documented where a contributor reads it.
2026-10-26 10:40:33 +08:00
mula.liu 4ed236bd9e docs: correct why older builds opened
The commit before this one claimed releases that opened fine "were ad-hoc signed,
predating the config entry". They were not: every DMG this channel has published,
back to the first 0.1.0, carries Authority=Shift Local Signing, because Tauri selects
a keychain identity itself when signingIdentity is unset.

What survives is the verified part — a self-signed identity that cannot chain to a
trusted root elsewhere, and an ad-hoc binary that gets an approvable prompt instead of
a hard refusal — so the build change stands and only the archaeology is corrected.
2026-10-26 09:48:18 +08:00
mula.liu 42d6424e9f build: sign macOS ad-hoc so other machines can open the app
The published DMG was refused on a fresh Mac as damaged/malware, with only
"Move to Trash" — no 仍要打开, no pane entry to approve. That is not the
"unidentified developer" box, and it is worse than shipping unsigned.

Cause: `signingIdentity: "Shift Local Signing"`, a locally created self-signed
certificate. On the build host it looks healthy — `codesign` reports valid on disk
and satisfies its Designated Requirement, `spctl` even accepts it — but the
certificate lives only in this keychain, is self-issued and CA:FALSE, so it cannot
chain to a trusted root on any other machine. Sequoia turns an unchainable
signature on a quarantined download into a hard refusal.

Releases that opened fine predates that config entry and were ad-hoc signed, which
gets the softer prompt the user can clear (right-click → 打开, or 允许 in 隐私与安全性).
Set signingIdentity to "-" explicitly so this cannot drift back, and rebuild all
three macOS/Windows artifacts from it: app is `Signature=adhoc`, the DMG carries no
signature of its own, and the pkg payload is ad-hoc too.

Docs corrected: the earlier explanation in "macOS packaging" blamed the DMG
container, which was wrong — the container still matters for first install (an
installed app is not left quarantined, so a .pkg opens with no prompt), but the
malware verdict came from the certificate.
2026-10-26 09:44:53 +08:00
mula.liu e9760b8514 release: publish a macOS .pkg so a fresh machine can open Shift
Builds are signed with the self-signed "Shift Local Signing" identity and are not
notarized, so Gatekeeper calls Shift an unidentified developer. Dragging the app out
of the DMG hands that verdict to the app: a fresh machine refuses the first launch
until the user approves it in 系统设置 → 隐私与安全性.

`scripts/macos-pkg.sh` wraps the built bundle with pkgbuild and the channel now
publishes `Shift-macOS-universal.pkg` alongside the DMG. Verified rather than
assumed: installing a quarantined copy of the package leaves the installed app with
only `com.apple.provenance` — no `com.apple.quarantine` — and `codesign --verify
--deep --strict` still passes, because pkgbuild neither re-signs nor strips the
payload (CDHash identical across built bundle, DMG copy and pkg copy: 3b7fac6c…).

The package is unsigned because `productsign` needs an Installer Signing certificate
and this build has only a code-signing identity, so the approval does not vanish — it
moves to the download, once, before anything is installed. `installer -pkg … -target
/` needs no approval at all.

The `macos` manifest key stays a DMG on purpose: `update_install`'s handoff mounts the
image with hdiutil, so pointing the key at a .pkg would break in-app updates.
2026-10-26 09:22:39 +08:00
mula.liu c98d554a88 release: 0.1.3 — the Recent list survives an upgrade
The Updates tab drops the "installs the ... artifact" chip, and the state label
now leads the status row instead of floating right, since the version it used to
sit beside moved into the header.

The file list no longer disappears on upgrade:

- The library already lived in the app data directory, outside the bundle, so an
  in-app update or reinstall never touched `history.json`. What it never had was a
  bridge from the store 0.1 used: that list lived in the webview's own storage,
  which a reinstall does not survive, so the first launch of a newer build showed
  an empty Recent list over files that were all still on disk.
- `history_import` merges those rows once, on the first launch after an upgrade.
  An entry the library already lists keeps its own timestamp, the kind is
  re-derived from the file rather than taken from the older store's guess, and the
  legacy key is dropped only after the merge succeeds so a later upgrade cannot
  resurrect rows the user has since removed.
- `HistoryEntry.kind`/`.at` gained serde defaults, so a row from the older store
  degrades to a usable entry instead of failing the whole import.

Verified on this machine that the legacy `shift.recent` key is still present in the
installed app's webview store, so the import has rows to adopt.

Gates: cargo fmt --check clean, `cargo test --lib` 149 passed / 2 ignored,
`pnpm check` clean, `pnpm test` 38 passed, `pnpm build` ok.
2026-10-26 04:02:31 +08:00
mula.liu 15498482fa release: 0.1.2 — install the update in place, and lead the tab with the host
Updates now finish without leaving the app. After the SHA256 gate, macOS replaces
its own `.app` from the downloaded disk image and Windows runs the same NSIS
installer with `/S`; both from a detached helper that waits for this process to
exit and then opens the new copy.

- `update.rs`: `bundle_path` (is this a bundled run?), `can_replace` (is the
  enclosing folder writable — checked before quitting, not after), and the two
  handoff scripts. Every macOS failure path still `open`s the bundle it had, so a
  failed swap leaves Shift running rather than closed.
- `windows-installer.nsi`: `${Silent}` skips the "Shift is running, close it?"
  box, which would otherwise abort an update nobody is there to answer.
- `useUpdate.ts`: a failed install reports its own error and keeps the verified
  download, instead of downgrading a "ready" status to "error".

The Updates tab now leads with two lines above everything else: system,
architecture and running version, then the feed URL. The header no longer repeats
the version in the status row.

Verified end to end on macOS: a 0.1.1 bundle swapped by the published 0.1.2 image,
`codesign --verify --deep --strict` clean afterwards, image detached, and the
busy-image path shown to reopen the old copy.

Gates: cargo fmt --check clean, `cargo test --lib` 146 passed / 2 ignored,
`pnpm check` clean, `pnpm test` 34 passed, `pnpm build` ok.
2026-10-26 03:41:47 +08:00
mula.liu b732b91ea6 release: 0.1.1 — update channel, settings/UI trims, macOS + Windows x64 only
Update path
- `src-tauri/src/update.rs`: manifest fetch, semver compare, optional ed25519
  signature check against a key baked in at build time, then a size + SHA256
  gate before an installer can run. `UpdateStatus` now reports the artifact key
  it resolved so the UI can name what it will install.
- Settings → Updates panel shows the feed, the check/download state machine, and
  the local OS, architecture and release artifact for this machine.
- `scripts/publish-release.sh` + `scripts/release-key.py` publish installers and a
  signed `shift-update.json` onto an orphan `releases` branch.

Scope trims requested for this release
- Settings: the Radial rings tab is gone, so ring orders are read from
  `settings.json` with no in-app editor for now.
- Main window: the update entry in the header bar is gone; updates live in
  Settings → Updates only.
- Release targets are macOS universal and Windows x64. ARM64 and Linux stay
  buildable and are no longer published; `docs/RELEASE.md` records the decision.

Gates: cargo fmt --check clean, `cargo test --lib` 142 passed / 2 ignored,
`pnpm check` clean, `pnpm test` 34 passed, `pnpm build` ok.
2026-10-26 03:06:46 +08:00
mula.liu b96bb03bbd 修复bug 2026-10-25 18:23:08 +08:00
mula.liu c6eff4e131 修复bug 2026-10-25 12:24:05 +08:00
Shift 3227e7c2d9 hotkeys: duplicate copy stays alive and reports dead hotkeys; live state derives from instance ownership 2026-10-21 10:18:19 +08:00
Shift b47670f391 fix(editor,drag,hotkeys): unified editor header, drop-to-button routing, single-instance hotkey ownership 2026-10-21 10:07:16 +08:00
Shift 0eb75595c6 baseline: capture workspace state (bug fixes in progress) 2026-10-21 08:54:54 +08:00