Skip to content

Update the working docs for the new repository - #1

Merged
bpstack merged 9 commits into
mainfrom
claude/compassionate-planck-gh6aof
Oct 5, 2026
Merged

bpstack merged 9 commits into
mainfrom
claude/compassionate-planck-gh6aof

Conversation

@bpstack

@bpstack bpstack commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Primeros commits en el repositorio nuevo: ponen al día los ficheros de trabajo tras la reescritura del historial y el cambio de repositorio, antes de hacerlo público (fase 4 de docs/ROADMAP.md).

Cambios

  • Hashes (fb877ac): los 176 hashes de commit citados en VERIFY, GITCLEAN, DECISIONS, TODO y SESSION pasan a los del historial reescrito, con el mapa de git-filter-repo.
  • .nvmrc (2b84b0a): Node 22, como piden los engines.
  • TODO.md (aab1848, d197ad6): se cierra «Antes de publicar»; la rotación de credenciales, el borrado de los datos de prueba de Aiven y la versión de Node en Render pasan a «Después de publicar». Sin rutas locales.
  • GITCLEAN.md (2fd2f56): tercera pasada, sus dos auditorías y la publicación en privado; sin rutas locales.
  • ROADMAP.md (5b216a0): fases 1c y 2 cerradas; la 4 es la actual.
  • DECISIONS.md (0f237d0): ADR-036, el original se archiva al final y la rotación va después de publicar.
  • VERIFY.md (2009f39) y SESSION.md (8194031): despliegues desde el repositorio nuevo y estado de la sesión.

Comprobado

  • Vercel desplegó el preview de 8194031 solo, desde este repositorio.
  • Render no despliega: estos commits no tocan backend/.
  • Sin secretos, hosts, IDs de servicios ni rutas locales en lo añadido.

- Replace the 176 commit hashes cited in VERIFY, GITCLEAN, DECISIONS,
  TODO and SESSION with their rewritten equivalents, from the
  filter-repo commit map
- Update the two hashes quoted inside one commit subject in VERIFY

Why: the history rewrite changed every commit hash, so the old
references point to commits that do not exist in this repository.
- Add .nvmrc with 22, matching engines >=22.16.0 in both packages

Why: fnm and nvm pick the right Node version on every machine
without remembering to run fnm use 22.
- Remove "Antes de publicar": the history cleanup resolved the
  database passwords and staff names, and the rest moves below
- Add the credential rotation, the Aiven test data cleanup and the
  Render Node version check to "Después de publicar"
- Point the branch note to the PR #10 merge

Why: the clean history is published; what remains no longer blocks
publication and the rotation procedure stays outside the repository.
…ication

- Record the third rewrite after PR #10, the commits it pruned and the
  identical tip trees
- Record the two independent audits and the empty blob dump lesson
- Record the private repository, the archive rename and the Vercel and
  Render reconnection, and list what is left before going public
- Replace the local working paths with a generic description

Why: the document still ended at the second pass and named local paths
that do not belong in a public repository.
- Describe the harness repository without its path on the main machine

Why: the path names a local user folder and adds nothing for readers
of a public repository.
- Close phases 1c and 2 with a one-line result each; the detail moves
  to the local archive
- Make phase 4 current: the clean history is in the new private
  repository and deploys from it, with the steps left to go public
- Say two branches instead of all branches, as ADR-035 decided

Why: the roadmap still showed phase 1c as current and the publication
of every branch.
- Add ADR-036: archive the original last, after Vercel and Render deploy
  from the new repository; rotate credentials after publishing, with the
  procedure kept outside the repository
- Link ADR-035 and ADR-007 to the decision that revises them
- Replace the local path of the harness templates in ADR-008

Why: the order and the rotation timing changed during the publication
and were not written down; the path names a local user folder.
- Record the manual deploys from bpstack/four-points in production and
  preview, and that the deploy on push is still unchecked
- Add the rows for fb877ac to 0f237d0

Why: the deploys now come from the new repository and the table lists
every commit of the branch.
- Rewrite the state: phases 1c and 2 closed, clean history in the new
  private repository, deploys already switched
- List the steps left to go public and the hooks setup for new clones
- Drop the database dump and private candidate notes, resolved in
  phase 2, and the local machine name

Why: the session still described phase 1c and the old repository.
@vercel

vercel Bot commented Oct 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
four-points Ready Ready Preview Oct 5, 2026 11:04am UTC

@bpstack
bpstack merged commit 2aab36f into main Oct 5, 2026
4 checks passed

This branch was successfully deployed

1 active deployment
Preview — 81940315 Deployed Oct 5, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant