You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Phase 3.1: Production Deployment - Metrics Agent #2119
Deploy metrics-collection workflow to production with automatic scheduling.
Deliverables
Enable metrics-collection.yml workflow on main/develop
Configure scheduled run: daily at 2 AM UTC
Set up GitHub token and environment secrets
Enable workflow logging and monitoring
Configure failure alerts (Slack notifications)
Acceptance Criteria
Workflow runs automatically on schedule
Metrics collected successfully within <5 minutes
Zero authentication or permission errors
Failure notifications working
Estimate: 3-5 hours
Related: Metrics Agent Phase 3 Project, Task 3.1
Definition of Ready (DoR)
Clear problem statement and expected outcome
Acceptance criteria defined
Related issues/dependencies identified
Required resources/approvals listed
Owner / Assignee
Responsible Party: [To be assigned]
Definition of Done (DoD)
All acceptance criteria met
Changes tested and validated
Documentation updated
Changes merged and deployed
Stakeholders notified
Spec 020 programme alignment — Tier 7
Keep this issue scoped to its existing workflow-deployment outcome; it does not establish portable metrics-agent implementation or readiness. Verify current workflow behaviour, permissions, scheduling, collected data and alert delivery before treating checked criteria as evidence. Record metric definitions, source coverage and collection failures. Production scheduling, credentials and notification changes require an exact preview and approval; never include secret values in issues or reports.
Programme Tier 7 describes delivery sequencing, not native priority. Each delivery slice must record its exact branch and base, PR title, live template, verified labels, assignee, changed-file scope, tests and closure criteria before implementation. Reuse matching existing work. Stack PRs only for a demonstrated dependency, with merge and retargeting order documented.
Closing as stale: no linked open PR and no activity since 2026-08-19, and it belongs to a plan that predates the current agents and skills consolidation (#3464). Reopen if it is still needed.
Reopening: this is planned work that has not started, not work that is superseded. It should not have been closed in the #3464 sweep. Sorry for the noise.
Activity
linear-code commentedon Aug 19, 2026
LS-2679
project: Metrics Agent Phase 3 — Production Rollout & Integration
github-actions commentedon Aug 19, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
github-actions commentedon Aug 19, 2026
✅ Template check passed after update. Thanks for fixing the issue body.
chore(release): v1.0.0 (#2351)
github-actions commentedon Sep 9, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:area:cimigrate:priority:importantmigrate:status:needs-more-infomigrate:type:taskValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.
eleshar commentedon Sep 23, 2026
Closing as stale: no linked open PR and no activity since 2026-08-19, and it belongs to a plan that predates the current agents and skills consolidation (#3464). Reopen if it is still needed.
eleshar commentedon Sep 23, 2026
Reopening: this is planned work that has not started, not work that is superseded. It should not have been closed in the #3464 sweep. Sorry for the noise.