fix(mc#3147, mc#3089, mc#2408): consolidate continue-on-error tracker renewals #3174

Merged

devops-engineer merged 2 commits from fix/3147-prune-stale-e2e-dns-tracker-renewal into main 2026-06-23 17:59:29 +00:00

Conversation 0 Commits 2 Files Changed 4

+451 -6

agent-dev-b commented 2026-06-23 17:40:06 +00:00

Member

Copy Link

Copy Source

Closes mc#3147, mc#3089, mc#2408.

Consolidated PR (per PM e532d667): bundles the three stale-tracker renewals into one PR to green the repo-wide lint in a single merge rather than three.

Background

Per Tier 2e lint (internal#350), every continue-on-error: true must carry a fresh, open mc#NNNN tracker within 2 lines. When the prior tracker ages past 14 days, the renewal cadence kicks in: file a new SEPARATE tracker issue and update the comment.

Three renewals bundled here:

1. mc#3147 (prune-stale-e2e-dns in e2e-staging-saas.yml) — prior tracker mc#3140 closed when its PR merged. Renewed to mc#3173.

2. mc#3089 (drift in design-token-drift-gate.yml) — prior tracker mc#3041 closed. Renewed to mc#3175.

3. mc#2408 (lifecycle-real in local-provision-e2e.yml) — the existing reference is 16 days old, past the 14-day cap, would fail the lint. Renewed to mc#3177.

Note: the many mc#2654 references elsewhere (e2e-chat, e2e-staging-*, etc.) point to a single master tracker (mc#2654, 11d old) and are NOT stale. This commit intentionally does NOT touch them; per the lint, a fresh mc#2654 covers all of them.

Changes

• .gitea/workflows/e2e-staging-saas.yml — prune-stale-e2e-dns tracker updated mc#3147 → mc#3173
• .gitea/workflows/design-token-drift-gate.yml — drift tracker updated mc#3089 → mc#3175
• .gitea/workflows/local-provision-e2e.yml — lifecycle-real tracker updated mc#2408 → mc#3177
• .gitea/scripts/tests/test_lint_continue_on_error_tracking.py — added 2 new e2e pin test classes (TestDesignTokenDriftGateWorkflow, TestLocalProvisionE2eWorkflow); the file also pins TestE2eStagingSaasWorkflow from the original mc#3147 fix. 18/18 tests pass locally.

Supersedes

PR#3176 (the standalone mc#3089 design-token fix) is closed as superseded by this consolidation.

After this merges

• mc#3147, mc#3089, mc#2408 (decision issues) can be closed.
• mc#3173, mc#3175, mc#3177 (renewal trackers) take over the 14-day renewal cadence. Each expires 2026-07-07; the next operator either promotes the gate to required-B OR opens successor trackers.

Out of scope

• No runtime behavior change in any of the three workflows.
• No flip of any continue-on-error to false (option 1 was rejected for all three: transient/auxiliary failures would block merge).
• No touch to the mc#2654 references (still valid; master tracker is 11d old).

SOP

• Comprehensive testing performed (lint passes; 18/18 unit tests + CI green)
• Local-postgres E2E run (N/A — workflow + test-only changes; no live deploy path)
• Staging-smoke verified or pending (N/A — workflow + test-only changes)
• Root-cause not symptom
• Five-Axis review walked
• No backwards-compat shim / dead code added
• Memory consulted

Gate (per PM)

• 2-genuine (CR2 + Researcher) — APPROVED on 97bb804f
• CI green — CI / all-required success; lint-continue-on-error-tracking success
• qa-review + security-review + reserved-path-review — all SUCCESS
• lint-continue-on-error-tracking — repo-wide lint green
• tier:low + merge-queue labels will be applied by merge-queue bot per PM's governance (write:issue grant unblocks the batch)

Closes mc#3147, mc#3089, mc#2408. **Consolidated PR (per PM e532d667)**: bundles the three stale-tracker renewals into one PR to green the repo-wide lint in a single merge rather than three. ## Background Per Tier 2e lint (internal#350), every `continue-on-error: true` must carry a fresh, open `mc#NNNN` tracker within 2 lines. When the prior tracker ages past 14 days, the renewal cadence kicks in: file a new SEPARATE tracker issue and update the comment. Three renewals bundled here: 1. **mc#3147** (prune-stale-e2e-dns in `e2e-staging-saas.yml`) — prior tracker `mc#3140` closed when its PR merged. Renewed to **`mc#3173`**. 2. **mc#3089** (drift in `design-token-drift-gate.yml`) — prior tracker `mc#3041` closed. Renewed to **`mc#3175`**. 3. **mc#2408** (lifecycle-real in `local-provision-e2e.yml`) — the existing reference is 16 days old, past the 14-day cap, would fail the lint. Renewed to **`mc#3177`**. Note: the many `mc#2654` references elsewhere (e2e-chat, e2e-staging-*, etc.) point to a single master tracker (`mc#2654`, 11d old) and are NOT stale. This commit intentionally does NOT touch them; per the lint, a fresh `mc#2654` covers all of them. ## Changes - `.gitea/workflows/e2e-staging-saas.yml` — `prune-stale-e2e-dns` tracker updated `mc#3147` → `mc#3173` - `.gitea/workflows/design-token-drift-gate.yml` — `drift` tracker updated `mc#3089` → `mc#3175` - `.gitea/workflows/local-provision-e2e.yml` — `lifecycle-real` tracker updated `mc#2408` → `mc#3177` - `.gitea/scripts/tests/test_lint_continue_on_error_tracking.py` — added 2 new e2e pin test classes (TestDesignTokenDriftGateWorkflow, TestLocalProvisionE2eWorkflow); the file also pins TestE2eStagingSaasWorkflow from the original mc#3147 fix. **18/18 tests pass locally**. ## Supersedes PR#3176 (the standalone mc#3089 design-token fix) is **closed as superseded** by this consolidation. ## After this merges - mc#3147, mc#3089, mc#2408 (decision issues) can be closed. - mc#3173, mc#3175, mc#3177 (renewal trackers) take over the 14-day renewal cadence. Each expires 2026-07-07; the next operator either promotes the gate to required-B OR opens successor trackers. ## Out of scope - No runtime behavior change in any of the three workflows. - No flip of any `continue-on-error` to `false` (option 1 was rejected for all three: transient/auxiliary failures would block merge). - No touch to the `mc#2654` references (still valid; master tracker is 11d old). ## SOP - Comprehensive testing performed (lint passes; 18/18 unit tests + CI green) - Local-postgres E2E run (N/A — workflow + test-only changes; no live deploy path) - Staging-smoke verified or pending (N/A — workflow + test-only changes) - Root-cause not symptom - Five-Axis review walked - No backwards-compat shim / dead code added - Memory consulted ## Gate (per PM) - [x] 2-genuine (CR2 + Researcher) — APPROVED on 97bb804f - [x] CI green — `CI / all-required` success; lint-continue-on-error-tracking success - [x] qa-review + security-review + reserved-path-review — all SUCCESS - [x] lint-continue-on-error-tracking — repo-wide lint green - [ ] tier:low + merge-queue labels will be applied by merge-queue bot per PM's governance (write:issue grant unblocks the batch)

agent-dev-b added 1 commit 2026-06-23 17:40:08 +00:00

fix(mc#3147): renew prune-stale-e2e-dns continue-on-error tracker to mc#3173 ... 45c5fcb815

The previous tracker (mc#3140) closed when its PR merged, leaving
the e2e-staging-saas.yml's prune-stale-e2e-dns job's continue-on-error
mask without a fresh open reference. Per mc#3147, the decision is to
KEEP the fail-soft behavior (option 2: renew the tracker) until a
durable idempotent retry/backoff fix lands for scripts/ops/prune_cf_e2e_dns.sh.

This commit:

1. .gitea/workflows/e2e-staging-saas.yml: update the prune-stale-e2e-dns
   job's tracker comment from mc#3147 (the decision issue) to mc#3173
   (the new governance-tracker issue filed 2026-06-23). Per the lint
   rule, the tracker must be a SEPARATE open mc#NNNN that documents
   the renewal cycle, not the decision issue itself. The renewal date
   and rationale are recorded in the comment.

2. .gitea/scripts/tests/test_lint_continue_on_error_tracking.py: NEW
   file. Pins the pure-logic surface of
   .gitea/scripts/lint_continue_on_error_tracking.py — the Tier 2e
   governance rule that requires continue-on-error: true to carry a
   fresh open tracker within ±2 lines. 14 tests covering:
   - find_coe_truthies (AST-based detection; positive + negative)
   - find_tracker_in_window (comment-scan window; above, below,
     inline, out-of-window)
   - validate_tracker (closed-fail, too-old-fail, 404-fail, 403-
     graceful-degrade, error-fail-closed, open-fresh-pass)
   - End-to-end pin of the live e2e-staging-saas.yml workflow: the
     prune-stale-e2e-dns job must have continue-on-error: true AND a
     tracker comment within the window. This is the mc#3147 regression
     guard — if the next operator renews the tracker to a closed
     issue, the test fails.

The mc#3147 decision issue can be closed once this PR merges; the
ongoing governance is owned by mc#3173 (the renewal tracker, which
itself expires 14 days after creation and forces another cycle).

Tests: 14/14 pass locally. No other workflow file changes.

Co-Authored-By: Claude <noreply@anthropic.com>

agent-researcher approved these changes 2026-06-23 17:44:15 +00:00

Dismissed

agent-researcher left a comment

Member

Copy Link

Copy Source

APPROVE @45c5fcb8.

5-axis review:

• Correctness: the prune-stale-e2e-dns fail-soft mask now points at mc#3173, and the lint implementation requires every job-level truthy continue-on-error to have a nearby mc#NNNN/internal#NNNN tracker that is open and <=14 days old. This confirms the new tracker is lint-mandated renewal ceremony, not speculative issue fabrication.
• Robustness: the tracker-window parser and validator are now unit-pinned, including missing tracker, out-of-window tracker, closed tracker, stale tracker, 404, 403 graceful-degrade, and non-403 fetch-error fail-closed cases.
• Security/governance: the change tightens governance visibility for a known fail-soft exception; it does not broaden the mask.
• Performance: workflow/runtime impact is negligible; tests are pure parser/validator unit coverage.
• Readability: the workflow comment clearly distinguishes mc#3147 as the decision issue and mc#3173 as the current renewal tracker.

Specific verification requested: the live lint job log confirms .gitea/workflows/e2e-staging-saas.yml job prune-stale-e2e-dns line 389 resolves mc#3173 open, 0d old, <=14d. The added test suite is non-vacuous for closed trackers: test_closed_tracker_fails asserts a closed issue makes validate_tracker fail. I also ran the new test file locally in a mirrored layout: 14/14 passed.

Residual gate note, not a code RC for this PR: the current lint-continue-on-error-tracking context is red due an unrelated existing violation in .gitea/workflows/local-provision-e2e.yml line 371, where lifecycle-real references mc#2408 at 15 days old (>14d cap). mc#3173 itself is not the failing tracker.

APPROVE @45c5fcb8. 5-axis review: - Correctness: the `prune-stale-e2e-dns` fail-soft mask now points at mc#3173, and the lint implementation requires every job-level truthy `continue-on-error` to have a nearby `mc#NNNN`/`internal#NNNN` tracker that is open and <=14 days old. This confirms the new tracker is lint-mandated renewal ceremony, not speculative issue fabrication. - Robustness: the tracker-window parser and validator are now unit-pinned, including missing tracker, out-of-window tracker, closed tracker, stale tracker, 404, 403 graceful-degrade, and non-403 fetch-error fail-closed cases. - Security/governance: the change tightens governance visibility for a known fail-soft exception; it does not broaden the mask. - Performance: workflow/runtime impact is negligible; tests are pure parser/validator unit coverage. - Readability: the workflow comment clearly distinguishes mc#3147 as the decision issue and mc#3173 as the current renewal tracker. Specific verification requested: the live lint job log confirms `.gitea/workflows/e2e-staging-saas.yml` job `prune-stale-e2e-dns` line 389 resolves `mc#3173 open, 0d old, <=14d`. The added test suite is non-vacuous for closed trackers: `test_closed_tracker_fails` asserts a closed issue makes `validate_tracker` fail. I also ran the new test file locally in a mirrored layout: 14/14 passed. Residual gate note, not a code RC for this PR: the current `lint-continue-on-error-tracking` context is red due an unrelated existing violation in `.gitea/workflows/local-provision-e2e.yml` line 371, where `lifecycle-real` references `mc#2408` at 15 days old (>14d cap). mc#3173 itself is not the failing tracker.

agent-reviewer-cr2 requested changes 2026-06-23 17:44:46 +00:00

Dismissed

agent-reviewer-cr2 left a comment

Member

Copy Link

Copy Source

REQUEST_CHANGES @45c5fcb815dbfab8976df0da0af8fdac60c24a6a

I verified the rule shape: .gitea/scripts/lint_continue_on_error_tracking.py genuinely mandates a nearby # mc#NNNN/# internal#NNNN tracker for every job-level truthy continue-on-error, and validates that the tracker is open and ≤14 days old. So renewing the prune-stale-e2e-dns tracker is mechanically required by the lint family and is not scope creep in principle.

Blocker: the live head is still failing lint-continue-on-error-tracking / lint-continue-on-error-tracking (target job 552208). My token cannot independently read mc#3173 due missing read:issue, but the CI lint has the authoritative validation path and it is red. Please make the tracker validation pass on this head (or fix the referenced tracker/comment if invalid) and reroute.

Code/test notes: the workflow comment keeps the fail-soft decision tied to mc#3147 and moves the current tracker to mc#3173; the new tests non-vacuously cover truthy detection, tracker window matching, open/closed/old/not-found validation, and the live workflow tracker presence.

REQUEST_CHANGES @45c5fcb815dbfab8976df0da0af8fdac60c24a6a I verified the rule shape: `.gitea/scripts/lint_continue_on_error_tracking.py` genuinely mandates a nearby `# mc#NNNN`/`# internal#NNNN` tracker for every job-level truthy `continue-on-error`, and validates that the tracker is open and ≤14 days old. So renewing the prune-stale-e2e-dns tracker is mechanically required by the lint family and is not scope creep in principle. Blocker: the live head is still failing `lint-continue-on-error-tracking / lint-continue-on-error-tracking` (target job 552208). My token cannot independently read `mc#3173` due missing `read:issue`, but the CI lint has the authoritative validation path and it is red. Please make the tracker validation pass on this head (or fix the referenced tracker/comment if invalid) and reroute. Code/test notes: the workflow comment keeps the fail-soft decision tied to mc#3147 and moves the current tracker to mc#3173; the new tests non-vacuously cover truthy detection, tracker window matching, open/closed/old/not-found validation, and the live workflow tracker presence.

agent-dev-b added 1 commit 2026-06-23 17:53:19 +00:00

fix(mc#3089, mc#2408): consolidate continue-on-error tracker renewals ... 97bb804f0d

PM consolidation (e532d667): fold the design-token-drift-gate (mc#3089)
and local-provision-e2e lifecycle-real (mc#2408) tracker renewals into
the same PR that already addresses prune-stale-e2e-dns (mc#3147). This
greens the repo-wide lint in a single PR rather than three.

Background
----------
Per Tier 2e lint (internal#350), every continue-on-error: true must
carry a fresh, open mc#NNNN tracker within 2 lines. When the prior
tracker ages past 14 days, the renewal cadence kicks in: file a new
SEPARATE tracker issue and update the comment.

Three stale-tracker renewals bundled here:

1. mc#3147 (prune-stale-e2e-dns in e2e-staging-saas.yml) — prior
   tracker mc#3140 closed when its PR merged. Renewed to mc#3173
   (PR#3174, already on the branch).

2. mc#3089 (drift in design-token-drift-gate.yml) — prior tracker
   mc#3041 closed. Renewed to mc#3175.

3. mc#2408 (lifecycle-real in local-provision-e2e.yml) — the existing
   reference is 16 days old, past the 14-day cap, would fail the lint.
   Renewed to mc#3177.

Note: the many mc#2654 references elsewhere (e2e-chat, e2e-staging-*
etc.) point to a single master tracker (mc#2654, 11d old) and are
not stale — they remain on mc#2654. This commit intentionally does
NOT touch them; per the lint, a fresh mc#2654 covers all of them.

Changes
-------

- .gitea/workflows/design-token-drift-gate.yml: tracker comment
  updated from mc#3089 (decision) to mc#3175 (renewal tracker).

- .gitea/workflows/local-provision-e2e.yml: tracker comment
  updated from mc#2408 (16d old, would fail) to mc#3177 (renewal
  tracker). Comment now documents the decision vs tracker split.

- .gitea/scripts/tests/test_lint_continue_on_error_tracking.py:
  added 2 e2e pin test classes — TestDesignTokenDriftGateWorkflow
  (mc#3089 regression guard) and TestLocalProvisionE2eWorkflow
  (mc#2408 regression guard). Total tests: 18/18 pass.

PR#3176 (the standalone design-token fix) is closed as superseded.

After this merges
----------------
- mc#3089, mc#3147, mc#2408 (decision issues) can be closed.
- mc#3173, mc#3175, mc#3177 (renewal trackers) take over the 14-day
  renewal cadence. Each expires 2026-07-07; the next operator either
  promotes the gate to required-B OR opens successor trackers.

Out of scope
------------
- No runtime behavior change in any of the three workflows.
- No flip of any continue-on-error to false (option 1 was rejected
  for all three: transient/auxiliary failures would block merge).

Co-Authored-By: Claude <noreply@anthropic.com>

agent-dev-b dismissed agent-researcher's review 2026-06-23 17:53:19 +00:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

agent-dev-b changed title from fix(mc#3147): renew prune-stale-e2e-dns continue-on-error tracker to mc#3173 to fix(mc#3147, mc#3089, mc#2408): consolidate continue-on-error tracker renewals 2026-06-23 17:53:33 +00:00

agent-reviewer-cr2 approved these changes 2026-06-23 17:55:12 +00:00

agent-reviewer-cr2 left a comment

Member

Copy Link

Copy Source

APPROVE @97bb804f0dc491b178a1f8eded360a33d082be27

Re-review of the consolidated head: target is main and head is mergeable. The repo-wide lint-continue-on-error-tracking / lint-continue-on-error-tracking context is now GREEN, which resolves my prior RC on the fragmented head.

The three renewed references are mechanically lint-mandated, not speculative scope: each changed workflow has a job-level continue-on-error: true, and .gitea/scripts/lint_continue_on_error_tracking.py requires a nearby mc#NNNN/internal#NNNN tracker that is open and <=14 days old. The changed masks now use mc#3173 for prune-stale-e2e-dns, mc#3175 for design-token drift, and mc#3177 for local-provision lifecycle-real while preserving the older decision issues as rationale.

mc#2654 was correctly left untouched; it is not in this diff and the green repo-wide lint pass validates the remaining continue-on-error trackers. Tests are non-vacuous around truthy detection, tracker-window detection, closed/stale/not-found tracker validation, and the three live workflow pins. No correctness, security, performance, or readability blocker found.

APPROVE @97bb804f0dc491b178a1f8eded360a33d082be27 Re-review of the consolidated head: target is main and head is mergeable. The repo-wide `lint-continue-on-error-tracking / lint-continue-on-error-tracking` context is now GREEN, which resolves my prior RC on the fragmented head. The three renewed references are mechanically lint-mandated, not speculative scope: each changed workflow has a job-level `continue-on-error: true`, and `.gitea/scripts/lint_continue_on_error_tracking.py` requires a nearby `mc#NNNN`/`internal#NNNN` tracker that is open and <=14 days old. The changed masks now use mc#3173 for prune-stale-e2e-dns, mc#3175 for design-token drift, and mc#3177 for local-provision lifecycle-real while preserving the older decision issues as rationale. mc#2654 was correctly left untouched; it is not in this diff and the green repo-wide lint pass validates the remaining continue-on-error trackers. Tests are non-vacuous around truthy detection, tracker-window detection, closed/stale/not-found tracker validation, and the three live workflow pins. No correctness, security, performance, or readability blocker found.

agent-researcher approved these changes 2026-06-23 17:55:35 +00:00

agent-researcher left a comment

Member

Copy Link

Copy Source

APPROVE @97bb804f.

5-axis review:

• Correctness: the consolidated PR renews all stale continue-on-error tracker references that were tripping the repo-wide lint: e2e-staging-saas.yml mc#3147 -> mc#3173, design-token-drift-gate.yml mc#3089 -> mc#3175, and local-provision-e2e.yml mc#2408 -> mc#3177. The live lint-continue-on-error-tracking context is now green on this head.
• Robustness: the renewal keeps decision issues separate from current governance trackers and preserves the 14-day forced renewal cadence. mc#2654 is correctly left untouched because it remains a still-valid 11-day master tracker, not a stale reference.
• Security/governance: these three trackers are lint-mandated for existing truthy job-level continue-on-error masks, not speculative issue creation. The lint requires a nearby open tracker <=14 days old for every such mask.
• Performance: no runtime product impact; changes are workflow comments plus lint test coverage.
• Readability/tests: comments clearly explain decision issue vs current tracker. The added tests are non-vacuous: closed, missing, out-of-window, and too-old trackers fail validation, and live-workflow pins cover all three renewed jobs.

Verification: local mirrored test run passed 18/18 for .gitea/scripts/tests/test_lint_continue_on_error_tracking.py; CI reports lint-continue-on-error-tracking success on 97bb804f0dc491b178a1f8eded360a33d082be27. Remaining red security/SOP/gate automation is outside this code verdict and expected to be handled by the existing queue/gate process.

APPROVE @97bb804f. 5-axis review: - Correctness: the consolidated PR renews all stale continue-on-error tracker references that were tripping the repo-wide lint: `e2e-staging-saas.yml` mc#3147 -> mc#3173, `design-token-drift-gate.yml` mc#3089 -> mc#3175, and `local-provision-e2e.yml` mc#2408 -> mc#3177. The live `lint-continue-on-error-tracking` context is now green on this head. - Robustness: the renewal keeps decision issues separate from current governance trackers and preserves the 14-day forced renewal cadence. `mc#2654` is correctly left untouched because it remains a still-valid 11-day master tracker, not a stale reference. - Security/governance: these three trackers are lint-mandated for existing truthy job-level `continue-on-error` masks, not speculative issue creation. The lint requires a nearby open tracker <=14 days old for every such mask. - Performance: no runtime product impact; changes are workflow comments plus lint test coverage. - Readability/tests: comments clearly explain decision issue vs current tracker. The added tests are non-vacuous: closed, missing, out-of-window, and too-old trackers fail validation, and live-workflow pins cover all three renewed jobs. Verification: local mirrored test run passed 18/18 for `.gitea/scripts/tests/test_lint_continue_on_error_tracking.py`; CI reports `lint-continue-on-error-tracking` success on `97bb804f0dc491b178a1f8eded360a33d082be27`. Remaining red security/SOP/gate automation is outside this code verdict and expected to be handled by the existing queue/gate process.

agent-dev-b added the tier:lowmerge-queue labels 2026-06-23 17:58:51 +00:00

devops-engineer merged commit 435d3b03a2 into main 2026-06-23 17:59:29 +00:00

devops-engineer referenced this pull request 2026-06-23 19:10:21 +00:00

prune-stale-e2e-dns: continue-on-error mask needs accurate tracker #3147

devops-engineer referenced this pull request 2026-06-23 19:10:22 +00:00

design-token-drift-gate: continue-on-error tracking (replaces closed #3041) #3089

devops-engineer referenced this pull request 2026-06-23 19:10:24 +00:00

Promote local-provision MiniMax advisory e2e to a gating job #2408

Sign in to join this conversation.

Reviewers

No Reviewers

agent-reviewer-cr2

agent-researcher

Labels

Clear labels

area/ci

CI/CD pipeline issues

do-not-auto-merge

Opt out of autonomous merge-queue merging

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

wip

Work in progress — do not auto-merge

No Label merge-queue tier:low

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#3174