@bvdm/delano 0.1.0

package/assets/payload/.agents/skills/execution-skill/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: execution-skill
+description: Execute mapped tasks with stream discipline, dependency safety checks, and evidence updates. Use when tasks are ready for implementation.
+---
+
+# execution-skill
+
+## Trigger context
+- tasks are ready and dependency-safe
+
+## Required inputs
+- task_ids
+- stream_boundaries
+- dependency_state
+
+## Output schema
+- updated task status
+- progress updates
+- delivery artifacts (commits/PRs/notes)
+
+## Quality checks
+- blockers explicit with owner/check-back time
+- progress updates current
+- stream boundaries respected
+
+## Failure behavior
+- stop work on hard blockers
+- escalate file ownership conflict
+
+## Allowed side effects
+- update task frontmatter/status
+- append updates under `.project/projects/<slug>/updates/`
+
+## Script hooks
+- `bash .agents/scripts/pm/in-progress.sh`
+- `bash .agents/scripts/pm/standup.sh`
+- `bash .agents/scripts/pm/next.sh`
+
+## Execution assets
+- `references/runbook.md`
+- `templates/blocker-update.md`
+- `templates/stream-update.md`

package/assets/payload/.agents/skills/execution-skill/references/runbook.md

@@ -0,0 +1,16 @@
+# Execution Runbook
+
+1. Pick dependency-safe task:
+   - `bash .agents/scripts/pm/next.sh`
+2. Set task status to `in-progress`.
+3. Execute implementation in owned boundaries.
+4. Record updates in `.project/projects/<slug>/updates/...`.
+5. Surface blockers immediately:
+   - `bash .agents/scripts/pm/blocked.sh`
+6. Review active work:
+   - `bash .agents/scripts/pm/in-progress.sh`
+
+Exit gate:
+- Work complete per acceptance criteria
+- Evidence log updated
+- Task ready for quality/review

package/assets/payload/.agents/skills/execution-skill/templates/blocker-update.md

@@ -0,0 +1,13 @@
+# Blocker Update
+
+## Task
+
+## Blocker
+
+## Blocker Owner
+
+## Check-back Time
+
+## Mitigation Attempted
+
+## Next Safe Action

package/assets/payload/.agents/skills/execution-skill/templates/stream-update.md

@@ -0,0 +1,9 @@
+# Stream Update
+
+## Completed
+
+## In Progress
+
+## Blockers
+
+## Next Actions

package/assets/payload/.agents/skills/learning-skill/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: learning-skill
+description: Distill reusable decisions and lessons into project memory and improvement actions. Use at milestones, closeout, or recurring failure patterns.
+---
+
+# learning-skill
+
+## Trigger context
+- milestone or project closeout
+- recurring failure pattern detected
+
+## Required inputs
+- project_slug
+- retrospective_notes
+- execution_logs
+
+## Output schema
+- updated `decisions.md`
+- reusable lessons summary
+- follow-up improvement items
+
+## Quality checks
+- every lesson links to observed evidence
+- lessons are actionable and specific
+- next-cycle improvements are prioritized
+
+## Failure behavior
+- if evidence is weak, return evidence gaps first
+
+## Allowed side effects
+- update `.project/projects/<slug>/decisions.md`
+- append to project context/progress docs
+
+## Script hooks
+- `bash .agents/scripts/query-log.sh --last 200`
+- `bash .agents/scripts/pm/status.sh`
+
+## Execution assets
+- `references/runbook.md`
+- `templates/retrospective.md`
+- `templates/improvement-backlog.md`

package/assets/payload/.agents/skills/learning-skill/references/runbook.md

@@ -0,0 +1,13 @@
+# Learning Runbook
+
+1. Gather evidence from updates, logs, and outcomes.
+2. Extract decisions and lessons with explicit evidence links.
+3. Update `.project/projects/<slug>/decisions.md`.
+4. Add prioritized improvement actions for next cycle.
+5. Snapshot current project state:
+   - `bash .agents/scripts/pm/status.sh`
+
+Exit gate:
+- Lessons are actionable
+- Reusable patterns are explicit
+- Improvement backlog is prioritized

