chore: Move documentation

[maciaszczykm]

To release documentation, use documentation/v*.*.* tags.

• Use the same aslant configuration and move it here?

Test Plan

Test environment: https://console.your-env.onplural.sh/

Checklist

• I have added a meaningful title and summary to convey the impact of this PR to a user.
• If required, I have updated the Plural documentation accordingly.
• I have added tests to cover my changes.
• I have deployed the agent to a test environment and verified that it works as expected (required only when changing agent code).

Plural Flow: console

[linear]

PROD-5180

[soffi-ai]

Soffi AI Summary

This PR consolidates the monorepo's frontend and documentation workspaces under a new top-level js/ directory, unifying all JavaScript/TypeScript tooling (Yarn workspace, Git hooks, Prettier, CI workflows) into a single root workspace. The change also migrates documentation release automation from an external repository to version tags (documentation/v*.*.*) within this repo, consolidates duplicated GitHub Actions workflows and issue/PR templates, and cleans up several housekeeping items (CODEOWNERS, Renovate config, Makefile targets). The net effect is a simpler, single-workspace frontend monorepo with a cleaner CI/CD surface for both the console app and the documentation site.

---

Updated: 2026-08-31 15:26 UTC

Deploy in Soffi

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​eslint@​8.57.1
	npm/​@​graphql-codegen/​add@​5.0.0
	npm/​@​graphql-codegen/​introspection@​4.0.0
	npm/​eslint-config-next@​15.5.24
	npm/​next@​15.5.24
	npm/​@​react-stately/​select@​3.5.1
	npm/​react-github-btn@​1.4.0
	npm/​@​graphql-codegen/​typescript-operations@​4.0.0
	npm/​@​types/​glob@​8.1.0
	npm/​@​graphql-codegen/​typescript-react-apollo@​3.3.7
	npm/​@​graphql-codegen/​client-preset@​4.0.0
	npm/​@​react-aria/​ssr@​3.6.0
	npm/​@​typescript-eslint/​parser@​7.0.1
	npm/​@​graphql-codegen/​typescript@​4.0.0
	npm/​@​react-stately/​list@​3.8.1
	npm/​eslint-config-prettier@​9.1.0
	npm/​@​styra/​highlightjs-rego@​0.1.2
	npm/​@​react-stately/​selection@​3.19.0
	npm/​react-hooks@​1.0.1
	npm/​@​pluralsh/​eslint-config-typescript@​2.5.183
	npm/​mermaid@​11.12.1
	npm/​deep-freeze@​0.0.1
	npm/​gray-matter@​4.0.3
	npm/​raw-loader@​4.0.2
	npm/​@​graphql-codegen/​cli@​4.0.1
	npm/​react-embed@​3.7.0
	npm/​@​typescript-eslint/​eslint-plugin@​7.0.1
	npm/​stylelint-config-prettier@​9.0.5
	npm/​@​loomhq/​loom-embed@​1.5.0
	npm/​openapi-types@​12.1.3
	npm/​usehooks-ts@​2.9.1
	npm/​@​emotion/​styled@​11.11.0
	npm/​chokidar@​4.0.3
See 32 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @graphql-tools/github-loader is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: js/documentation/package.json → npm/@graphql-codegen/cli@4.0.1 → npm/@graphql-tools/github-loader@8.0.22 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@graphql-tools/github-loader@8.0.22. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @types/node is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: js/documentation/package.json → npm/@pluralsh/eslint-config-typescript@2.5.183 → npm/@types/node@18.19.21 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@types/node@18.19.21. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm damerau-levenshtein is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: js/documentation/package.json → npm/eslint-config-next@15.5.24 → npm/eslint-plugin-jsx-a11y@6.8.0 → npm/@pluralsh/eslint-config-typescript@2.5.183 → npm/damerau-levenshtein@1.0.8 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/damerau-levenshtein@1.0.8. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm ts-api-utils is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: js/documentation/package.json → npm/@typescript-eslint/eslint-plugin@7.0.1 → npm/@typescript-eslint/parser@7.0.1 → npm/@pluralsh/eslint-config-typescript@2.5.183 → npm/ts-api-utils@1.4.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ts-api-utils@1.4.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[github-actions]

Storybook preview: https://6a8c1fbd32d6c1cc8fc131a5-txtebmigoh.chromatic.com/