Skip to content

The .pfs is the performance - #309

Merged
engmung merged 1 commit into
mainfrom
dev
Aug 15, 2026
Merged

The .pfs is the performance#309
engmung merged 1 commit into
mainfrom
dev

Conversation

@engmung

@engmung engmung commented Aug 15, 2026

Copy link
Copy Markdown
Owner

Upstream made Open/Save in the Director the same .pfs table the panel plays
(SimonePDA 9469220),
and deleted the JSON demos with it. Our design assumed the split that replaced
— JSON as the editable source, .pfs as the build output — so a deck pack
carried both and the UI told people the JSON was the file to keep working on.
That is now untrue, and a file nothing opens is weight in someone's download.

  • Packs carry the table alone.
  • The pattern page's second link is relabelled raw, and described as what
    it is: the same cues for reading or scripting, not something the Director
    opens.
  • Uploads still accept .json — Directors from before the format settled
    saved it.

The stored form stays JSON. It is the site's own canonical shape — what
summaries and validation read, and what regenerates the table on the way out —
and it never had a life outside this server. The comments that called it "the
editable source" now say so.

deck-pack-smoke asserts the table lands and no JSON rides along; the rest
of its checks (modules and catalog.txt untouched, the .pfs decoding back to
the same show, a malformed attachment still leaving an installable pack) are
unchanged and pass, as does performance-smoke.

Also

The three findings we sent upstream have landed there in ca031fb — loader
ABI range, .pfs on install, buffers out of DRAM, plus the stop() hold
release and the clock refresh. Checked against that tree rather than assumed;
our PR was closed as redundant.

…g opens

Upstream made Open/Save in the Director the same .pfs table the panel plays
(SimonePDA 9469220), and dropped the JSON demos with it. Our design assumed
the split it replaced — JSON as the editable source, .pfs as the build
output — so a deck pack carried both and the UI told people the JSON was
the file to keep working on. That is now simply untrue, and a file nothing
opens is weight in someone's download.

Packs carry the table alone. The pattern page's second link is relabelled
"raw" and described as what it is: the same cues for reading or scripting,
not something the Director will open. Uploads still accept .json, because
Directors from before the format settled saved it.

The stored form stays JSON — it is the site's own canonical shape, what
summaries and validation read and what regenerates the table on the way
out, and it never had a life outside this server. The comments that called
it "the editable source" now say so.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pattern-flow-open Ready Ready Preview Aug 15, 2026 12:26pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
pattern-flow_origin Ignored Ignored Aug 15, 2026 12:26pm

@engmung
engmung merged commit 9825215 into main Aug 15, 2026
3 checks passed
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