Document Fixed left, Focus, and recent settings

[matthummel-pa]

What does this PR do?

The GitHub README and support docs now match 1.6.15 behavior that is already on main.

• Fixed left docks as an 18rem column inside main (or article) on singular views at min-width: 1100px (wp-singular, single, page, attachment). Archives, the blog index, and smaller screens leave the outline with the content. The header stays put.
• Focus sets html.tocguide-is-focusing and a paper card ("Segoe UI", system-ui, sans-serif). #tocguide-focus-exit shows Show page, Bring the rest back, and Esc. Escape or the button restores the page.
• Resume stays hidden until localStorage key tocguide-bm-{postId} holds a heading in the current outline.
• Settings → TOCguide → Design has a live preview.
• Shortcode attributes confirmed in PHP: close (default on), focus, fixed, theme (inherit, exclude, include), export (Copy, .md, .doc, Print). On/off values are 1, true, yes, and on.

readme.txt is left for PR #41 so this does not conflict with that WordPress.org copy. CHANGELOG.md already records 1.6.4 through 1.6.15, so history was not rewritten and the plugin version was not bumped.

Closes #

Type of change

• Bug fix
• New feature
• Documentation
• Refactor / chore

How was this tested?

Docs-only change. Shortcode names and defaults were checked in includes/class-tocguide-plugin.php. Dock width, breakpoint, singular body classes, Focus exit copy, and the resume key were checked in src/view.js, src/style.scss, src/edit.js, and admin/views/settings.php. The GitHub Pages HTML was not opened in a browser.

Checklist

• npm run build completes without errors
• npm run lint:js and npm run lint:css pass
• Block inserts, live-previews headings, and saves without console errors
• Front-end TOC links scroll to the correct headings (including custom HTML anchors)
• No PHP notices with WP_DEBUG on
• I did not commit node_modules/ or build/
• Docs / readme.txt / CHANGELOG.md updated if behavior changed
• Text domain is the literal string tocguide (not a variable)

  

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 5f4ad970-5ebd-4e92-8f9d-9b70ce6f65ea)