chore: open-source release cleanup

[anandgupta42]

What does this PR do?

Cleans up the repository for open-source release by removing internal files, fixing CI workflows, and standardizing branding.

Removed:

• Internal planning docs (FEATURES_*.md, IMPLEMENTATION_PLAN.md, PLATFORM_ENGINEER_SIMULATION.md, STATS.md)
• Internal scripts (beta.ts, duplicate-pr.ts, stats.ts)
• Internal CI workflows (beta.yml, stats.yml)
• .github/TEAM_MEMBERS (internal employee list)
• .zed/ (single dev editor config)
• docs/design/ (internal product strategy)

Fixed:

• pr-management.yml: removed broken check-duplicates job (referenced deleted script), kept add-contributor-label
• opencode.yml: replaced self-hosted blacksmith runner with ubuntu-latest
• Standardized internal placeholder URLs from opencode.internal → altimate-code.internal

Moved:

• RELEASING.md → docs/RELEASING.md

Type of change

• Chore (maintenance, cleanup, no functional changes)

Issue for this PR

Closes #207

How did you verify your code works?

• Verified all deleted files are internal-only (not referenced by source code or CI)
• Confirmed pr-management.yml retains the useful add-contributor-label job
• Grep confirmed all opencode.internal references updated to altimate-code.internal

Checklist

• I have tested locally and verified my changes work
• I have not included unrelated changes

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review.

[arora-saurabh448]

• Need to Remove or Update -> .github/CODEOWNERS (currently points to opencode users)

• Need to remove or update -> .github/VOUCHED.td

• Verify if the templates are required in .github folder

• experiments/ folder needs to be removed or updated

• github/ folder for Github actions needs to be made consistent - terminal commands still mention altimate-code instead of altimate standalone

• Security.md needs to be updated to remove opencode contact email and put ours instead. It also mentions - Report a Vulnerability tab, which we do not have and the associated link is broken(404). Can either update on the basis of this or remove this section entirely.

• LICENSE - says Copyright Opencode 2025. It should say both -

Copyright (c) 2026 Altimate AI
Copyright (c) 2026 opencode

Kilo also does the same - https://github.com/Kilo-Org/kilocode/blob/main/LICENSE

[arora-saurabh448]

Do we need this file? This has information about removal of files/content as logs.

[anandgupta42]

Good catch! Removed it from tracking and added .github/meta/ to .gitignore. This was a scratch file used for commit messages — shouldn't be committed.

[anandgupta42]

Addressed all review items:

• CODEOWNERS — Keeping for now (will update with team ownership rules separately)
• VOUCHED.td — Removed (upstream contributor vouching file, not relevant to our fork)
• Templates — Verified: bug report, feature request, question, PR template all look good. Keeping as-is.
• experiments/ — Keeping per team decision
• github/ action naming — Already branded as altimate-code throughout. The CLI binary is altimate-code (with altimate as alias), so terminal commands are correct.
• SECURITY.md — Fixed escalation email from security@anoma.ly → security@altimate.ai. Enabled private vulnerability reporting on GitHub so the "Report a Vulnerability" tab works.
• LICENSE — Added dual copyright:

  Copyright (c) 2026 Altimate AI
  Copyright (c) 2025 opencode
  

Also fixed:

• .github/meta/commit.txt removed + gitignored
• altimate_change marker mismatches in config.ts and skill.ts
• Removed beta.yml branding test (file was deleted)

[sentry]

Bug: An extra // altimate_change end comment in config.ts creates a mismatch with start markers, which will cause the CI merge guard test to fail.
_{Severity: HIGH}

Suggested Fix

Remove the extraneous // altimate_change end comment from line 1269 in packages/opencode/src/config/config.ts to ensure the number of 'start' and 'end' markers is equal.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/opencode/src/config/config.ts#L1269

Potential issue: An extra `// altimate_change end` comment was added in `config.ts`,
creating an imbalance with `// altimate_change start` comments. The file now contains 9
'start' markers but 10 'end' markers. This will cause the `upstream-merge-guard.test.ts`
CI check, which validates that these markers are balanced in all TypeScript source
files, to fail. The failure of this automated integrity check will prevent the pull
request from being merged.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: A script executed during the release CI workflow (release.yml) attempts to read the deleted .github/TEAM_MEMBERS file, which will cause the release process to fail.
_{Severity: CRITICAL}

Suggested Fix

Remove the code from packages/script/src/index.ts that reads the now-deleted .github/TEAM_MEMBERS file to prevent the runtime error in the CI release workflow.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: .github/workflows/opencode.yml#L13-L19

Potential issue: The file `.github/TEAM_MEMBERS` was deleted, but the script at
`packages/script/src/index.ts` attempts to read it during module initialization. This
script is a dependency for other build and publish scripts (`build.ts`, `publish.ts`)
that are executed by the `release.yml` CI workflow. When the release workflow runs, it
will trigger the execution of these scripts, leading to a runtime error because the
required file is missing. This will cause the release pipeline to fail.

_{Did we get this right? 👍 / 👎 to inform future reviews.}