package/assets/payload/.agents/skills/learning-skill/templates/improvement-backlog.md

@@ -0,0 +1,10 @@
+# Improvement Backlog
+
+## P1
+- 
+
+## P2
+- 
+
+## P3
+- 

package/assets/payload/.agents/skills/learning-skill/templates/retrospective.md

@@ -0,0 +1,11 @@
+# Retrospective
+
+## What Worked
+
+## What Did Not Work
+
+## Key Decisions and Why
+
+## Reusable Patterns
+
+## Improvements for Next Cycle

package/assets/payload/.agents/skills/planning-skill/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: planning-skill
+description: Translate an approved Spec into an executable Delivery Plan and workstreams. Use after spec approval before task decomposition.
+---
+
+# planning-skill
+
+## Trigger context
+- `spec.md` approved and active
+
+## Required inputs
+- spec_path
+- architecture_constraints
+- dependency_inputs
+
+## Output schema
+- `.project/projects/<slug>/plan.md`
+- `.project/projects/<slug>/workstreams/*.md`
+
+## Quality checks
+- architecture decisions justified
+- rollout and rollback path documented
+- workstream boundaries explicit
+
+## Failure behavior
+- stop on unresolved architectural conflicts
+- return tradeoff matrix and decision prompts
+
+## Allowed side effects
+- create/update `plan.md`
+- create/update `workstreams/*.md`
+
+## Script hooks
+- `bash .agents/scripts/pm/validate.sh`
+- `bash .agents/scripts/pm/status.sh`
+
+## Execution assets
+- `references/runbook.md`
+- `templates/architecture-decision.md`
+- `templates/workstream-definition.md`

package/assets/payload/.agents/skills/planning-skill/references/runbook.md

@@ -0,0 +1,15 @@
+# Planning Runbook
+
+1. Read `spec.md` and extract constraints.
+2. Draft `plan.md` from `.project/templates/plan.md`.
+3. Define initial workstreams from `.project/templates/workstream.md`.
+4. Add milestone, rollout, rollback, and test strategies.
+5. Validate:
+   - `bash .agents/scripts/pm/validate.sh`
+6. Snapshot:
+   - `bash .agents/scripts/pm/status.sh`
+
+Exit gate:
+- Architecture decisions justified
+- Workstream ownership boundaries clear
+- Rollout/rollback explicit

package/assets/payload/.agents/skills/planning-skill/templates/architecture-decision.md

@@ -0,0 +1,15 @@
+# Architecture Decision
+
+## Context
+
+## Decision
+
+## Alternatives Considered
+- Option A:
+- Option B:
+
+## Rationale
+
+## Consequences
+
+## Follow-up Actions

package/assets/payload/.agents/skills/planning-skill/templates/workstream-definition.md

@@ -0,0 +1,13 @@
+# Workstream Definition
+
+## Name
+
+## Objective
+
+## Owned Files/Areas
+
+## Dependencies
+
+## Conflict Risk Zones
+
+## Handoff Criteria

package/assets/payload/.agents/skills/quality-skill/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: quality-skill
+description: Verify release readiness and enforce quality gates with risk-based checks and evidence capture. Use before closure or merge.
+---
+
+# quality-skill
+
+## Trigger context
+- target tasks are implemented and ready for verification
+
+## Required inputs
+- changed_scope
+- risk_level
+- test_requirements
+
+## Output schema
+- quality_evidence bundle
+- pass/fail gate decision
+
+## Quality checks
+- required tests executed by risk level
+- acceptance criteria complete
+- unresolved critical defects = 0
+
+## Failure behavior
+- stop merge readiness on failed critical checks
+- emit remediation checklist
+
+## Allowed side effects
+- append evidence logs in task files
+- write test logs under `.agents/logs/tests/`
+
+## Script hooks
+- `bash .agents/scripts/test-and-log.sh <command>`
+- `bash .agents/scripts/pm/validate.sh`
+
+## Execution assets
+- `references/runbook.md`
+- `templates/quality-evidence.md`
+- `templates/gate-decision.md`

package/assets/payload/.agents/skills/quality-skill/references/runbook.md

@@ -0,0 +1,14 @@
+# Quality Runbook
+
+1. Determine risk level (low/medium/high).
+2. Execute required tests and capture logs:
+   - `bash .agents/scripts/test-and-log.sh <test command>`
+3. Verify acceptance criteria and evidence completeness.
+4. Re-run validation:
+   - `bash .agents/scripts/pm/validate.sh`
+5. Produce gate decision summary.
+
+Exit gate:
+- Required checks pass for risk level
+- Critical unresolved defects = 0
+- Evidence links are present

package/assets/payload/.agents/skills/quality-skill/templates/gate-decision.md

@@ -0,0 +1,10 @@
+# Quality Gate Decision
+
+## Decision
+- pass / fail
+
+## Reasoning
+
+## Blocking Items (if fail)
+
+## Required Follow-up

package/assets/payload/.agents/skills/quality-skill/templates/quality-evidence.md

@@ -0,0 +1,16 @@
+# Quality Evidence
+
+## Scope
+
+## Risk Level
+
+## Tests Run
+- Unit:
+- Integration:
+- GUI/E2E:
+
+## Results
+
+## Defects Found
+
+## Evidence Links

package/assets/payload/.agents/skills/sync-skill/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: sync-skill
+description: Reconcile local contracts with Linear and GitHub state, repair mapping and status drift, and update registry files. Use when task state changes or sync drift is suspected.
+---
+
+# sync-skill
+
+## Trigger context
+- active tasks changed
+- status or dependency drift suspected
+
+## Required inputs
+- project_slug
+- local_registry
+- task_files
+
+## Output schema
+- updated_registry
+- drift_report
+
+## Quality checks
+- active tasks mapped
+- no duplicate mapping
+- dependency parity pass
+
+## Failure behavior
+- dry-run when uncertainty detected
+- emit conflict resolution actions
+
+## Allowed side effects
+- update `.project/registry/linear-map.json`
+- update local IDs/links in task contracts
+
+## Script hooks
+- `bash .agents/scripts/pm/status.sh`
+- `bash .agents/scripts/pm/validate.sh`
+
+## Execution assets
+- `references/runbook.md`
+- `templates/drift-report.md`
+- `templates/conflict-resolution-actions.md`

package/assets/payload/.agents/skills/sync-skill/references/runbook.md

@@ -0,0 +1,17 @@
+# Sync Runbook
+
+1. Read local contracts and `.project/registry/linear-map.json`.
+2. Compare with Linear/GitHub state.
+3. Apply idempotent cycle:
+   - create missing mappings
+   - update changed statuses/links
+   - preserve existing IDs
+4. Write drift report and mapping updates.
+5. Validate:
+   - `bash .agents/scripts/pm/status.sh`
+   - `bash .agents/scripts/pm/validate.sh`
+
+Exit gate:
+- No orphaned active tasks
+- No duplicate mappings
+- Status/dependency parity confirmed

package/assets/payload/.agents/skills/sync-skill/templates/conflict-resolution-actions.md

@@ -0,0 +1,10 @@
+# Conflict Resolution Actions
+
+## Conflict
+
+## Proposed Resolution
+
+## Needs Human Decision?
+- yes / no
+
+## Safe Next Step

package/assets/payload/.agents/skills/sync-skill/templates/drift-report.md

@@ -0,0 +1,14 @@
+# Drift Report
+
+## Mapping Drift
+
+## Status Drift
+
+## Dependency Drift
+
+## Orphan Drift
+
+## Risk Level
+- low | medium | high
+
+## Recommended Action

package/assets/payload/.delano/README.md

@@ -0,0 +1,7 @@
+# Optional Delano UI Layer
+
+This folder is reserved for optional presentation tooling.
+
+Policy:
+- `.project` remains source of truth.
+- `.delano` must not become process truth.

package/assets/payload/.gitattributes

@@ -0,0 +1,14 @@
+*.sh text eol=lf
+*.bash text eol=lf
+*.zsh text eol=lf
+
+*.md text eol=lf
+*.yml text eol=lf
+*.yaml text eol=lf
+*.json text eol=lf
+*.jsonc text eol=lf
+*.ts text eol=lf
+*.tsx text eol=lf
+*.js text eol=lf
+*.mjs text eol=lf
+*.py text eol=lf

package/assets/payload/.project/context/README.md

@@ -0,0 +1,15 @@
+# Delano Context Pack
+
+Keep this folder current for execution continuity.
+
+Required context files:
+
+- `project-overview.md`
+- `project-brief.md`
+- `tech-context.md`
+- `project-structure.md`
+- `system-patterns.md`
+- `product-context.md`
+- `project-style-guide.md`
+- `progress.md`
+- `gui-testing.md`

package/assets/payload/.project/context/gui-testing.md

@@ -0,0 +1,20 @@
+# GUI Testing Policy
+
+## Enforcement Mode
+- `advisory`
+
+## Smoke Routes
+- No GUI smoke route is required for the current core repo because Delano is presently handbook- and script-driven.
+- If a project introduces or changes `.delano/` UI surfaces, that project should add the routes and critical flows to exercise here or in project-specific context.
+
+## Console Filtering
+- Block browser/runtime errors for any UI surface that is introduced.
+- Allow only documented, known development-only noise during local testing.
+
+## Evidence Requirements
+- Capture screenshots, console output, and comparison notes only for work that touches `.delano/` or other browser-visible surfaces.
+- Script- and contract-only changes do not require GUI evidence.
+
+## Design Validation Threshold
+- For UI work, critical flows must render correctly, remain usable on supported viewports, and ship without blocked console errors.
+- For non-UI work in this repo, this section is not a gating constraint.

package/assets/payload/.project/context/product-context.md

@@ -0,0 +1,17 @@
+# Product Context
+
+## Users
+- Maintainers evolving Delano's handbook, runtime, and installer behavior.
+- Operators adding Delano to existing repositories and using the PM/runtime scripts day to day.
+- Coding agents working through Delano's shared contracts and adapter notes instead of tool-specific process variants.
+
+## Core Flows
+- Start with an outcome, draft a spec, make the probe decision explicit, plan workstreams, decompose tasks, execute, validate, and close out with evidence.
+- Install Delano into a repository, then operate primarily through `.project/` contracts and `.agents/scripts/pm/*`.
+- Use `validate`, `status`, `next`, and related scripts to keep delivery state coherent and dependency-safe.
+
+## Constraints
+- Delano must stay agent-agnostic and protocol-first rather than becoming a proprietary execution host.
+- `.project` remains the source of truth for delivery state.
+- `.agents` remains the canonical runtime and `.claude` is compatibility only.
+- `.delano` remains optional and must not become process truth.

package/assets/payload/.project/context/progress.md

@@ -0,0 +1,23 @@
+# Progress
+
+## What Changed
+- Completed the handbook-theo-method-upgrade implementation bundle across handbook, templates, runtime scripts, hooks/logging, installer messaging, and skill/runbook references.
+- Synced the `.claude` compatibility mirror to the updated `.agents` runtime so canonical and fallback command paths now align.
+- Replaced the placeholder `.project/context/` files with repo-specific context for Delano as both product and reference implementation.
+- Created the `delano-cli-packaging-v1` project with an approved spec, planned delivery plan, four workstreams, and a decomposed task graph.
+- Added the first working `@bvdm/delano` scaffold: package metadata, `delano` bin entrypoint, command dispatch, wrapper commands, install manifest, asset build pipeline, and a conservative install flow.
+
+## Why It Changed
+- The repo had drift between written process, generated scaffolds, and executable runtime behavior around canonical paths and probe-aware delivery.
+- Closing that drift restores Delano's contract discipline and makes the documented operating model match the runnable one.
+- The repository still lacked living context for Delano itself and needed a clean planning baseline before starting the npm CLI packaging effort.
+- The CLI effort needed a real executable foundation so later bridge, docs, and release work could build on actual package behavior rather than placeholders.
+
+## What Is Next
+- Use `.agents/scripts/pm/*` as the canonical operator path for future work.
+- Follow up separately on any external documentation that may still teach legacy `.claude` examples.
+- Continue `delano-cli-packaging-v1` with legacy installer alignment, operator docs, and release-focused verification.
+
+## Remaining Risks
+- External docs outside this repository may still need the same canonical-path sweep.
+- The CLI packaging project still needs explicit operator documentation and final quality review before the first npm release is ready.

