modwire 4.0.0__tar.gz → 5.0.0__tar.gz

{modwire-4.0.0 → modwire-5.0.0}/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,8 +1,9 @@
 name: Bug report
 description: Report incorrect architecture analysis, graph output, package metadata, or report output.
 title: "Bug: "
-labels:
-  - bug
+type: Bug
+projects:
+  - modwire/1
 body:
   - type: markdown
     attributes:

modwire-5.0.0/.github/ISSUE_TEMPLATE/decision.yml

@@ -0,0 +1,48 @@
+name: Architecture or governance decision
+description: Record a decision that changes contracts, compatibility, architecture, or governance.
+title: "Decision: "
+type: Decision
+labels:
+  - contract
+projects:
+  - modwire/1
+body:
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      description: Explain the forces, constraints, and decision deadline.
+    validations:
+      required: true
+
+  - type: textarea
+    id: options
+    attributes:
+      label: Options considered
+      description: Describe credible alternatives and their tradeoffs.
+    validations:
+      required: true
+
+  - type: textarea
+    id: decision
+    attributes:
+      label: Proposed decision
+      description: State the proposed choice and why it best fits the constraints.
+    validations:
+      required: true
+
+  - type: textarea
+    id: consequences
+    attributes:
+      label: Consequences and acceptance criteria
+      description: Describe positive and negative consequences plus the evidence needed to consider the decision implemented.
+    validations:
+      required: true
+
+  - type: input
+    id: relationships
+    attributes:
+      label: Related issues and decisions
+      description: Link superseded, blocking, blocked, parent, or implementation issues.
+    validations:
+      required: false

modwire-5.0.0/.github/ISSUE_TEMPLATE/epic.yml

@@ -0,0 +1,51 @@
+name: Ecosystem epic
+description: Coordinate an outcome delivered by multiple repository-owned sub-issues.
+title: "Epic: "
+type: Epic
+labels:
+  - ecosystem
+projects:
+  - modwire/1
+body:
+  - type: textarea
+    id: outcome
+    attributes:
+      label: Ecosystem outcome
+      description: Describe the user-visible or compatibility result across packages.
+    validations:
+      required: true
+
+  - type: textarea
+    id: repositories
+    attributes:
+      label: Affected repositories
+      description: List every repository expected to own a sub-issue.
+      placeholder: |
+        - modwire/modwire
+        - modwire/modwire-cli
+    validations:
+      required: true
+
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      description: Include integration verification and release-readiness conditions.
+    validations:
+      required: true
+
+  - type: textarea
+    id: rollout
+    attributes:
+      label: Rollout and rollback
+      description: Define compatibility promises, rollout order, and rollback strategy.
+    validations:
+      required: true
+
+  - type: input
+    id: relationships
+    attributes:
+      label: Initial sub-issues and dependencies
+      description: Link existing issues. Create native sub-issue and dependency relationships after submission.
+    validations:
+      required: false

{modwire-4.0.0 → modwire-5.0.0}/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,8 +1,9 @@
 name: Feature request
 description: Suggest a new architecture, graph, shape, callable, export, or integration capability.
 title: "Feature: "
-labels:
-  - enhancement
+type: Feature
+projects:
+  - modwire/1
 body:
   - type: markdown
     attributes:

modwire-5.0.0/.github/ISSUE_TEMPLATE/task.yml

@@ -0,0 +1,56 @@
+name: Task
+description: Propose concrete implementation, maintenance, documentation, or release work.
+title: "Task: "
+type: Task
+projects:
+  - modwire/1
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Select every pinned issue field before submission. Use native dependencies and sub-issues for relationships; do not encode them only in prose.
+
+  - type: textarea
+    id: outcome
+    attributes:
+      label: Outcome
+      description: State the observable result, not only the activity.
+      placeholder: After this work...
+    validations:
+      required: true
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: Scope
+      description: Describe the intended implementation boundary and important exclusions.
+    validations:
+      required: true
+
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      description: List objective conditions that prove the outcome is complete.
+      placeholder: |
+        - [ ] Observable behavior is implemented.
+        - [ ] Relevant tests and documentation are updated.
+    validations:
+      required: true
+
+  - type: textarea
+    id: rollout
+    attributes:
+      label: Rollout and rollback
+      description: Explain compatibility, migration, rollout, or rollback considerations; write "Not applicable" when none exist.
+    validations:
+      required: true
+
+  - type: input
+    id: relationships
+    attributes:
+      label: Related issues
+      description: Link candidate parents, sub-issues, blockers, or blocked work. A maintainer will create the native relationships.
+      placeholder: https://github.com/modwire/...
+    validations:
+      required: false

{modwire-4.0.0 → modwire-5.0.0}/.github/modwire-ecosystem.yml

@@ -1,8 +1,8 @@
-version: 2
+version: 3
 
 packages:
   core:
-    repository: 9orky/modwire
+    repository: modwire/modwire
     distribution: modwire
     component: Core
     role: coordinator
@@ -10,7 +10,7 @@ packages:
     summary: Typed coordination library and ecosystem integration gate.
     depends_on: [extraction, mermaid, siren]
   cli:
-    repository: 9orky/modwire-cli
+    repository: modwire/modwire-cli
     distribution: modwire-cli
     component: CLI
     role: runtime
@@ -18,43 +18,43 @@ packages:
     summary: Command-line runtime and user-facing workflows.
     depends_on: [core]
   extraction:
-    repository: 9orky/modwire-extraction
+    repository: modwire/modwire-extraction
     distribution: modwire-extraction
     component: Extraction
     role: building_block
     lifecycle: active
     summary: Canonical source extraction and normalization.
   mermaid:
