docs(release): de-branding pass on release workflow docs by A1igator · Pull Request #16 · BackTrackCo/tenjin-agent

A1igator · 2026-07-22T18:34:29Z

Why

The release-bot GitHub App that opens tenjin-agent's version PRs is shared
with BackTrackCo/x402r-sdk: both repos' RELEASE_APP_CLIENT_ID var is the
same value, Iv23liZZg55AR4PICMOH. Owner decision: keep the App shared
across both repos rather than splitting into a dedicated tenjin App, and
give it org-neutral BackTrack branding via an in-place rename to
backtrack-release-bot. This PR is the repo-side de-branding pass; the App
rename itself is a GitHub UI action only the owner can do.

Note: while this PR was open, #19 restructured README.md and moved its
Release section into a new top-level RELEASING.md. This PR was rebased on
that merge; the branding fixes below now live in RELEASING.md and
.github/workflows/release.yml rather than README.md's old Release
section.

Branding fixes (final, post-rebase)

.github/workflows/release.yml (header comment): "Modeled on
BackTrackCo/x402r-sdk's release.yml (the house template); see that repo's
x402r-notes/sdk/RELEASING.md for the operator runbook" -> "Adapted from
BackTrackCo/x402r-sdk's release.yml (the house template); the operator
runbook is this repo's own RELEASING.md".
.github/workflows/release.yml (mid-file comment): "(x402r validates with
publint + attw via test:pkg; tenjin doesn't carry those yet, ...)" ->
"(The house template validates with publint + attw via test:pkg; tenjin
doesn't carry those yet, ...)".
RELEASING.md (Release section, inherited unmodified from docs(readme): CLI-first restructure, staleness fixes #19, already
matching this PR's wording): "adapted from the house template
(BackTrackCo/x402r-sdk)" kept as attribution; the owner-setup step
already read "Install the shared backtrack-release-bot GitHub App on
BackTrackCo/tenjin-agent ... also installed on BackTrackCo/x402r-sdk"
going into the merge, so no further edit was needed there.
README.md: the entire old "## Release" section (including its two
x402r-flavored lines: "This mirrors the house template in
BackTrackCo/x402r-sdk" and "the same x402r-release-bot App used by
x402r-sdk, or an equivalent") was removed by docs(readme): CLI-first restructure, staleness fixes #19's restructure and
replaced with a one-line pointer to RELEASING.md. Nothing left to
de-brand there.

Superseded intermediate wording (from before the shared-App decision and
before #19's restructure, listed here only for the record): README.md's old
owner-setup step 1 briefly read "Install a dedicated release-bot GitHub App
on BackTrackCo/tenjin-agent (permissions: Contents write, Pull requests
write; no webhook needed)"; that text no longer exists in the tree after the
rebase.

Judgment calls

Kept "adapted from / modeled on the house template in
BackTrackCo/x402r-sdk" as a factual provenance note wherever it appears
(release.yml, RELEASING.md). True attribution (the workflow structure
and two-job dispatch pattern were copied from x402r-sdk), not a claim of
ownership over tenjin's release process.
Removed the pointer into x402r-notes/sdk/RELEASING.md as tenjin-agent's
"operator runbook," pointing instead at this repo's own RELEASING.md
(previously the README's Release section, now a dedicated file after
docs(readme): CLI-first restructure, staleness fixes #19).
Confirmed RELEASING.md, brought in by the docs(readme): CLI-first restructure, staleness fixes #19 merge, already describes
the release-bot App as the shared backtrack-release-bot, consistent
with the owner's shared-App decision, so no additional edit was needed
there beyond the release.yml comment fix.
Did not touch RELEASE_APP_CLIENT_ID / RELEASE_APP_PRIVATE_KEY var/secret
names anywhere: those are neutral, and the App rename keeps the client ID
and private key valid, so no var/secret change or reinstall is needed on
either repo.
Left NOTICE.md and the BlockRun MCP attributions (README.md,
src/lib/scan.ts) untouched: genuine unrelated third-party MIT
attribution.
Re-swept the full merged tree for x402r stragglers after the rebase;
the only remaining hits are the two factual attribution lines above.
package.json name/description/repository/homepage/author remain
tenjin-scoped; the x402 keyword there is the protocol name, not x402r
branding.

Owner actions (cannot be done from a repo PR)

Rename the shared release-bot GitHub App to backtrack-release-bot in the
GitHub UI: App settings -> Basic information -> App name. Client ID
Iv23liZZg55AR4PICMOH, the private key, and both installations
(BackTrackCo/tenjin-agent and BackTrackCo/x402r-sdk) all survive the
rename unchanged, so no repo var/secret updates and no reinstalls are needed
on either repo. After the rename, the next Changesets refresh re-authors the
version PR as backtrack-release-bot[bot] on both repos.

Evidence the App is shared today: both BackTrackCo/tenjin-agent and
BackTrackCo/x402r-sdk have RELEASE_APP_CLIENT_ID = Iv23liZZg55AR4PICMOH.

Out of scope

x402r-sdk's own docs and x402r-notes/sdk/RELEASING.md still reference
x402r-release-bot by name and will read stale once the App is renamed.
That's x402r-sdk's repo to fix, not this PR's.

Refs #14
Refs #7

Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01BeThex5KMQmgx6tEE5VU3A

The release-bot GitHub App (client ID Iv23liZZg55AR4PICMOH) is shared with BackTrackCo/x402r-sdk. Point tenjin-agent's operator runbook at this repo's own README instead of x402r-notes, and describe the App as dedicated rather than shared, while keeping the factual "adapted from x402r-sdk" provenance note. Refs #14 Refs #7 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeThex5KMQmgx6tEE5VU3A

Owner decision: the release App stays shared between x402r-sdk and tenjin-agent, renamed to backtrack-release-bot in place, instead of splitting into a dedicated tenjin App. Update the one-time owner setup step to describe installing/using the shared, renamed App rather than a dedicated one. Refs #14 Refs #7 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeThex5KMQmgx6tEE5VU3A

A1igator · 2026-07-23T03:58:57Z

Coordination note: this PR now collides with #19, which moves the README Release section (the exact block this PR rewrites) into a new RELEASING.md. Verified with git merge-tree --write-tree: content conflict in README.md in both merge orders. Whichever lands second carries the other's change: if #19 merges first, this PR gets redone against RELEASING.md (the branding fixes and the shared backtrack-release-bot guidance move there verbatim); if this merges first, #19's section-move should carry this wording into RELEASING.md rather than resurrecting the old x402r references. Also note RELEASING.md in #19 states credentials are already configured; that is now true for the GitHub App side (the bot opens PRs), while the npm-publish environment approval and Trusted Publisher confirmation are still pending owner action.

- 'Adapted from the house template (BackTrackCo/x402r-sdk)' instead of any mirror claim. - Dedicated release-bot framing: install the shared backtrack-release-bot App (Contents write, Pull requests write; no webhook; also on x402r-sdk). - Credentials claim made verifiable, not bald: configured on this repo (gh variable list / gh secret list to verify); the steps stay as a fork / re-setup reference. Captures #16's substance so nothing is lost regardless of merge order. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Adapt the release.yml header comment ("Modeled on ... x402r-sdk's release.yml" becomes "Adapted from the house template") and point the operator runbook at this repo's own RELEASING.md rather than x402r's notes. Neutralize the mid-file validation note ("x402r validates with publint + attw" becomes "The house template validates ..."). Comment-only; no workflow behavior change. Makes #16 fully redundant. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

This reverts commit ee79134.

* docs(readme): restructure CLI-first, drop stale status Lead with the CLI (live on npm) instead of the zero-install fallback. New order: hero, Quickstart, one merged commands table, consent modes and pricing, skills (what install puts in place), a zero-install/remote-MCP fallback for CLI-less agents, output contract, safety model, development, release. - Kill the stale 'early preview / Track A2 not deployed / will not work yet' status blockquote; every command works against production. Merge the two command tables into one shipped-commands table (adds candidate and publish --candidate). - Remove internal ledger references (Track A2, plan 12 decision O1, CLI spec 10); state the rules as plain fact. - Quickstart documents the @Alpha install channel, install, wallet create/fund/show, and a first lookup. - Skills are shipped (not 'soon'); plugin marketplace and tenjin mcp stay the roadmap Next line. Release: owner setup is done on this repo, kept as a re-setup/fork reference. - No em dashes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(readme): audit cuts (extract RELEASING.md, dedupe roadmap, split walls) - Move Development, Release, and one-time owner setup into RELEASING.md (with a short Contributing section for the pnpm check block); README keeps a one-line pointer. Stripped the internal flavor while moving (no 'done on this repo', no house-template name-drop). - Dedupe the roadmap mentions (plugin marketplace + tenjin mcp appeared 4x): keep only the intro one; drop the orphaned Consent 'Next:' block, the skills path-supersede note, and the fallback tenjin-mcp clause. - Consent modes: cut the candidate paragraph that restated Commands-table rows, and compress the committed-.tenjin.json downgrade to one clause; the three mode bullets are unchanged. - Split the post-Commands wall: buy behavior as its own paragraph, and --print-body/--sections as a one-line flags note. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(readme): plain npm install; latest now tracks the current release Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(releasing): hand-carry #16 de-branding into RELEASING.md - 'Adapted from the house template (BackTrackCo/x402r-sdk)' instead of any mirror claim. - Dedicated release-bot framing: install the shared backtrack-release-bot App (Contents write, Pull requests write; no webhook; also on x402r-sdk). - Credentials claim made verifiable, not bald: configured on this repo (gh variable list / gh secret list to verify); the steps stay as a fork / re-setup reference. Captures #16's substance so nothing is lost regardless of merge order. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(release): fold #16 de-branding into release.yml comments Adapt the release.yml header comment ("Modeled on ... x402r-sdk's release.yml" becomes "Adapted from the house template") and point the operator runbook at this repo's own RELEASING.md rather than x402r's notes. Neutralize the mid-file validation note ("x402r validates with publint + attw" becomes "The house template validates ..."). Comment-only; no workflow behavior change. Makes #16 fully redundant. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Revert "docs(release): fold #16 de-branding into release.yml comments" This reverts commit ee79134. --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…se-branding # Conflicts: # README.md

A1igator · 2026-07-24T01:58:28Z

Collision with #19 resolved per the coordination plan: rebased on origin/main, branding edits now live in RELEASING.md and the release.yml comments (the old README Release section moved there in #19); re-swept the merged tree for x402r stragglers, only the two factual attribution lines remain.

A1igator and others added 2 commits July 22, 2026 14:33

This was referenced Jul 23, 2026

feat(publish): unified publish modes, review default #17

Merged

docs(readme): CLI-first restructure, staleness fixes #19

Merged

vraspar added a commit that referenced this pull request Jul 23, 2026

Revert "docs(release): fold #16 de-branding into release.yml comments"

44bcfb3

This reverts commit ee79134.

This was referenced Jul 23, 2026

feat(install): retrieval-instinct nudge in AGENTS.md, opt-in CLAUDE.md (#21) #23

Merged

feat(mcp): local stdio MCP server over the CLI core #24

Merged

Merge remote-tracking branch 'origin/main' into A1igator/tenjin-relea…

269aa4d

…se-branding # Conflicts: # README.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

docs(release): de-branding pass on release workflow docs#16

docs(release): de-branding pass on release workflow docs#16
A1igator wants to merge 3 commits into
mainfrom
A1igator/tenjin-release-branding

A1igator commented Jul 22, 2026 •

edited

Loading

Uh oh!

A1igator commented Jul 23, 2026

Uh oh!

A1igator commented Jul 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

A1igator commented Jul 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Why

Branding fixes (final, post-rebase)

Judgment calls

Owner actions (cannot be done from a repo PR)

Out of scope

Uh oh!

A1igator commented Jul 23, 2026

Uh oh!

A1igator commented Jul 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

A1igator commented Jul 22, 2026 •

edited

Loading