<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Todd Schiller - game modding</title><link href="https://toddschiller.com/" rel="alternate"></link><link href="https://toddschiller.com/feeds/tag/game-modding.atom.xml" rel="self"></link><id>https://toddschiller.com/</id><updated>2026-11-06T00:00:00-05:00</updated><subtitle>Human ✘ Artificial Intelligence</subtitle><entry><title>This Week in Extensibility: Epic makes custom progression systems publishable in Fortnite, Glean adds MCP Tasks and Skills, and the W3C Agentic Web group adds a threat model to its charter</title><link href="https://toddschiller.com/blog/this-week-in-extensibility-2026-11-06.html" rel="alternate"></link><published>2026-11-06T00:00:00-05:00</published><updated>2026-11-06T00:00:00-05:00</updated><author><name>Todd Schiller</name></author><id>tag:toddschiller.com,2026-11-06:/blog/this-week-in-extensibility-2026-11-06.html</id><summary type="html">Week of October 31 – November 6, 2026: Epic made custom quest and progression systems publishable in Fortnite's creator platform, Glean added MCP's Tasks and Skills to its assistant, the W3C Agentic Web group added a threat model for pages that try to manipulate a visitor's agent, and Standard Webhooks added a handshake that verifies a webhook endpoint.</summary><content type="html">&lt;!-- markdownlint-disable MD013 --&gt;
&lt;p&gt;Epic made custom quest and progression systems publishable in Fortnite, lifting the
gate that kept islands built on them in development. Glean added MCP's Tasks and
Skills to its assistant, and the W3C Agentic Web group added a
threat model for web pages that try to manipulate or track a visitor's agent.
Standard Webhooks added a handshake that proves a webhook endpoint agreed to receive
events before delivery starts, and Shopify gave app developers a way to test their
network-access rules before they ship.&lt;/p&gt;
&lt;h2&gt;Game modding: Epic makes custom progression systems publishable in Fortnite&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Epic made the Progression API generally available, so Fortnite islands built on
custom quest and progression systems can now be published to other players.&lt;/strong&gt; The
&lt;a href="https://dev.epicgames.com/documentation/fortnite/43-00-fortnite-ecosystem-updates-and-release-notes"&gt;43.00 release on November 1&lt;/a&gt;
takes the interface creators use to build quests, levels, and unlock tracks out of
its experimental stage. Until this release, an island that used it could not be
shipped to other players. The same release
added scripting features to Verse, Epic's creator language, including events that
other code can subscribe to, an experimental timer, and a clock any script can
read, and it gave creators a dashboard that reports how their published islands
perform.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; Epic's creator platform is the layer players use to extend
Fortnite into experiences Epic itself never built, and the Progression API is how a
creator adds quests and leveling to an island. Now a creator can ship an island that
depends on it, widening what reaches Fortnite's audience.&lt;/p&gt;
&lt;h2&gt;Agents and the web: Glean adds MCP Tasks and Skills, and the W3C Agentic Web group adds a threat model&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Glean added support for MCP's Tasks and Skills features to its enterprise
assistant.&lt;/strong&gt; Per the project's
&lt;a href="https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3495"&gt;client-support matrix&lt;/a&gt;
(November 3), Glean now supports Tasks, which lets an agent hand a connected service a
long-running job and come back later for the result, and Skills, which let a connected
service offer reusable capability bundles an agent can load. The matrix lists Tasks
support in Claude, Claude Code, the third-party MCPJam inspector, and now Glean; it is
community-maintained and does not claim to be complete.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The W3C Agentic Web group added a threat model to its draft charter.&lt;/strong&gt; This follows the proposal at the W3C's Dublin gathering last week to
move WebMCP, the draft that lets a web page offer tools a visitor's agent can call,
into a new working group. This week the draft charter gained a section cataloging
what a web page can do to an agent that visits it: feed it bad instructions through
content other users wrote, block it outright, and waste its time with traps built to
stall it. The section also raises how far a site's declared capabilities should be
trusted. A W3C staff contributor
&lt;a href="https://github.com/w3c/charter-drafts/pull/915"&gt;approved the latest additions on November 5&lt;/a&gt;.
Separately, WebMCP's editors, whose draft still runs only in Chromium browsers behind
an origin trial, added a way for a page to
&lt;a href="https://github.com/webmachinelearning/webmcp/pull/254"&gt;declare the shape of a tool's output&lt;/a&gt;
to the agent (November 2). The charter has not yet gone to the member vote that would
create the group.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; Glean now supports the MCP features that turn a one-time request
into a standing job an agent can run and return to, which is agent automation reaching
a product people use at work. On the browser side, the cross-vendor group that would
standardize how a page exposes tools to an agent is still being chartered, and its
threat model now names defending the agent from a hostile page as in scope.&lt;/p&gt;
&lt;h2&gt;Webhooks: Standard Webhooks adds an endpoint-verification handshake&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Standard Webhooks added a handshake that lets a sender confirm an endpoint agreed to
receive events, and holds the shared secret, before it starts delivering.&lt;/strong&gt; On
&lt;a href="https://github.com/standard-webhooks/standard-webhooks/pull/344"&gt;October 30 the cross-vendor convention merged the extension&lt;/a&gt;:
the sender posts a random challenge value to the endpoint, signed like a normal event,
and the endpoint proves itself by echoing back a value derived from the signing key.
Challenge requests are explicitly not events, so a receiver will not mistake the check
for real traffic.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; confirming that an address actually wants a sender's events, and
can prove it holds the key used to sign them, has been left to each vendor to solve its
own way. OpenAI, Anthropic, Twilio, and others already use Standard Webhooks for the
format and signing of webhook payloads. A shared way to verify the endpoint itself
extends that common ground to the step before the first event is sent.&lt;/p&gt;
&lt;h2&gt;Marketplace security: Shopify lets developers test an app's network-access rules before shipping&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Shopify shipped a preview that lets app developers check, on a test store, which
outside servers their app is allowed to contact.&lt;/strong&gt; The
&lt;a href="https://shopify.dev/changelog/posts/test-app-network-access-configuration-on-dev-stores"&gt;November 4 change&lt;/a&gt;
reads the list of outside servers and sites an app has declared and warns in the browser
console when a storefront page reaches something not on the list. It warns; it does not
block. This is the working half of the security package Shopify set out on October 27,
which asks apps to declare where they send data as part of tightening the App Store.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; a Shopify app runs on the developer's own servers, where Shopify
never sees the code, so the platform relies on what an app declares about itself. Giving
developers a way to catch an undeclared connection before they ship helps them meet that
requirement ahead of the 2027 deadlines, when apps that fall short start losing their
listings.&lt;/p&gt;
&lt;h2&gt;Also worth knowing&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Google landed an on-device decision engine as a flag-gated developer trial in Chrome 157.&lt;/strong&gt;
The &lt;a href="https://issues.chromium.org/issues/568193538"&gt;Decisions API&lt;/a&gt; runs fast,
deterministic classification on the device, sorting an input against a fixed set of
options in a single pass, the kind of check a page or extension can use to route or
validate input without a server round trip. It is
&lt;a href="https://chromestatuslite.com/?version=157"&gt;turned on only behind a flag&lt;/a&gt;, on desktop,
and is neither an origin trial nor on by default.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The W3C WebExtensions group drafted the section of its cross-browser extension
standard covering background service workers.&lt;/strong&gt; The
&lt;a href="https://github.com/w3c/webextensions/pull/1173"&gt;in-progress specification&lt;/a&gt; is being filled
in piece by piece; this section defines the background process an extension uses to keep
working when none of its windows are open.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;QuickJS-ng hardened how it isolates guest code.&lt;/strong&gt;
&lt;a href="https://github.com/quickjs-ng/quickjs/releases/tag/v0.18.0"&gt;Version 0.18.0 (November 1)&lt;/a&gt;
of the small JavaScript engine many products embed to run user-supplied scripts made
out-of-memory and internal errors impossible for a guest script to catch, so a
misbehaving script can no longer swallow them and keep running.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CopilotKit locked its in-app assistant interface to a single versioned format.&lt;/strong&gt;
&lt;a href="https://github.com/CopilotKit/CopilotKit/releases/tag/v1.84.0"&gt;Release 1.84.0 (November 3)&lt;/a&gt;
requires the generated assistant UI to use one agreed message format and drops the older
pre-release shapes, a breaking change aimed at keeping the agent and the interface in sync.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;On the radar&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;November 9:&lt;/strong&gt; The WebAssembly Component Model subgroup holds its second meeting.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;November 10:&lt;/strong&gt; JetBrains holds its Plugin Developer Conference.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;November 12:&lt;/strong&gt; The W3C WebExtensions Working Group holds its next call.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;November 17:&lt;/strong&gt; Cloudflare changes a default in how its Workers handle a cancelled request.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mid-to-late November:&lt;/strong&gt; The W3C posts minutes from its Dublin meeting, including the
sessions on WebMCP and the browser-extension platform.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;December 1:&lt;/strong&gt; New Microsoft 365 Copilot Business licenses switch to usage-based billing
by default, and Copilot becomes purchasable without a qualifying base subscription.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;December 18:&lt;/strong&gt; Atlassian stops forwarding Forge's old full-page addresses; apps must move
to the unified building block.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;December 31:&lt;/strong&gt; Cloudflare ends bug and security fixes for the 0.x line of its Sandbox SDK.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;January 1, 2027:&lt;/strong&gt; Shopify delists public apps still using access credentials that never
expire.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;em&gt;This Week in Extensibility is curated by Todd Schiller. Research, drafting, and fact
checking are AI-assisted.&lt;/em&gt;&lt;/p&gt;
</content><category term="Extensibility"></category><category term="extensibility"></category><category term="plugins"></category><category term="sandboxes"></category><category term="web standards"></category><category term="MCP"></category><category term="WebMCP"></category><category term="Fortnite"></category><category term="UEFN"></category><category term="game modding"></category><category term="Glean"></category><category term="webhooks"></category><category term="Shopify"></category><category term="Chrome"></category></entry><entry><title>This Week in Extensibility: Jagex ships an official RuneScape plugin system, Anthropic ships MCP Tasks in Claude, and Obsidian starts delisting plugins that fail its automated review</title><link href="https://toddschiller.com/blog/this-week-in-extensibility-2026-10-30.html" rel="alternate"></link><published>2026-10-30T00:00:00-04:00</published><updated>2026-10-30T00:00:00-04:00</updated><author><name>Todd Schiller</name></author><id>tag:toddschiller.com,2026-10-30:/blog/this-week-in-extensibility-2026-10-30.html</id><summary type="html">Week of October 24 – October 30, 2026: Jagex shipped an official, in-client plugin system for RuneScape, Anthropic shipped MCP's Tasks feature in Claude's apps, Obsidian began delisting community plugins that fail its automated security review, and Cloudflare made an agent's code able to survive a crash and pause for a person's approval.</summary><content type="html">&lt;!-- markdownlint-disable MD013 --&gt;
&lt;p&gt;Jagex gave RuneScape its first sanctioned way to extend the game, a plugin system
built into the client. On letting AI agents operate the apps people already use,
Anthropic shipped MCP's Tasks feature in Claude and Cloudflare let an agent's code
survive a crash and pause for a person's approval. Marketplace owners kept raising
the security bar on the extensions they host: Obsidian started delisting plugins
that fail its automated review, and Shopify set hard 2027 deadlines to retire app
credentials that never expire.&lt;/p&gt;
&lt;h2&gt;Game modding: Jagex ships an official plugin system for RuneScape&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Jagex shipped an official, in-client plugin system for RuneScape,&lt;/strong&gt; the first
sanctioned way to extend the game from inside its own client. It
&lt;a href="https://secure.runescape.com/m=news/runescape-plugins-officially-available-now"&gt;went live on all worlds on October 19&lt;/a&gt;,
with an in-game hub where players browse and install community plugins. The first
batch was five, including a quest helper and a tile marker, but the machinery behind
them matters more. Jagex built an interface for plugins to call, added a scripting
language to the client, and routes every plugin through a moderator queue and
quality-assurance playtesting before it ships
&lt;a href="https://runescape.wiki/w/Plugin"&gt;through the mod.io platform&lt;/a&gt;. Only approved,
mod.io-published plugins run on live worlds; untrusted and in-development ones stay
on separate developer worlds that do not touch a player's account. A plugin
&lt;a href="https://www.pcgamesn.com/runescape/community-plugins"&gt;may not automate gameplay or grant an unfair advantage&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; RuneScape 3 had no equivalent to the third-party overlay client
that Old School RuneScape players have long used, and Jagex has kept outside clients
at arm's length. Building the system into the official client lets the studio offer
reviewed customization while blocking the automation it works against. The hard
problem in a competitive game is separating helping a player from playing for them,
and Jagex has now encoded that boundary in what the interface lets a plugin do.&lt;/p&gt;
&lt;h2&gt;Marketplace security: Shopify sets hard 2027 deadlines to retire app credentials that never expire&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Shopify set hard 2027 deadlines to retire App Store credentials that never expire,
and shipped the security controls it previewed last week.&lt;/strong&gt; On October 27 it
&lt;a href="https://shopify.dev/changelog/blog/app-security-updates-october-2026"&gt;published the schedule and the controls&lt;/a&gt;.
Starting January 1, 2027 a public app still using a non-expiring credential is
delisted and blocked from new installs; on January 15 affected merchants see a
warning; on April 1 the credential stops working on API calls. The controls that
shipped alongside the dates go beyond last week's preview: an app must declare which
outside servers and sites it talks to, developers must verify their identity before
installing on a development or transfer store, and a security hub gives developers a
self-check to run against their own code. The expiring-credential requirement itself
&lt;a href="https://shopify.dev/changelog/posts/expiring-offline-access-tokens-required-for-all-public-apps-as-of-january-1-2027"&gt;dates to May&lt;/a&gt;;
the deadlines are what is new.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; last week's preview now has fixed dates. Hard credential expiry
is a rule Shopify can enforce even though its apps run on the developers' own servers,
where it never sees the code.&lt;/p&gt;
&lt;h2&gt;Plugin directories: Obsidian starts delisting plugins that fail its automated review&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Obsidian began removing community plugins whose latest version fails its automated
security review.&lt;/strong&gt; The note-taking app
&lt;a href="https://obsidian.md/blog/future-of-plugins/"&gt;announced in May&lt;/a&gt; that it would scan
every version of every plugin, not just first submissions, for security problems,
code-quality issues, and malware, and post the result as a public safety scorecard.
It said existing plugins would eventually have to meet the bar but set no date. That
enforcement takes effect on October 31, 2026: a plugin whose current release still
fails is dropped from the directory and can no longer be installed from inside the
app. Copies already installed keep working, and a maintainer can fix the problems and
re-release.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; passing the automated review is now a condition of staying listed,
not a one-time gate at submission. A plugin runs with the app's reach into a user's
notes and files, so whether it still meets the bar is part of what a user trusts when
they install it.&lt;/p&gt;
&lt;h2&gt;Agents and the web: Anthropic ships MCP Tasks in Claude, and WebMCP's incubator proposes a W3C working group&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Anthropic shipped MCP's new Tasks feature in Claude.&lt;/strong&gt;
Last week the MCP project chartered a group to standardize two things: how a connected
service runs a long job for a user's agent, and how it tells the agent when something
changes. This week Claude on the web and Claude Code gained the first half, Tasks,
per the project's
&lt;a href="https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3459"&gt;client support matrix&lt;/a&gt;
(October 28). Tasks lets an agent hand a connected service a long-running job and come
back later for the result, not only quick back-and-forth requests. It is still
pre-stable, and the matrix lists only a few clients with support, Claude alongside the
third-party MCPJam inspector. The companion half, event notifications, is
&lt;a href="https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3415"&gt;still being written&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;And the group incubating the draft WebMCP standard proposed handing it to a new W3C
working group.&lt;/strong&gt; WebMCP is a draft that lets a web page offer tools a visitor's agent can
call. At the W3C's annual gathering in Dublin (October 26 to 28), that group
&lt;a href="https://github.com/w3c/strategy/issues/576"&gt;proposed moving the work&lt;/a&gt; into an Agentic Web
Working Group, whose charter is in review, and a separate session took up
&lt;a href="https://github.com/w3c/tpac2026-breakouts/issues/84"&gt;how WebMCP fits the browser-extension platform&lt;/a&gt;.
The draft charter was &lt;a href="https://github.com/w3c/charter-drafts/pull/901"&gt;broadened during the week&lt;/a&gt;
to cover agent identity and delegation, not only WebMCP, and the editors
&lt;a href="https://github.com/webmachinelearning/webmcp/pull/326"&gt;merged rules&lt;/a&gt; for how a page can
safely let an agent use its tools when embedded in another site. WebMCP still runs only
behind origin trials or experiments in Chromium-based browsers like Chrome, Edge, and
Brave. Firefox has only an early prototype that stays off behind hidden settings, and
Mozilla's position is neutral; Safari does not implement it and Apple opposes it. So none
of this makes it a capability that works across browser engines.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; on the protocol side, an AI agent can already act inside the apps
people use today, even if Tasks is pre-stable and in only a few clients. WebMCP is still
one browser family's origin trial; the W3C proposal would move its design into a
cross-vendor working group. Whether other browsers implement it is the open question.&lt;/p&gt;
&lt;h2&gt;Infrastructure: Cloudflare makes an agent's code survive crashes and pause for approval&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Cloudflare made an agent's code able to survive a crash and pause for a person's
approval.&lt;/strong&gt; On October 26 its framework for running agent code
&lt;a href="https://developers.cloudflare.com/changelog/post/2026-10-26-computer-durable-javascript/"&gt;gained two experimental abilities&lt;/a&gt;:
a run can resume after the service is redeployed or crashes, and it can pause partway
for an outside answer, for example a human approving an action, without the wait
counting against the run's time limit.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; a sandbox running an agent's code on a customer's behalf can now hold
a long or risky task open for human sign-off and pick up where it left off after a
failure, enough for a multi-step workflow a person would trust it with rather than a
single quick action. Durable execution and human-in-the-loop pauses are established in
tools like Temporal and Vercel's Workflow kit; what is new is bringing them to
Cloudflare's agent-code sandbox, still experimental for now.&lt;/p&gt;
&lt;h2&gt;Also worth knowing&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Minecraft shipped a new stable version of the scripting interface its Bedrock add-ons
are built on.&lt;/strong&gt; The &lt;a href="https://learn.microsoft.com/minecraft/creator/scriptapi/minecraft/server/changelog"&gt;October 27 release&lt;/a&gt;
gives add-ons a way to read and control in-game time and its events, plus finer control
over sound and experience points. Bedrock, the edition on consoles and mobile, has a
large player base, and its official add-on interface is a widely used way players
customize the game. The update is incremental.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;MCP defined experimental, beta, and stable stages for its extensions.&lt;/strong&gt; The
&lt;a href="https://github.com/modelcontextprotocol/modelcontextprotocol/pull/3392"&gt;new ladder&lt;/a&gt;,
paired with a twice-yearly release schedule, sets how extensions like Tasks graduate
from experimental to stable. Within days MCP
&lt;a href="https://github.com/modelcontextprotocol/ext-skills/pull/161"&gt;applied it&lt;/a&gt;,
reclassifying its Skills extension, a way for a connected service to offer reusable
capability bundles an agent can load, to beta.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Atlassian added organization-scoped distribution for marketplace apps.&lt;/strong&gt; Developers can
now &lt;a href="https://developer.atlassian.com/platform/forge/changelog/"&gt;restrict a Jira or Confluence app&lt;/a&gt;
so only members of the publisher's own Atlassian organization can install it (October 28).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The password-manager maker Dashlane documented how Chrome's extension model slows its
product down.&lt;/strong&gt; As input to a W3C Dublin discussion on the cross-browser extension platform,
Dashlane &lt;a href="https://github.com/w3c/webextensions/issues/1144"&gt;detailed concrete limits&lt;/a&gt; of the
current model (Manifest V3), including background processes that reload from scratch and
cause delays a user can feel.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CopilotKit now sandboxes embedded assistant widgets by default.&lt;/strong&gt; The toolkit for
building in-app AI assistants &lt;a href="https://github.com/CopilotKit/CopilotKit/releases"&gt;changed its default&lt;/a&gt;
so a third-party interface widget an assistant embeds is isolated and cannot follow links
out of its sandbox.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;On the radar&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;November 3:&lt;/strong&gt; Google releases Chrome 157 to everyone, and the WebAssembly Community Group
discusses how a web page's content security policy applies to WebAssembly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;November 5:&lt;/strong&gt; The W3C's cross-browser extensions group holds its next call.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;November 9:&lt;/strong&gt; The WebAssembly Component Model group holds its second meeting.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mid-to-late November:&lt;/strong&gt; The W3C posts minutes from its Dublin meeting, including the
sessions on WebMCP and the browser-extension platform.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;December 1:&lt;/strong&gt; New Microsoft 365 Copilot Business licenses switch to usage-based billing
by default.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;December 18:&lt;/strong&gt; Atlassian stops forwarding Forge's old full-page addresses; apps must move
to the unified building block.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;December 31:&lt;/strong&gt; Cloudflare ends bug and security fixes for the 0.x line of its Sandbox SDK.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;January 1, 2027:&lt;/strong&gt; Shopify delists public apps still using access credentials that never
expire.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;em&gt;This Week in Extensibility is curated by Todd Schiller. Research, drafting, and fact
checking are AI-assisted.&lt;/em&gt;&lt;/p&gt;
</content><category term="Extensibility"></category><category term="extensibility"></category><category term="plugins"></category><category term="sandboxes"></category><category term="web standards"></category><category term="MCP"></category><category term="WebMCP"></category><category term="RuneScape"></category><category term="game modding"></category><category term="Minecraft"></category><category term="Shopify"></category><category term="Obsidian"></category><category term="Cloudflare"></category><category term="marketplace security"></category></entry></feed>