[ChristopherVR]

What does this change?

Two fixes, one commit each.

Table cells draw no default border (closes #406). Vanilla, Svelte and Vue started every cell from border: 1px solid rgba(255, 255, 255, 0.3), and React gave every cell a border class (border-white/30 in the rawXml renderer, border-gray-400/50 in the structured one). A side the deck gives no border (for example <a:lnL w="0"><a:noFill/></a:lnL>) still drew it and pushed the cell content in by about a pixel. Cells now carry only the borders their style gives, which is what the Angular binding already did. React and Vue keep a faint grid while a table is being edited (React's existing editable branch, and Vue's --editable modifier), so the cells of a borderless table can still be found. Vanilla and Svelte have no editing path, so they draw none.

Tests: vanilla and Svelte assert a plain cell has no border while a cell with an explicit left border keeps it; React asserts no border class on a read-only cell; Vue guards the stylesheet, because scoped SFC CSS is not applied in jsdom.

The ooxml sync can push to the protected main (closes #407). The run in #407 passed every check (all ten packages green); the failing step was Push the bump, rejected with Required status check "ci-success" is expected. main requires that check and only an admin may bypass it, and the reusable workflow pushed with the default token. The caller now passes secrets: inherit, so the repository's existing RELEASE_TOKEN does the push. The reusable workflow in ooxml uses it when present and now reports a refused push as "could not be pushed" instead of a failed verification.

How was it verified?

• Typecheck passes in vanilla, react, vue and svelte (core built first).
• The table tests of all four bindings pass, including the new ones.
• Format and oxlint --deny-warnings pass on the changed files.
• The workflow change can only be confirmed by the next scheduled sync run after this merges.

[github-actions]

Cross-binding parity check

This is advisory only and does not block the PR. It looks at changed file paths, so it cannot tell a genuinely framework-specific change from a parity gap. If it is wrong here, just say so in a comment.

Binding	This PR
React	changed
Vue	changed
Angular	not changed
Svelte	changed
Vanilla	changed

UI source changed in 4 of 5 bindings

Changed: React, Vue, Svelte, Vanilla. Not changed: Angular.

If this is a new UI feature, it needs to land in all five. If it is a fix, please confirm in the PR description whether the other bindings have the same defect, and fix the ones that do. If the change really is framework-specific, say so and this note can be ignored.

Several bindings changed, but packages/shared did not

Parallel edits across bindings with no shared change often mean the same logic was written more than once. Framework-agnostic logic belongs in pptx-viewer-shared, with each binding importing it. View-layer-only changes are a legitimate exception.

Binding UI changed with no framework-neutral e2e spec

Specs in e2e/ run against all five demos, so they are what stops a binding quietly falling behind. New UI features should add or extend one. Fixes covered by unit tests can skip this.

---

See the parity rule for what is expected. Missing: Angular.