Add Agent Playbook section for automated updates

[stefanvacareanu7]

Summary

• Adds a "Agent Playbook: Updating This Repository End-to-End" section to README.md, documenting how an AI agent (or human) should perform version bumps / updates to this repo (Dockerfile base images, orb versions, sbt seed library), how to test locally with codacy-plugins-test, and the requirement to poll CI until green.
• Documentation only — no other files touched.

Test plan

• README renders correctly (markdown only change)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The PR successfully adds a comprehensive 'Agent Playbook' to the README to guide automated and manual updates. While the content aligns well with the documented intent, there are several procedural errors in the instructions that could lead to build failures or stale updates.

Key issues identified include missing directory transitions when cloning test tools and Docker caching behavior that might prevent fetching latest dependencies. Additionally, the CI polling logic can be simplified using native CLI flags. Codacy reports the PR is up to standards, but these documentation improvements are necessary to ensure the playbook is functional for agents.

Test suggestions

• Verify that all provided sbt test and format commands are correct and executable.
• Verify that the local integration test commands (json, pattern, multiple) reflect the current repo structure.
• Verify that the GitHub CLI command for checking PR status (gh pr checks) is accurate.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that all provided sbt test and format commands are correct and executable.
2. Verify that the local integration test commands (json, pattern, multiple) reflect the current repo structure.
3. Verify that the GitHub CLI command for checking PR status (gh pr checks) is accurate.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🟡 MEDIUM RISK}

Suggestion: The instructions for running the test tool are missing a directory change step after cloning, which will cause the subsequent sbt commands to fail or run in the wrong context.

Suggested change

	5. **Run `codacy-plugins-test` locally** before pushing — clone https://github.com/codacy/codacy-plugins-test and run, per this repo's own README:
	5. **Run `codacy-plugins-test` locally** before pushing — clone https://github.com/codacy/codacy-plugins-test, `cd` into it, and run:

[codacy-production]

_{🟡 MEDIUM RISK}

Suggestion: Docker's layer caching mechanism will reuse the results of the 'go get -u' command from previous builds unless the Dockerfile itself changes. To ensure you are actually building with the latest upstream version of the tool during local development, use the --no-cache flag.

Suggested change

	docker build -t codacy-aligncheck .
	docker build --no-cache -t codacy-aligncheck .