-    repository: 9orky/modwire-mermaid
+    repository: modwire/modwire-mermaid
     distribution: modwire-mermaid
     component: Mermaid
     role: building_block
     lifecycle: active
     summary: Typed, deterministic Mermaid source generation.
   siren:
-    repository: 9orky/modwire-siren
+    repository: modwire/modwire-siren
     distribution: modwire-siren
     component: Siren
     role: building_block
     lifecycle: active
     summary: Typed Siren hypermedia and OpenAPI integration.
   mcp:
-    repository: 9orky/modwire-mcp
+    repository: modwire/modwire-mcp
     distribution: modwire-mcp
     component: MCP
     role: integration
     lifecycle: incubating
-    summary: MCP surface and future home of scaffolding operations.
-    depends_on: [core]
+    summary: Planned MCP integration, activated after CLI exposes filesystem, project, and execution capabilities.
+    depends_on: [cli]
 
 project:
-  owner: 9orky
+  owner: modwire
   title: Modwire Ecosystem
-  number: 4
+  number: 1
   visibility: public
   default_package: core
   description: Cross-repository roadmap and release coordination for the Modwire ecosystem.
-  governance_url: https://github.com/9orky/modwire/blob/main/docs/governance/github-ecosystem.md
+  governance_url: https://github.com/modwire/modwire/blob/main/docs/governance/github-ecosystem.md
 
 workflows:
   contract_ref: workflows-v1
@@ -62,7 +62,9 @@ workflows:
   release_entrypoint: .github/workflows/release.yml
   verify_reusable: .github/workflows/python-package.yml
   release_build_reusable: .github/workflows/python-release-build.yml
-  github_release_reusable: .github/workflows/python-github-release.yml
+  release_assets_reusable: .github/workflows/python-release-assets.yml
+  release_driver: github_release
+  release_event: published
   release_tag_pattern: ^v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)$
   artifact_name: python-package-distributions
   pypi_environment: pypi
@@ -73,26 +75,85 @@ workflows:
     download_artifact: actions/download-artifact@v8
     publish_pypi: pypa/gh-action-pypi-publish@release/v1
 
+issue_types:
+  Task:
+    description: A concrete unit of implementation, maintenance, or documentation work.
+    color: yellow
+  Bug:
+    description: Incorrect or unexpected existing behavior.
+    color: red
+  Feature:
+    description: A new user-facing capability or behavior.
+    color: blue
+  Epic:
+    description: A coordinated outcome delivered through multiple sub-issues.
+    color: purple
+  Decision:
+    description: An architecture, compatibility, or governance decision.
+    color: green
+
 fields:
   Status:
+    owner: project
     type: single_select
     options: [Inbox, Ready, In progress, Blocked, Review, Done]
   Horizon:
+    owner: issue
     type: single_select
-    options: [Now, Next, Later]
+    description: Planning horizon; Unscheduled means accepted but not placed on the roadmap.
+    visibility: public
+    options: [Now, Next, Later, Unscheduled]
   Priority:
+    owner: issue
     type: single_select
+    description: Relative delivery priority, from critical P0 to opportunistic P3.
+    visibility: public
     options: [P0, P1, P2, P3]
   Component:
+    owner: issue
     type: single_select
+    description: Modwire package primarily responsible for delivery.
+    visibility: public
     source: packages
   Release train:
+    owner: issue
     type: text
+    description: Coordinated delivery train, or Unscheduled when none applies.
+    visibility: public
   Target date:
+    owner: issue
     type: date
+    description: Expected completion date for committed work.
+    visibility: public
+  Start date:
+    owner: issue
+    type: date
+    description: Date on which active implementation begins.
+    visibility: public
   Risk:
+    owner: issue
     type: single_select
+    description: Delivery, compatibility, or operational risk if the issue changes or slips.
+    visibility: public
     options: [Low, Medium, High]
+  Effort:
+    owner: issue
+    type: single_select
+    description: Relative implementation effort using T-shirt sizing.
+    visibility: public
+    options: [XS, S, M, L, XL]
+
+issue_intake:
+  project: modwire/1
+  required_fields: [Horizon, Priority, Risk, Component, Release train, Effort]
+  ready_requires: [assignee, acceptance_criteria]
+  incomplete_label: needs-metadata
+  agent_must_not_guess: true
+
+relationships:
+  dependencies: native
+  hierarchy: native_sub_issues
+  cross_repository_parent: modwire/modwire
 
 views:
   - name: Roadmap
@@ -120,16 +181,10 @@ views:
     filter: "Status:Inbox"
 
 labels:
-  "type:bug":
-    color: "d73a4a"
-    description: Incorrect existing behavior
-  "type:feature":
-    color: "0e8a16"
-    description: New user-facing capability
-  "type:maintenance":
+  maintenance:
     color: "c5def5"
     description: Internal maintenance
-  "type:docs":
+  documentation:
     color: "0075ca"
     description: Documentation
   ecosystem:
@@ -141,19 +196,22 @@ labels:
   breaking:
     color: "b60205"
     description: Backward-incompatible change
-  blocked:
-    color: "e99695"
-    description: Blocked by another decision or delivery
   release-gate:
     color: "fbca04"
     description: Must complete before a release
+  needs-metadata:
+    color: "b60205"
+    description: Missing required issue intake metadata
+  requires-human-approval:
+    color: "d93f0b"
+    description: Explicitly require a human to approve the pull request
 
 automation:
   auto_add_filter: "is:open"
   added_status: Inbox
   closed_status: Done
   merged_status: Done
-  archive_filter: "Status:Done updated:<@today-30d"
+  archive_filter: "is:closed updated:<@today-30d"
 
 milestones:
   scope: repository