Skip to content

docs(mcp): reference current NFS-e API contracts and handoff behavior - #25

Open
vitormattos wants to merge 1 commit into
mainfrom
docs/current-mcp-nfse-contract-20261112
Open

vitormattos wants to merge 1 commit into
mainfrom
docs/current-mcp-nfse-contract-20261112

Conversation

@vitormattos

Copy link
Copy Markdown
Member

Scope

  • Fix README link to the integrated akaunting-nfse/main Web/API/domain matrix, rather than an implementation branch.
  • Replace transient epic wording in MCP architecture with a direct description of supported native NFS-e resources.
  • Explain that seven secure browser handoffs provide authenticated navigation, not direct JSON or file execution.
  • Use stable API operation-inventory terminology in the API read contract.

Verification context

Compared the NFS-e current main (99e222483f10eb887ca550b629aa5cc5ac2ac5df) and MCP main (32e9dee2d7c97ba482ce9582d3872d7a859c64d8). Source-only contract consistency review; no runtime OAuth or financial operations performed. No permission changes.

Review gate

  • Independent reviewer checks integration and security semantics.
  • CI and link checks at PR HEAD are inspected.
  • No merge without explicit authorization.

Signed DCO commit through Git Signing MCP.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
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