molecule-ai/molecule-core
49
0
Fork 2
Code Issues 145 Pull Requests 157 Actions 5 Packages Projects Releases Wiki Activity

Docs sweep: remove awareness namespace references after #1735 backend removal #1753

New Issue
Closed
opened 2026-05-23 23:56:28 +00:00 by hongming · 0 comments
hongming commented 2026-05-23 23:56:28 +00:00
Owner
Copy Link
Copy Source

Docs sweep: remove "awareness namespace" references after #1735 backend removal

PR #1737 deletes the awareness namespace backend (column, model, provisioner env injection, helpers, INSERTs, tests) but leaves narrative references to "awareness" / AWARENESS_URL / AWARENESS_NAMESPACE scattered through the runtime + architecture docs. The two API spec lines (docs/api-reference.md:106 describing the workspaces row, and docs/api-protocol/platform-api.md:93 claiming workspace creation assigns an awareness_namespace) are patched in #1737 because they would mislead anyone integrating against the workspace-server API.

The remaining ~30 hits below describe awareness as a live feature in handbook-style docs. Wrong post-#1737 merge, but not contract-breaking — file as a docs follow-up so the cleanup runs sequentially without bloating the backend PR.

Files needing edits

Scope File Notes
Architecture docs/architecture/memory.md §4 "Awareness-backed persistence" — delete entirely; remove from the surface-comparison table
Architecture docs/architecture/molecule-technical-doc.md Memory section row + env-var table row reference AWARENESS_URL / AWARENESS_NAMESPACE
Runtime docs/agent-runtime/config-format.md Lists both env vars under optional config
Runtime docs/agent-runtime/workspace-runtime.md Example env blocks reference the vars + claim memory routing through awareness namespace
Runtime docs/agent-runtime/cli-runtime.md Same shape as workspace-runtime.md
Postmortem docs/engineering/postmortem-2026-04-23-boot-event-401.md Minor in-line mention; one-line edit
READMEs README.md, README.zh-CN.md "HMA + awareness namespaces" framing in the architecture diagram; rephrase as "HMA via v2 memory plugin"
Index docs/index.md Cross-reference to memory.md §4

Suggested approach

One sweep PR after #1737 merges. Each file is a small surgical edit — total work ~30 min. Tag area:docs + tier:low. No code change, no migration.

Discovery method (for the future)

git grep -nE "awareness|AWARENESS_(URL|NAMESPACE)" docs/ README*.md plugins/

Refs

  • #1735 (the original awareness-removal RFC)
  • #1737 (the backend removal PR — closes #1735, leaves docs work for this issue)

Out-of-tree assets (no action in this repo)

  • plugins/superpowers/plans/2026-04-08-workspace-awareness-integration.md exists only in operator-cloned trees produced by scripts/clone-manifest.sh. The /plugins/ directory is gitignored in molecule-core, so the file is not version-controlled here. Cleanup belongs in the upstream superpowers plugin repo (or wherever the manifest resolves to) — out of scope for this docs sweep.
# Docs sweep: remove "awareness namespace" references after #1735 backend removal PR #1737 deletes the awareness namespace backend (column, model, provisioner env injection, helpers, INSERTs, tests) but leaves narrative references to "awareness" / `AWARENESS_URL` / `AWARENESS_NAMESPACE` scattered through the runtime + architecture docs. The two **API spec lines** (`docs/api-reference.md:106` describing the `workspaces` row, and `docs/api-protocol/platform-api.md:93` claiming workspace creation assigns an `awareness_namespace`) are patched in #1737 because they would mislead anyone integrating against the workspace-server API. The remaining ~30 hits below describe awareness as a live feature in handbook-style docs. Wrong post-#1737 merge, but not contract-breaking — file as a docs follow-up so the cleanup runs sequentially without bloating the backend PR. ## Files needing edits | Scope | File | Notes | |---|---|---| | Architecture | `docs/architecture/memory.md` | §4 "Awareness-backed persistence" — delete entirely; remove from the surface-comparison table | | Architecture | `docs/architecture/molecule-technical-doc.md` | Memory section row + env-var table row reference `AWARENESS_URL` / `AWARENESS_NAMESPACE` | | Runtime | `docs/agent-runtime/config-format.md` | Lists both env vars under optional config | | Runtime | `docs/agent-runtime/workspace-runtime.md` | Example env blocks reference the vars + claim memory routing through awareness namespace | | Runtime | `docs/agent-runtime/cli-runtime.md` | Same shape as workspace-runtime.md | | Postmortem | `docs/engineering/postmortem-2026-04-23-boot-event-401.md` | Minor in-line mention; one-line edit | | READMEs | `README.md`, `README.zh-CN.md` | "HMA + awareness namespaces" framing in the architecture diagram; rephrase as "HMA via v2 memory plugin" | | Index | `docs/index.md` | Cross-reference to memory.md §4 | ## Suggested approach One sweep PR after #1737 merges. Each file is a small surgical edit — total work ~30 min. Tag `area:docs` + `tier:low`. No code change, no migration. ## Discovery method (for the future) ```bash git grep -nE "awareness|AWARENESS_(URL|NAMESPACE)" docs/ README*.md plugins/ ``` ## Refs - #1735 (the original awareness-removal RFC) - #1737 (the backend removal PR — closes #1735, leaves docs work for this issue) ## Out-of-tree assets (no action in this repo) - `plugins/superpowers/plans/2026-04-08-workspace-awareness-integration.md` exists only in operator-cloned trees produced by `scripts/clone-manifest.sh`. The `/plugins/` directory is gitignored in molecule-core, so the file is not version-controlled here. Cleanup belongs in the upstream `superpowers` plugin repo (or wherever the manifest resolves to) — out of scope for this docs sweep.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#1753
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?