Alexander Mills ORESoftware

Dancing Dragons — Combined Task List

CRITICAL: Run ALL tasks listed here (yes, you can complete all in one loop interval). Consider them all fresh tasks — remove memory of each task from prior runs. Even if tasks haven't changed since last time, re-run them all in order. Follow docs/critical-merging-instructions.md throughout.

ABSOLUTELY CRITICAL — do NOT skip tasks — do NOT do them out of order!

MASTER TASK LIST

GLOBAL RULES

DO NOT skip tasks.
Run tasks strictly in order unless blocked.
Commit frequently with meaningful commit messages.
Push frequently.
Ask for clarification only if truly blocked.
Preserve existing functionality.

CRITICAL: run ALL tasks listed here, in order. Treat this file as fresh every loop. Follow docs/critical-merging-instructions.md and docs/audit-and-harden.md.

Notes:

Do not use blacklisted commands from AGENTS.md: rm, sed, mv, git stash, or shell wrappers that invoke them.
If a project script invokes a blacklisted command, do not run that script; run the safe underlying command directly.
Do all browser automation headless.
Skip full eslint and full tsc until the final verification pass. Use focused tests and spot checks while working.
For spot type checks, use: pnpm exec tsc --noEmit --isolatedModules -p tsconfig.json

CRITICAL: run ALL tasks listed here! (yes you can complete all in one loop interval)! And consider them all fresh tasks, you can remove your memory of each task from prior runs. Critical - even if these tasks haven't changed since last time, you must re-run them, all of them in order!

ABSOLUTELY CRITICAL - do NOT skip tasks - do NOT do them out of order!!!!!!

notes:

when type-checking just do spot checks with --isolatedModules -p tsconfig.json; and skip eslint; the -p tsconfig.json is important because of path aliases in tsconfig.json ;
prefer src/server/subroutines to src/server/actions; and src/server/actions/cache should probably be in src/server/cache;

please do all browser automation HEADLESS!!;

CRITICAL: run ALL tasks listed here! (yes you can complete all in one loop interval)! And consider them all fresh tasks, you can remove your memory of each task from prior runs. Critical - even if these tasks haven't changed since last time, you must re-run them, all of them in order! follow docs/critical-merging-instructions.md;

ABSOLUTELY CRITICAL - do NOT skip tasks - do NOT do them out of order!!!!!!

notes:

when type-checking just do spot checks with --isolatedModules -p tsconfig.json; and skip eslint; the -p tsconfig.json is important because of path aliases in tsconfig.json ;
please do all browser automation HEADLESS!!;

with a backend server action:

'use server';

export async function createEntity(v: string, n: number, o: boolean){
 ///
  return {success: true, val: x};
}

	Here is the text formatted clearly with proper structure, bullet points, and linebreaks so Claude Code can easily parse your architecture and requirements:

	Create a new universal package manager called zed-pkg that is backed by any Git server (GitHub, GitLab, Bitbucket).

	### Core Goals & Philosophy

	* Disk Space Efficiency: End-users should save disk space by not having to clone entire Git repositories (including tests) to their local laptops and servers.
	* Publishing & Namespaces:
	* Users can claim a namespace (`<org>`).
	* As long as the repository can be published to GitHub, GitLab, or Bitbucket, it can be published to the organization as `<org>/<repo>.git`.

	let i = 0;

	const v = () => {

	setInterval(() => {
	console.log({i});
	}, 200);

	setInterval(() => {
	i++;

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<meta name="viewport" content="width=device-width, initial-scale=1.0">
	<title>Kanban Dashboard</title>
	<style>
	body {
	font-family: sans-serif;
	margin: 0;

	// source file path: ./src/components/nav/coach-header.tsx
	'use client';

	import React, { useEffect, useRef, useState } from 'react';
	import Link from 'next/link';
	import {
	ChevronDownIcon,
	ChevronUpIcon,
	MagnifyingGlassIcon,
	PersonIcon,