docs(rfc): mark RFC 0029 accepted and drop the private-repo citation

[aaltshuler]

Follow-up to #440 (merged as 12a85966).

Two lifecycle items that belong with the merge rather than with later design adjustments:

1. Status → Accepted. docs/rfcs/README.md specifies that maintainers own the Status field and that it reads Accepted on merge for the public-contribution track. The merged file still said Proposed.
2. Audience neutrality. The diagram prompt cited msftse/azure-architecture-proposal, which an outside reader cannot open — the case AGENTS.md maintenance rule 5 asks to translate into a durable public rationale. The prompt text below the note is already fully self-contained, so the attribution becomes a neutral description of the method. This was raised in review on RFC 0029: native Azure Blob storage #440; the thread was resolved to unblock the merge on the commitment to fix it here.

Docs-only. scripts/check-agents-md.sh passes (74 links, 69 docs).

Greptile Summary

This documentation-only PR marks RFC 0029 as accepted and replaces an inaccessible private-repository citation with an audience-neutral description.

• Updates RFC 0029 lifecycle metadata following its merge.
• Retains the complete reproducible architecture prompt while removing private provenance.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking RFC metadata consistency issue to resolve.

The prompt remains self-contained and audience-neutral, while the RFC status introduces an undocumented parenthesized-date variant rather than using the defined bare Accepted value.

Files Needing Attention: docs/rfcs/0029-azure-blob-storage.md

Important Files Changed

Filename	Overview
docs/rfcs/0029-azure-blob-storage.md	Marks RFC 0029 accepted, but adds an undocumented date suffix to the repository’s defined status value.
docs/rfcs/assets/0029-azure-reference-architecture.prompt.md	Replaces an inaccessible private-repository attribution with a neutral description without changing the self-contained prompt.

_{Reviews (1): Last reviewed commit: "docs(rfc): mark RFC 0029 accepted and dr..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Avoid an undocumented status variant

The RFC process defines the merged status as bare Accepted; adding a parenthesized date creates an undocumented variant and leaves exact status interpretation and the convention for future RFCs ambiguous.

Suggested change

	| **Status** | Accepted (2026-08-05) |
	| **Status** | Accepted |

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!