chore: version 0.8.0 and install pin

- package.json version 0.8.0, README install line #v0.8.0 (L4 CR-01)
- Upgrading from 0.7: the HTML sitemap pages, the catch-all rule and
  seo.htmlSitemap.overCatchAll (L4 WR-04), the post page's article meta
  and the path-form listing segments
- the link:../vue-seo-layer dependency stays until the release swap

README.md

@@ -3,7 +3,7 @@
 A Nuxt 4 layer that renders a Journal blog (post list, post, category, tag and author pages, RSS link) from the Journal API of a SummerCMS application, with its SEO output from the CMS through vue-seo-layer.
 
 ```bash
-pnpm add git+https://git.golem15.com/golem15/vue-journal-layer.git#v0.4.0
+pnpm add git+https://git.golem15.com/golem15/vue-journal-layer.git#v0.8.0
 ```
 
 ## Overview
@@ -265,6 +265,9 @@ The feed's item links come from the Journal API, which links posts under `/blog/
 - **The post title may be a `p`.** With the Journal H1 setting off it renders as `p.journal-post__title`; app CSS that styles `h1` for the title styles `.journal-post__title` or sets the `--journal-post-title-*` tokens.
 - **Breadcrumbs appear** at the top of journal pages. A layout that already renders breadcrumbs sets `journal.breadcrumbs: false`.
 - **Related post cards are `h3`.** CSS that targets `h2.journal-post-card__title` targets the class instead.
+- **HTML sitemap pages.** The layer brings vue-seo-layer's HTML sitemap pages (pl `/mapa-strony`, en `/sitemap` by default, set in `seo.htmlSitemap.paths`). An app that renders its pages through a root catch-all (`pages/[...slug].vue`, as with the pages plugin) gets none, so a CMS page at such a path is not shadowed, unless it sets `seo.htmlSitemap.overCatchAll: true`; an app with its own page at such a path keeps its page; `seo: { htmlSitemap: false }` turns them off. An app without pages of its own (only `app.vue`) gets none and needs no setting.
+- **Post pages keep their article meta.** `og:type` `article`, `article:published_time` and `article:modified_time` come from the post on every post page, also while the CMS answers (the CMS head never carries them); the title, description and `og:image` come from the CMS when it answers.
+- **Path-form listing routes follow vue-seo-layer's segments.** With `seo.pagination.form: 'path'` the listings get `<listing>/strona/:page` and `<listing>/page/:page` from the SEO layer's resolved option (its defaults included), the same segments its pagination links use.
 
 ## Local development
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "vue-journal-layer",
-  "version": "0.7.1",
+  "version": "0.8.0",
   "private": true,
   "type": "module",
   "main": "./nuxt.config.ts",