DocsCommand.php

Source file: wordpress/hslg-docs-publisher/src/DocsCommand.php

Module: wordpress-hslg-docs-publisher

Size: 21 lines

SHA-256: 4c83fddc775aea502902081e28e4aa46fe2fd0061d8d6509decc46611f35de87

Responsibility

Imports versioned documentation automatically when activated or upgraded; keeps stable WordPress page IDs, ownership metadata, unlimited post revisions and collision protection.

Declared entry points

• HSLG_Docs_Command — source line 4.
• plan — source line 6.
• publish — source line 15.

Imports and dependencies

No direct import declarations detected in this file.

Behaviour and audit locations

Review control flow and returned values in the named source file; no special integration marker was detected.

Optional diagnostic command

This file provides a WP-CLI view of publisher plans and status. It is not the normal publication path: plugin activation or a newer installed bundle should automatically handle page creation and revision updates. Retain it for disaster recovery or read-only diagnosis, where the correct WordPress path and site user have been verified. Do not tell a non-root administrator to publish manually as part of routine releases.

Relationship to the system

This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.

Change verification

Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.