Skip to content

fix: regenerate Flatpak vendor sources for v0.3.2 - #5

Merged
JDonaghy merged 1 commit into
mainfrom
develop
Mar 11, 2026
Merged

fix: regenerate Flatpak vendor sources for v0.3.2#5
JDonaghy merged 1 commit into
mainfrom
develop

Conversation

@JDonaghy

Copy link
Copy Markdown
Owner

Summary

  • Regenerate flatpak/cargo-sources.json to match Cargo.lock (libc 0.2.182 → 0.2.183)
  • Includes all develop commits since v0.3.1 merge

The v0.3.2 release workflow's Flatpak job failed because cargo-sources.json vendored libc-0.2.182 but Cargo.lock requires libc-0.2.183. Merging this PR will re-trigger the release workflow and upload vimcode.flatpak to the existing v0.3.2 release.

Test plan

  • Release workflow Flatpak job passes after merge
  • vimcode.flatpak appears in v0.3.2 release assets

🤖 Generated with Claude Code

Cargo.lock requires libc-0.2.183 but cargo-sources.json vendored
libc-0.2.182, causing the Flatpak build to fail on `cargo --offline fetch`.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@JDonaghy
JDonaghy merged commit 9773371 into main Mar 11, 2026
4 checks passed
JDonaghy added a commit that referenced this pull request Jun 26, 2026
…ence

Capture the primary objective — eliminate all platform-specific code from
vimcode and lift it into quadraui — in a coordinator-style living GOALS.md,
and reference it from a new "Current Goal — read first" section at the top of
CLAUDE.md. Documents the build (#5) vs adopt (#7 Platform-Neutral) milestone
split and the ready-now vs blocked-on-quadraui sequencing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
JDonaghy added a commit that referenced this pull request Jul 11, 2026
…ence

Capture the primary objective — eliminate all platform-specific code from
vimcode and lift it into quadraui — in a coordinator-style living GOALS.md,
and reference it from a new "Current Goal — read first" section at the top of
CLAUDE.md. Documents the build (#5) vs adopt (#7 Platform-Neutral) milestone
split and the ready-now vs blocked-on-quadraui sequencing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
JDonaghy added a commit that referenced this pull request Sep 5, 2026
…E.md

A four-agent audit of develop @ ee26268 found these planning docs materially
stale, in ways that actively misdirect work:

- The "#47 closed with blocker filed nowhere" claim was already false by the
  time the revision carrying it was written: quadraui#699 was filed and
  closed within the same 33-minute window (2026-09-03 16:38Z-17:11Z), and
  vimcode#47 was reopened into milestone #5 at 16:38Z. quadraui milestone #9
  was never closed either, so the "re-open it" instruction was acting on a
  wrong premise.
- The "44 call sites" figure conflated every use of the `backend` field with
  the two Rc-handle methods actually in question. Real count, verified at
  ee26268: 19 (modal_stack_handle x12, drag_state_handle x7).
- GOALS.md §2's "duplication moved down a level into quadraui" claims (1,671
  byte-identical lines, EventOutcome declared twice, 7 private UTF-8 copies,
  no desktop/, etc.) were checked against quadraui's pinned rev and mostly
  don't hold up; quadraui#481's own correction comment had already withdrawn
  the headline number.
- The post-#735 size table's src/gtk/ column (9,650) predated #785's move of
  struct App into src/app.rs. Regenerated all columns at ee26268 with
  scripts/prod_lines.py and added the src/app.rs row.
- docs/IRREDUCIBLE_SURFACE.md's folder-picker verdict was wrong, not just
  stale: quadraui::compose::FolderPickerController has existed since
  2026-05-25 and its module doc already instructs vimcode to adopt it. Struck
  the row and added a caveat on how thin the unit_w/unit_h seam actually is
  (7 signatures, two explicit char_width > 1.0 sniffs).

Every regenerated number is cited with the script and revision it was
measured at, per GOALS.md's own "regenerate, don't trust a number typed into
prose" rule. Pure documentation change, no code touched.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant