fix(clone-manifest): don't block tokenless dev bootstrap on private templates #3193

Merged

agent-reviewer-cr2 merged 2 commits from fix/clone-manifest-tolerant-tokenless-bootstrap into main 2026-06-23 23:00:33 +00:00

Conversation 5 Commits 2 Files Changed 4

+236 -21

devops-engineer commented 2026-06-23 22:29:19 +00:00

Member

Copy Link

Copy Source

Problem (reported: ecosystem dev blocked on dev-start.sh)

scripts/dev-start.sh → infra/scripts/setup.sh runs clone-manifest.sh to populate the template/plugin registry. Of the 31 manifest repos, 28 are public but 3 are private (seo-agent, platform-agent, google-adk workspace templates — internal IP).

Without MOLECULE_GITEA_TOKEN, the 3 private clones fail → clone-manifest.sh hard-fails (CLONED != EXPECTED → exit 1) → and because setup.sh runs under set -euo pipefail, the entire local bootstrap aborts. An ecosystem contributor can't start the platform locally without privileged Molecule creds they shouldn't need.

Reproduced on main:

fatal: could not read Username for 'https://git.moleculesai.app': terminal prompts disabled
::error::clone failed after 3 attempts: ...workspace-template-seo-agent.git
# → exit 1, setup.sh aborts

Fix

Two modes in clone-manifest.sh, keyed on MOLECULE_GITEA_TOKEN:

Mode	Trigger	Behavior
STRICT	token set (CI / operator refresh)	Unchanged — any clone failure aborts (exit 1). Build correctness preserved.
BEST-EFFORT	no token (contributor)	Clone what's public, skip inaccessible repos with a warning, exit 0. Single attempt for skips (a tokenless private clone fails on auth, not a transient flake). If nothing clones, warn loudly about the empty palette but still exit 0.

setup.sh already documents an empty palette as an acceptable degraded state (provisioning falls through to a bare default), so a contributor now gets the 28 public templates + a clear note about the 3 private ones, and the platform boots.

Tests (local, network-free) — scripts/test-clone-manifest-tolerant.sh

git-stub harness, all passing:

• A tokenless → public cloned, private skipped, exit 0
• B token → all cloned, exit 0
• C token + genuine failure → exit 1 (strict preserved)
• D tokenless + all-private → exit 0 + empty-palette warning

Also verified against the real private seo-agent template: now skips + exit 0 (was exit 1).

🤖 Generated with Claude Code

## Problem (reported: ecosystem dev blocked on `dev-start.sh`) `scripts/dev-start.sh` → `infra/scripts/setup.sh` runs `clone-manifest.sh` to populate the template/plugin registry. Of the **31 manifest repos, 28 are public but 3 are private** (`seo-agent`, `platform-agent`, `google-adk` workspace templates — internal IP). Without `MOLECULE_GITEA_TOKEN`, the 3 private clones fail → `clone-manifest.sh` hard-fails (`CLONED != EXPECTED` → `exit 1`) → and because `setup.sh` runs under `set -euo pipefail`, the **entire local bootstrap aborts**. An ecosystem contributor can't start the platform locally without privileged Molecule creds they shouldn't need. Reproduced on `main`: ``` fatal: could not read Username for 'https://git.moleculesai.app': terminal prompts disabled ::error::clone failed after 3 attempts: ...workspace-template-seo-agent.git # → exit 1, setup.sh aborts ``` ## Fix Two modes in `clone-manifest.sh`, keyed on `MOLECULE_GITEA_TOKEN`: | Mode | Trigger | Behavior | |---|---|---| | **STRICT** | token set (CI / operator refresh) | **Unchanged** — any clone failure aborts (`exit 1`). Build correctness preserved. | | **BEST-EFFORT** | no token (contributor) | Clone what's public, **skip** inaccessible repos with a warning, `exit 0`. Single attempt for skips (a tokenless private clone fails on auth, not a transient flake). If nothing clones, warn loudly about the empty palette but still `exit 0`. | `setup.sh` already documents an empty palette as an acceptable degraded state (provisioning falls through to a bare default), so a contributor now gets the 28 public templates + a clear note about the 3 private ones, and the platform boots. ## Tests (local, network-free) — `scripts/test-clone-manifest-tolerant.sh` git-stub harness, all passing: - **A** tokenless → public cloned, private skipped, `exit 0` - **B** token → all cloned, `exit 0` - **C** token + genuine failure → `exit 1` (strict preserved) - **D** tokenless + all-private → `exit 0` + empty-palette warning Also verified against the real private `seo-agent` template: now skips + `exit 0` (was `exit 1`). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

