[bruno-archastro]

Summary

• Make live Ask dashboards discoverable in the core ArchDev skill description and add command examples for generation, personal CRUD, supplied JSX, sharing, and pinning.
• Explain availability (ask --help, user login, and archdev_ask_views), hosted-model sponsorship, and the distinction between personal artifacts and copied Company Room tiles.
• Require permission before publishing personal content, explain per-viewer live data/permissions, and preserve artifact IDs on partial failures. Warn that an unconfirmed room write can already have committed before a retry.
• Regenerate all eight harness skill copies and add a documentation regression test that verifies the workflow and generated copies.

Companion implementation

ArchAstro/firstlanding#18845 adds the CLI command group. This guidance is capability-gated with ask --help: do not assume older installed CLIs support it, upgrade without permission, or configure a local model provider for sponsored Ask generation.

Verification

From tools/plugin-gen:

• npm run build regenerated the bundles.
• npm run check: all 140 generated files match the catalog.
• npm test: 66 passed, 0 failed.
• Whitespace checks passed. No visual changes or live dashboard writes.

Agent session: 01a1517f-1d80-7448-9ede-9a1394f343a0

[bruno-archastro]

Reviewed the server's PR and code-region concerns for 296ef47 (medium).

• Cross-checked every documented command and flag against companion firstlanding#18845: personal creation is the default, create --pin requires --share, supplied JSX skips generation only on create/update, and sharing copies code into the room rather than mutating a private artifact's permissions.
• The skill requires ask --help capability checking and upgrade consent because the companion CLI is not yet released. Existing user login and archdev_ask_views gating are stated explicitly.
• Permission before team publication, per-viewer data access, copied-tile update/delete semantics, and inspecting the board before retrying an uncertain write are all documented. These are behavioral safeguards, not merely command examples.
• The generator check verifies all 140 outputs, and the new regression test verifies wording and byte-identical propagation to all eight harness copies; all 66 plugin tests passed locally and the generated-plugin CI check passed.

All 20 checks now pass. The unrelated macOS zsh installer Ctrl-C test timed out on its first run and passed when only that failed job was rerun on the unchanged head; installer/PTY code was not modified. Human approval is still required. No live dashboard/model requests were made, and the companion implementation remains the authority for runtime behavior.