@inditextech/docouture-cli 0.1.0-SNAPSHOT.64.1 → 0.1.0-SNAPSHOT.68.1

package/build/commands/new.js

@@ -450,8 +450,8 @@ function printNextSteps(args) {
     console.log(theme.bold('Docs-authoring skills:'));
     console.log('  npx skills@latest add InditexTech/docouture --all');
     console.log('  (or --skill <name> for one at a time — installs docouture-getting-started,');
-    console.log('  docouture-documenting-changes, docouture-writing-docs-pages, docouture-docs-internals');
-    console.log('  and, for a versioned-mode site, docouture-docs-versioning)');
+    console.log('  docouture-documenting-changes, docouture-authoring-guides, docouture-writing-docs-pages,');
+    console.log('  docouture-docs-internals and, for a versioned-mode site, docouture-docs-versioning)');
     console.log('');
     if (mode === 'versioned') {
         console.log(theme.bold('Versioning: Versioned (Full History)'));

package/build/templates/agent-support/AGENTS.md

@@ -62,11 +62,14 @@ npx skills@latest add InditexTech/docouture --all
 
 - **`docouture-getting-started`** — start here on a brand-new site: scaffolding (if not done
   yet), planning what to document, sourcing content from wherever it actually lives
-  (existing docs, README, or the code itself). Hands off to the two skills below for
-  mechanics once a decision is made.
+  (existing docs, README, or the code itself). Hands off to the skills below for mechanics
+  and content once a decision is made.
 - **`docouture-documenting-changes`** — the re-entry point once the site exists: a feature,
   change, deprecation or fix landed in the repo, and the docs need to catch up. This is
   the one to reach for day to day, not `docouture-getting-started`.
+- **`docouture-authoring-guides`** — what to actually write on each page: purpose, section
+  skeleton, per-section instructions, a copyable AsciiDoc starting point and a quality
+  checklist, for every page in the standard structure plus the home page.
 - **`docouture-writing-docs-pages`** — authoring AsciiDoc content: the language itself,
   `xref:` references, `nav.adoc`, admonitions, code blocks, and this site's own custom
   blocks (`[tabs]`, `[cards]`, `[accordion]`, …).

package/build/templates/workflows/docouture-release.yml

@@ -56,7 +56,6 @@ on:
 
 permissions:
   contents: write
-  pull-requests: write
 
 concurrency:
   group: docouture-release
@@ -371,23 +370,23 @@ jobs:
           git tag -f "$TAG" "$SHA"
           git push origin "refs/tags/${TAG}" --force
 
-      # Versioned only: every version is kept forever, so each one gets a
-      # real Release entry. Standalone deliberately skips this — `docs/stable` is
-      # a rolling pointer with no changelog value of its own, and that mode
-      # keeps no version history to attach one to (see versioning-modes.md).
-      # The delete-then-create is a no-op the first time a version is
-      # released (nothing to delete); on a republish it drops the stale
-      # Release object first so `create` doesn't just fail against one that
-      # already exists.
-      - name: Create GitHub Release
-        if: steps.detect.outputs.mode == 'versioned'
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          TAG: ${{ steps.cut.outputs.tag }}
-          SHA: ${{ steps.cut.outputs.sha }}
-        run: |
-          gh release delete "$TAG" --yes 2>/dev/null || true
-          gh release create "$TAG" --title "$TAG" --generate-notes --target "$SHA"
+      # Neither mode creates a GitHub Release object — `Push release tag` above
+      # is the last step of this dance for both. Versioned mode used to
+      # (`gh release create --generate-notes` here, deleting-then-recreating
+      # on a republish), but that Release was functionally inert: nothing
+      # reads it back — no workflow, no Antora extension, no CLI command; the
+      # version dropdown and `duplicate_latest_version` are driven purely by
+      # the tag itself plus Antora's own ref aggregation (see
+      # versioning-modes.md) — and it polluted the same Releases page/RSS/
+      # watch feed as this repo's real npm semver releases
+      # (code-npm_node-publish-release-and-snapshot.yml), which #166's `docs/`
+      # tag prefix alone didn't fully solve: a Release object still shows in
+      # that list regardless of what its tag is named. `--generate-notes`'s
+      # auto PR-list was dropped outright rather than relocated when this was
+      # removed — its value is already covered by the hand-authored
+      # `release-notes/<version>.adoc` page and the auto-generated
+      # `changelog/index.adoc` (built from CHANGELOG.md at build time). See
+      # GH #172.
 
       # Versioned only, and only on a genuine forward release (not a
       # republish of an already-released version — see "Check for existing

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inditextech/docouture-cli",
-  "version": "0.1.0-SNAPSHOT.64.1",
+  "version": "0.1.0-SNAPSHOT.68.1",
   "description": "Command-line tool for docouture documentation sites: scaffold a new site and set its Antora version outside the monorepo",
   "repository": {
     "type": "git",