package/assets/payload/.project/context/project-brief.md

@@ -0,0 +1,13 @@
+# Project Brief
+
+## Problem
+- Delano is both the product and the reference repository, so this repo needs real execution context inside `.project/context/`, not empty placeholders.
+- The next delivery initiative is a first npm/CLI packaging layer that must wrap the existing runtime without breaking Delano's handbook-first, file-contract-first architecture.
+
+## Target Outcome
+- Keep this repository self-describing for maintainers and coding agents by documenting the actual product purpose, runtime boundaries, operating constraints, and current health.
+- Stand up a handbook-compliant project outline for the v1 CLI packaging effort so execution can start from an approved spec, delivery plan, workstreams, and atomic tasks.
+
+## Scope Boundaries
+- In scope: repository context for Delano itself, the current canonical runtime model, and the planning/decomposition artifacts for the CLI packaging initiative.
+- Out of scope: implementing the CLI in this setup pass, redefining Delano's core architecture, or changing adapter entrypoint behavior by default.

package/assets/payload/.project/context/project-overview.md

@@ -0,0 +1,14 @@
+# Project Overview
+
+## Mission
+- Delano is an agent-agnostic delivery system that turns outcomes into specs, plans, tasks, execution evidence, and learnings through shared file contracts and runtime scripts.
+- This repository is the canonical source for the handbook, runtime, templates, and reference install path used when Delano is adopted in other repositories.
+
+## Active Delivery Scopes
+- `handbook-theo-method-upgrade` is complete and established the `.agents`-first, probe-aware operating model.
+- `delano-cli-packaging-v1` is the next planned scope: add a thin npm CLI and packaging layer around the existing runtime without turning Delano into a harness.
+
+## Current Health
+- Canonical runtime and contract structure are present and `bash .agents/scripts/pm/validate.sh` passes in this environment.
+- `.agents/` is the canonical runtime tree. `.claude/` exists in this repo as a directory mirror with matching contents, not as a symlink.
+- The primary current gap was context quality rather than missing runtime pieces; the context pack should now be maintained as execution memory, not treated as boilerplate.

package/assets/payload/.project/context/project-structure.md

@@ -0,0 +1,24 @@
+# Project Structure
+
+Document major repository boundaries and ownership.
+
+## Canonical Boundaries
+- `HANDBOOK.md`: canonical operating model, governance, contracts, and workflow stages.
+- `.project/`: delivery truth for project specs, plans, workstreams, tasks, updates, decisions, templates, registry state, and shared context.
+- `.agents/`: canonical runtime assets shared across supported coding agents.
+- `.claude/`: compatibility mirror of `.agents/`; present for Claude-style path expectations only.
+- `.delano/`: optional presentation layer; never source of process truth.
+
+## Runtime Areas
+- `.agents/scripts/pm/`: critical operator commands such as `init.sh`, `validate.sh`, `status.sh`, `next.sh`, and `blocked.sh`.
+- `.agents/skills/`: stage skills and supporting runbooks/templates used to structure work.
+- `.agents/rules/` and `.agents/hooks/`: guardrails and runtime instrumentation.
+- `.agents/adapters/<agent>/`: thin agent-specific notes for Claude, Codex, OpenCode, and Pi.
+
+## Documentation Areas
+- `README.md`: short product/repo overview.
+- `docs/`: operator-facing guidance that expands on the handbook and runtime.
+- Top-level adapter entry files such as `AGENTS.md`, `CLAUDE.md`, and `CODEX.md`: thin pointers into the canonical model.
+
+## Working Notes
+- `tmp/` is scratch space and is not part of Delano's canonical runtime or delivery truth.

package/assets/payload/.project/context/project-style-guide.md