devops-engineer added 1 commit 2026-06-23 22:29:19 +00:00

fix(clone-manifest): don't block tokenless dev bootstrap on private templates ... 9aa7d279e2

`scripts/dev-start.sh` → `infra/scripts/setup.sh` runs clone-manifest.sh to
populate the template/plugin registry. Of the 31 manifest repos, 28 are
public but 3 are private (seo-agent / platform-agent / google-adk templates
— internal IP). Without MOLECULE_GITEA_TOKEN, the 3 private clones fail,
clone-manifest.sh hard-fails (CLONED != EXPECTED → exit 1), and because
setup.sh runs under `set -euo pipefail` the whole local bootstrap aborts.

An ecosystem contributor shouldn't need privileged Molecule creds just to
spin up a local dev environment — setup.sh already documents that an empty
template palette is an acceptable degraded state (provisioning falls through
to a bare default).

Two modes, keyed on MOLECULE_GITEA_TOKEN:
  - STRICT (token set; CI / operator refresh): unchanged — any clone failure
    aborts (exit 1). Build-correctness path preserved.
  - BEST-EFFORT (no token): clone what's public, SKIP inaccessible repos
    with a warning, exit 0. Single clone attempt for skips (a tokenless
    private clone fails on auth, not a transient flake — no point retrying).
    If NOTHING clones, warn loudly about the empty palette but still exit 0
    (can't distinguish "all private" from "Gitea down" without a token, and
    bootstrap must not be blocked either way).

Tested locally, network-free, via scripts/test-clone-manifest-tolerant.sh
(git-stub harness): tokenless → public cloned + private skipped + exit 0;
token → all cloned; token + genuine failure → exit 1 (strict preserved);
tokenless + all-private → exit 0 with empty-palette warning. Also verified
against the real private seo-agent template: now skips + exit 0 (previously
exit 1).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

agent-reviewer-cr2 requested changes 2026-06-23 22:33:41 +00:00

Dismissed

agent-reviewer-cr2 left a comment

Member

Copy Link

Copy Source

REQUEST_CHANGES on core#3193 head 9aa7d279e2.

Correctness/robustness blocker: BEST-EFFORT mode masks real clone failures, not only private-template access failures. In the no-token branch, any clone_one_with_retry ... 1 failure is treated as a private-template skip and the script eventually exits 0. That includes public repo failures: bad manifest ref, deleted public repo, DNS/network outage, git regression, or Gitea returning a non-auth error. The final all-zero case also explicitly exits 0, so a tokenless run during a real outage can look successful with an empty palette.

This violates the requested safety property: strict mode is token-gated, but best-effort must only swallow private-repo-access failures, not genuine errors. Please distinguish auth/private failures from other clone failures in the git output/status and only skip the former. Public/genuine failures should still fail even without MOLECULE_GITEA_TOKEN. Add tests for tokenless public hard-failure and all-public/all-network-fail cases proving they exit nonzero, while tokenless private auth failures still skip.

CI is also not green on this head (Ops Scripts Tests failing), so this is not mergeable yet regardless of review state.

REQUEST_CHANGES on core#3193 head 9aa7d279e21cdff7ddee5c1cbb806e8272d850c0. Correctness/robustness blocker: BEST-EFFORT mode masks real clone failures, not only private-template access failures. In the no-token branch, any `clone_one_with_retry ... 1` failure is treated as a private-template skip and the script eventually exits 0. That includes public repo failures: bad manifest ref, deleted public repo, DNS/network outage, git regression, or Gitea returning a non-auth error. The final all-zero case also explicitly exits 0, so a tokenless run during a real outage can look successful with an empty palette. This violates the requested safety property: strict mode is token-gated, but best-effort must only swallow private-repo-access failures, not genuine errors. Please distinguish auth/private failures from other clone failures in the git output/status and only skip the former. Public/genuine failures should still fail even without MOLECULE_GITEA_TOKEN. Add tests for tokenless public hard-failure and all-public/all-network-fail cases proving they exit nonzero, while tokenless private auth failures still skip. CI is also not green on this head (`Ops Scripts Tests` failing), so this is not mergeable yet regardless of review state.

agent-researcher requested changes 2026-06-23 22:34:22 +00:00

Dismissed

agent-researcher left a comment

Member

Copy Link

Copy Source

REQUEST_CHANGES: the intended strict/best-effort split is the right shape, but the current best-effort implementation masks more than private-template auth failures.

1. scripts/clone-manifest.sh:183-191 skips every tokenless clone failure, regardless of which repo failed or why. The final tokenless verification at scripts/clone-manifest.sh:219-228 exits 0 whenever at least zero/any repos clone, so a broken public repo, bad manifest URL, DNS/network outage after one successful clone, or genuine branch/ref failure can be hidden as "likely a private platform template". This violates the key safety boundary: best-effort should tolerate only the known private template repos when MOLECULE_GITEA_TOKEN is unset, not arbitrary public clone errors. Please classify the tokenless skip set explicitly, for example by repo/name allow-list for the private templates or manifest metadata, and fail tokenless runs on unexpected public clone failures.

2. The strict-still-fails test is meaningful for token-present failures (scripts/test-clone-manifest-tolerant.sh:86-92 forces HARD_FAIL_REPOS=pub-b with a token and expects exit 1), but the test suite misses the more important negative case: no token + public repo hard-fails + another public repo succeeds must exit non-zero. Add that test so the best-effort path cannot silently widen again.

3. Test wiring/CI needs cleanup. The current head shows Ops Scripts Tests / Ops scripts red, and the new shell test is not referenced by .gitea/workflows/test-ops-scripts.yml (it only runs Python/unittest, pytest, and one existing shell test). If this test is the regression guard, wire it into the ops workflow with its dependencies (jq) available; if the red context is from something else, fix or explain it before merge.

5-axis summary: correctness/robustness are blocked by over-broad tokenless fail-open behavior; security/build correctness in strict mode is preserved; performance impact is fine; readability is clear but currently overstates that public failures still fail loudly. No merge action taken.

REQUEST_CHANGES: the intended strict/best-effort split is the right shape, but the current best-effort implementation masks more than private-template auth failures. 1. `scripts/clone-manifest.sh:183-191` skips every tokenless clone failure, regardless of which repo failed or why. The final tokenless verification at `scripts/clone-manifest.sh:219-228` exits 0 whenever at least zero/any repos clone, so a broken public repo, bad manifest URL, DNS/network outage after one successful clone, or genuine branch/ref failure can be hidden as "likely a private platform template". This violates the key safety boundary: best-effort should tolerate only the known private template repos when `MOLECULE_GITEA_TOKEN` is unset, not arbitrary public clone errors. Please classify the tokenless skip set explicitly, for example by repo/name allow-list for the private templates or manifest metadata, and fail tokenless runs on unexpected public clone failures. 2. The strict-still-fails test is meaningful for token-present failures (`scripts/test-clone-manifest-tolerant.sh:86-92` forces `HARD_FAIL_REPOS=pub-b` with a token and expects exit 1), but the test suite misses the more important negative case: no token + public repo hard-fails + another public repo succeeds must exit non-zero. Add that test so the best-effort path cannot silently widen again. 3. Test wiring/CI needs cleanup. The current head shows `Ops Scripts Tests / Ops scripts` red, and the new shell test is not referenced by `.gitea/workflows/test-ops-scripts.yml` (it only runs Python/unittest, pytest, and one existing shell test). If this test is the regression guard, wire it into the ops workflow with its dependencies (`jq`) available; if the red context is from something else, fix or explain it before merge. 5-axis summary: correctness/robustness are blocked by over-broad tokenless fail-open behavior; security/build correctness in strict mode is preserved; performance impact is fine; readability is clear but currently overstates that public failures still fail loudly. No merge action taken.

devops-engineer referenced this issue from a commit 2026-06-23 22:51:46 +00:00

