Preserve local transport identity docs through the reference content migration

Aberta
#792 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 4 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
48/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
markdown, nodejs
Domínio
documentation

Direção de pesquisa

Read the final owning source copies changed by documentation#788 and the companion associated with harper#3755; the payload does not name their file paths. Check that the local identity, migration, token, refresh-token, and session details and the CLI, MQTT, option-summary, and operation links are preserved, along with the 5.4 release note. Done means the companion content is present in the owning sources in the correct migration order, while the application-guide correction remains in learn/.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

content
Documentation area

Current v5 reference and the 5.4 release notes.

Requested follow-up

Preserve the local transport identity documentation companion to harper#3755 through documentation#788, which moves current reference content into the product repositories.

Check the final owning source copies for the built-in local identity, reserved username and existing-user migration, credential-free token selection and 409 response, refresh-token replacement, and session isolation. Preserve the CLI, MQTT, option-summary and operation cross-links, plus the 5.4 release-note entry. The application-guide correction stays in learn/ here.

This is merge-order coordination, not a runtime defect. If the companion lands before #788, include its edits in the migration snapshot. If the migration lands first, carry them into the owning content sources before publishing the companion.

Review-Deferral: 877a0b2b077630ea severity=none category=documentation

Priority: P3. This is a bounded coordination task for an open migration, with no released runtime failure or identified customer block. Effort: Low. No existing content epic specifically owns this migration; no release milestone is committed for this tracking task.

🤖 Generated by OpenAI Codex; posted via @kriszyp.

Linguagem predominante
MDX
Estrelas
9
Forks
9
Merge médio
5d 5h
PRs com merge (30d)
48

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de HarperFast/documentation

Todas as issues de HarperFast/documentation

Issues semelhantes

Mais issues de Documentation

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.