@@ -0,0 +1,17 @@
+# Project Style Guide
+
+## Naming
+- Use kebab-case for project slugs under `.project/projects/`.
+- Use `WS-<letter>` for workstream identifiers and `T-###` for task identifiers.
+- Keep adapter/runtime references explicit: `.agents` for canonical paths, `.claude` only when discussing compatibility behavior.
+
+## Documentation Conventions
+- Keep context files short, factual, and current enough for another operator or agent to resume work without rediscovery.
+- Use handbook terminology consistently: outcome, spec, probe decision, workstream, task, evidence, and closeout.
+- Frontmatter timestamps must be ISO8601 UTC.
+- Do not leak machine-specific absolute paths into shared docs or contracts.
+
+## Review Expectations
+- Changes that touch contracts, templates, runtime scripts, or user-facing docs should be checked for cross-artifact consistency, not reviewed in isolation.
+- Run `bash .agents/scripts/pm/validate.sh` after modifying delivery artifacts or runtime behavior.
+- When planning install or packaging work, prefer conflict-first and non-destructive behavior by default.

package/assets/payload/.project/context/system-patterns.md

@@ -0,0 +1,22 @@
+# System Patterns
+
+Capture architecture and delivery patterns that should be reused.
+
+## Handbook-First Delivery
+- Changes to runtime behavior, templates, and operator guidance should be aligned with `HANDBOOK.md`, not invented ad hoc in scripts or adapter docs.
+- Planning follows the handbook stages: discovery, optional probe, planning, breakdown, sync, execution, quality, closeout, and learning.
+
+## File-Contract-First State
+- `.project/` is the source of truth for delivery state. Scripts and future tooling should read and respect those contracts instead of replacing them with hidden state.
+- Project context files are part of execution continuity and should be updated when repo reality changes.
+
+## Thin Runtime Wrapping
+- Delano favors thin wrappers around existing execution scripts over large rewrites. The current PM scripts are shell/Python-driven and should remain the execution layer unless there is a strong reason to replace them.
+- Adapter entrypoints stay minimal and point back to the shared runtime and handbook.
+
+## Compatibility Without Dual Truth
+- `.claude/` may mirror `.agents/`, but it is compatibility infrastructure only. New work should treat `.agents/` as canonical and avoid creating a second source of truth.
+
+## Conservative Installation
+- Installation and packaging flows should compute explicit plans, surface conflicts early, and avoid silently overwriting `.project/` or `.agents/` content.
+- Seeded files may establish a repo, but once installed the consumer repo owns its own `.project` state.

package/assets/payload/.project/context/tech-context.md

@@ -0,0 +1,19 @@
+# Tech Context
+
+## Stack
+- Markdown contracts and templates for delivery artifacts.
+- Bash for the PM/operator script layer.
+- Python for validation and dependency-graph checks.
+- Git for repository discovery, sparse installs, and sync-oriented workflows.
+- Node/npm is the intended packaging surface for the next CLI initiative, but not yet the execution layer for Delano itself.
+
+## Runtime Constraints
+- Current operator environment is Windows-first with PowerShell available; Delano still assumes `bash`, `git`, and a usable Python runtime.
+- Canonical command paths should use `.agents/scripts/...`; `.claude/scripts/...` is compatibility-only when the mirror exists.
+- Shared docs and contracts must avoid absolute path leakage.
+- `.project` and `.agents` are seeded artifacts and runtime assets, not package-owned mutable state after install.
+
+## Integration Points
+- `.project/registry/linear-map.json` and `.project/registry/migration-map.json` capture tracker mapping state.
+- `.agents/scripts/pm/init.sh`, `validate.sh`, `status.sh`, `next.sh`, and `blocked.sh` are the current critical-path operator interface.
+- `install-delano.sh` is the current shell-first bootstrap path for installing Delano into another repository.

package/assets/payload/.project/registry/linear-map.json

@@ -0,0 +1,6 @@
+{
+  "version": 1,
+  "updated": "2026-02-19T13:36:35Z",
+  "projects": {},
+  "tasks": {}
+}