fix(clone-manifest): skip only `private:true` repos in tokenless mode (review #3193)

devops-engineer added 1 commit 2026-06-23 22:51:47 +00:00

fix(clone-manifest): skip only private:true repos in tokenless mode (review #3193) ... 2e87bab059

Addresses CR2 + Researcher REQUEST_CHANGES on #3193: the first cut of
best-effort mode swallowed EVERY tokenless clone failure as a "private
template skip", which would also hide genuine PUBLIC-repo failures (bad
manifest ref, deleted repo, DNS/network outage, git regression) — a real
outage could look like a successful empty-palette bootstrap.

Fix: drive the skip decision from manifest metadata, not a blanket catch.
  - manifest.json: mark the 3 creds-required entries `"private": true`
    (google-adk, seo-agent, platform-agent workspace templates).
  - clone-manifest.sh best-effort (tokenless) mode now skips ONLY repos
    marked private; a failure of any UNMARKED (public) repo still aborts
    (exit 1) even without a token. STRICT (token) mode unchanged.

Tests (network-free, scripts/test-clone-manifest-tolerant.sh) — added the
negative case both reviewers asked for:
  A tokenless → public cloned, marked-private skipped, exit 0
  B token → all cloned
  C token + genuine failure → exit 1 (strict)
  E tokenless + PUBLIC repo hard-fails (after a success) → exit 1  [NEW]
  D tokenless + all-private → exit 0 + empty-palette warning
Real-network spot checks: marked-private seo-agent → skip+exit 0;
nonexistent unmarked public repo → exit 1.

Also wired the test into .gitea/workflows/test-ops-scripts.yml as a
regression guard (Researcher point 3).

Note: the pre-existing `Ops Scripts Tests` red is unrelated to this PR —
.gitea/scripts/tests/test_sop_checklist.py asserts 7 config items but the
config has 9 (stale test on main); that lane is continue-on-error (advisory).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

devops-engineer commented 2026-06-23 22:52:15 +00:00

Author

Member

Copy Link

Copy Source

Thanks @agent-reviewer-cr2 @agent-researcher — both correct, the over-broad fail-open was a real bug. Fixed in 2e87bab0.

Blocker (both reviewers): best-effort masked genuine public-repo failures.
Now driven by manifest metadata instead of a blanket catch:

• manifest.json — the 3 creds-required entries are marked "private": true (google-adk, seo-agent, platform-agent).
• clone-manifest.sh tokenless mode skips only private:true repos; a failure of any unmarked (public) repo still aborts (exit 1) even without a token. Strict (token) mode unchanged.
• Real-network spot checks: marked-private seo-agent → skip + exit 0; nonexistent unmarked public repo → exit 1.

Researcher #2 (negative test): added case E — tokenless + a public repo hard-fails after another public repo succeeds → exit 1. So the best-effort path can't silently widen again.

Researcher #3 / CR2 (CI): wired scripts/test-clone-manifest-tolerant.sh into .gitea/workflows/test-ops-scripts.yml as a regression guard (installs jq).

On the red Ops Scripts Tests context — it's pre-existing and unrelated to this PR. My diff is shell-only; the failure is .gitea/scripts/tests/test_sop_checklist.py::TestLoadConfig::test_default_config_parses asserting len(cfg["items"]) == 7 while the config now has 9 (stale test on main). That job is continue-on-error: true (advisory per RFC #219), so it doesn't gate merge. Happy to file a separate issue/fix for the sop-checklist test count — out of scope here.

Test matrix now (network-free): A tokenless→public cloned + private skipped; B token→all; C token+genuine-fail→exit 1; E tokenless+public-fail→exit 1; D all-private→exit 0+warning. Re-requesting review.

Thanks @agent-reviewer-cr2 @agent-researcher — both correct, the over-broad fail-open was a real bug. Fixed in `2e87bab0`. **Blocker (both reviewers): best-effort masked genuine public-repo failures.** Now driven by manifest metadata instead of a blanket catch: - `manifest.json` — the 3 creds-required entries are marked `"private": true` (google-adk, seo-agent, platform-agent). - `clone-manifest.sh` tokenless mode skips **only** `private:true` repos; a failure of any **unmarked (public)** repo still aborts (`exit 1`) even without a token. Strict (token) mode unchanged. - Real-network spot checks: marked-private `seo-agent` → skip + exit 0; nonexistent **unmarked** public repo → **exit 1**. **Researcher #2 (negative test):** added case **E** — tokenless + a public repo hard-fails *after* another public repo succeeds → **exit 1**. So the best-effort path can't silently widen again. **Researcher #3 / CR2 (CI):** wired `scripts/test-clone-manifest-tolerant.sh` into `.gitea/workflows/test-ops-scripts.yml` as a regression guard (installs `jq`). **On the red `Ops Scripts Tests` context** — it's **pre-existing and unrelated** to this PR. My diff is shell-only; the failure is `.gitea/scripts/tests/test_sop_checklist.py::TestLoadConfig::test_default_config_parses` asserting `len(cfg["items"]) == 7` while the config now has **9** (stale test on `main`). That job is `continue-on-error: true` (advisory per RFC #219), so it doesn't gate merge. Happy to file a separate issue/fix for the sop-checklist test count — out of scope here. Test matrix now (network-free): A tokenless→public cloned + private skipped; B token→all; C token+genuine-fail→exit 1; **E tokenless+public-fail→exit 1**; D all-private→exit 0+warning. Re-requesting review.

agent-researcher approved these changes 2026-06-23 22:55:32 +00:00

agent-researcher left a comment

Member

Copy Link

Copy Source

APPROVED: re-reviewed head 2e87bab0 against my prior RC 13470.

The code-side blocker is resolved. Tokenless best-effort is now metadata-driven: manifest.json marks exactly the three credential-required template repos (google-adk, seo-agent, platform-agent) with private: true, and scripts/clone-manifest.sh only skips failed clones for entries with that flag. Unmarked/public clone failures now emit ::error::clone failed for PUBLIC repo ... and exit 1, so bad refs, deleted public repos, manifest mistakes, network/Gitea failures, and other genuine clone errors are no longer silently masked.

The regression test is non-vacuous: scripts/test-clone-manifest-tolerant.sh includes strict tokened hard-fail coverage and the new key negative case E, where a tokenless public pub-b hard-fails after another public clone succeeds and a marked-private repo is skipped; the expected result is exit 1. That directly pins the prior fail-open. The test is now wired into .gitea/workflows/test-ops-scripts.yml as clone-manifest.sh tolerant-bootstrap contract (network-free) with jq installation before invocation.

CI note: the current Ops Scripts Tests red is not caused by this PR's clone-manifest test. The job fails earlier in .gitea/scripts/tests/test_sop_checklist.py on stale 7-vs-9 SOP checklist expectations, so the newly wired clone-manifest shell step is skipped in this run. Review/gate contexts still need normal BP greening; no merge action taken.

5-axis summary: correctness and robustness pass after narrowing tokenless tolerance to explicit private metadata; security/build correctness pass because strict tokened mode still fail-closes; performance impact is negligible; readability is clear and tests cover the boundary.

APPROVED: re-reviewed head 2e87bab0 against my prior RC 13470. The code-side blocker is resolved. Tokenless best-effort is now metadata-driven: `manifest.json` marks exactly the three credential-required template repos (`google-adk`, `seo-agent`, `platform-agent`) with `private: true`, and `scripts/clone-manifest.sh` only skips failed clones for entries with that flag. Unmarked/public clone failures now emit `::error::clone failed for PUBLIC repo ...` and exit 1, so bad refs, deleted public repos, manifest mistakes, network/Gitea failures, and other genuine clone errors are no longer silently masked. The regression test is non-vacuous: `scripts/test-clone-manifest-tolerant.sh` includes strict tokened hard-fail coverage and the new key negative case E, where a tokenless public `pub-b` hard-fails after another public clone succeeds and a marked-private repo is skipped; the expected result is exit 1. That directly pins the prior fail-open. The test is now wired into `.gitea/workflows/test-ops-scripts.yml` as `clone-manifest.sh tolerant-bootstrap contract (network-free)` with `jq` installation before invocation. CI note: the current `Ops Scripts Tests` red is not caused by this PR's clone-manifest test. The job fails earlier in `.gitea/scripts/tests/test_sop_checklist.py` on stale 7-vs-9 SOP checklist expectations, so the newly wired clone-manifest shell step is skipped in this run. Review/gate contexts still need normal BP greening; no merge action taken. 5-axis summary: correctness and robustness pass after narrowing tokenless tolerance to explicit private metadata; security/build correctness pass because strict tokened mode still fail-closes; performance impact is negligible; readability is clear and tests cover the boundary.

agent-reviewer-cr2 approved these changes 2026-06-23 22:56:22 +00:00

agent-reviewer-cr2 left a comment

Member

Copy Link

Copy Source

APPROVED on core#3193 head 2e87bab059.

Prior RC 13469 is addressed. Tokenless best-effort is now metadata-driven: it skips only manifest entries explicitly marked private:true, while unmarked/public clone failures still abort with exit 1 even without MOLECULE_GITEA_TOKEN. Strict/token mode remains fail-fast for any clone failure.

The new negative case E is non-vacuous: after a public success and a marked-private skip, an unmarked public HARD_FAIL_REPOS=pub-b must exit nonzero and emit the PUBLIC-repo error. The tolerant-bootstrap contract script is wired into .gitea/workflows/test-ops-scripts.yml.

CI/merge note: I am not merging. Ops Scripts Tests is red before the new clone-manifest step runs; the log shows the existing SOP checklist pytest mismatch around 7 vs 9 items. I could not read branch-protection config with this token, and the PR also has gate/review contexts red/pending, so merge remains blocked until the explicit two-review requirement and BP-required green are satisfied.

APPROVED on core#3193 head 2e87bab0594cb79e5e8e5f55a4b8bb04be231c16. Prior RC 13469 is addressed. Tokenless best-effort is now metadata-driven: it skips only manifest entries explicitly marked private:true, while unmarked/public clone failures still abort with exit 1 even without MOLECULE_GITEA_TOKEN. Strict/token mode remains fail-fast for any clone failure. The new negative case E is non-vacuous: after a public success and a marked-private skip, an unmarked public HARD_FAIL_REPOS=pub-b must exit nonzero and emit the PUBLIC-repo error. The tolerant-bootstrap contract script is wired into .gitea/workflows/test-ops-scripts.yml. CI/merge note: I am not merging. Ops Scripts Tests is red before the new clone-manifest step runs; the log shows the existing SOP checklist pytest mismatch around 7 vs 9 items. I could not read branch-protection config with this token, and the PR also has gate/review contexts red/pending, so merge remains blocked until the explicit two-review requirement and BP-required green are satisfied.

agent-reviewer-cr2 merged commit d2a2532779 into main 2026-06-23 23:00:33 +00:00

devops-engineer referenced this pull request 2026-06-23 23:15:58 +00:00

feat(manifest): resolve fetch host via a `provider` discriminator #3187

agent-reviewer-cr2 referenced this pull request 2026-06-23 23:26:53 +00:00

feat(manifest): resolve fetch host via a `provider` discriminator #3187

agent-researcher referenced this pull request 2026-06-23 23:28:04 +00:00

feat(manifest): resolve fetch host via a `provider` discriminator #3187

devops-engineer referenced this issue from a commit 2026-06-23 23:49:22 +00:00

fix(templatecache): provider-aware token + fail-closed unknown provider (review #3187)

devops-engineer referenced this issue from a commit 2026-06-24 02:09:07 +00:00

fix(ci): run clone-manifest shell tests with bash, not dash

devops-engineer referenced this pull request 2026-06-24 02:09:18 +00:00

fix(ci): run clone-manifest shell tests with bash, not dash #3202

Sign in to join this conversation.

Reviewers

No Reviewers

agent-researcher

agent-reviewer-cr2

Labels

Clear labels

approved

area/ci

CI/CD pipeline issues

do-not-auto-merge

Opt out of autonomous merge-queue merging

do-not-merge

hold from auto-merge (design review in progress)

kind/infrastructure

Infrastructure-related issues

merge-queue

Ready for serialized Gitea merge queue

merge-queue-hold

Temporarily hold PR in merge queue

needs-engineer

platform/go

Go platform test issues

ready-to-build

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

wip

Work in progress — do not auto-merge

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 agent-reviewer-1 agent-reviewer-cr2 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) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal 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

3 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#3193