AW12 — Close out the static HTML/CSS engine and defer JavaScript/runtime platform work

[joris97jansen]

Description

Close out Milestone AW and mark Borrowser’s static no-JavaScript HTML/CSS engine as complete for its documented release scope.

This issue should finalize the release tag, update the feature gap tracker, close milestone references, and create or confirm future deferred milestones for JavaScript, dynamic DOM, navigation/history, browser UI, platform security, GPU acceleration, and broader browser behavior.

The goal is to end the static renderer roadmap cleanly without pretending the whole browser is finished.

Requirements

• Add final AW closeout document.

• Confirm all AW release blockers are resolved or explicitly accepted.

• Confirm release packet is complete.

• Confirm support matrix is final for the release.

• Confirm feature gap tracker is updated.

• Confirm release docs are linked.

• Confirm version/tag is created or ready.

• Confirm all AD through AV milestone docs are linked.

• Confirm known limitations are published.

• Confirm public claim language is published.

• Confirm unsupported feature list is published.

• Confirm future deferred milestone list is published.

• Create or confirm future milestone for:

  • JavaScript runtime;

  • DOM bindings;

  • event loop;

  • dynamic DOM mutation;

  • navigation/history;

  • browser UI;

  • full platform accessibility bridge;

  • GPU/backend compositor;

  • service workers/storage APIs;

  • security sandbox/process isolation.

• Explicitly state that AW does not close:

  • complete browser implementation;

  • JavaScript support;

  • full Web Platform compatibility;

  • full UI/browser shell;

  • full security model.

• Prepare final GitHub milestone closeout comment.

• Prepare release announcement draft where scoped.

Exit Criteria

• Milestone AW has a final closeout document.

• Static HTML/CSS engine release scope is complete and documented.

• Release tag/version is ready or created.

• Feature gap tracker reflects AW accurately.

• Known limitations and deferred work are explicit.

• Future JavaScript/runtime/platform milestones are confirmed as separate work.

• The GitHub milestone can be closed.

• Borrowser can honestly claim completion of its documented static no-JavaScript HTML/CSS engine.