project-tiny-context-harness 0.11.0 → 0.12.1

package/assets/runtime/windows-job-supervisor/formal_process_supervisor_native_types.cs

@@ -1,215 +0,0 @@
-using System;
-using System.Runtime.InteropServices;
-using System.Text;
-
-public sealed class FormalProcessSupervisorResult
-{
-    public string RequestId { get; set; }
-    public int ProcessId { get; set; }
-    public int ExitCode { get; set; }
-    public bool TimedOut { get; set; }
-    public bool OutputOverflow { get; set; }
-    public bool DescendantsCleaned { get; set; }
-    public long StdoutBytes { get; set; }
-    public long StderrBytes { get; set; }
-    public long StartedUnixMs { get; set; }
-    public long CompletedUnixMs { get; set; }
-    public string MonotonicStartedNs { get; set; }
-    public string MonotonicCompletedNs { get; set; }
-    public string MonotonicClockId { get; set; }
-    public string WallClockId { get; set; }
-    public long UserCpu100Ns { get; set; }
-    public long KernelCpu100Ns { get; set; }
-    public long TotalCpu100Ns { get; set; }
-    public uint TotalProcesses { get; set; }
-    public uint ActiveProcessesAtResult { get; set; }
-    public uint TotalTerminatedProcesses { get; set; }
-    public string AccountingSourceKind { get; set; }
-    public string Error { get; set; }
-}
-
-public static partial class FormalProcessSupervisor
-{
-    private const uint CREATE_SUSPENDED = 0x00000004;
-    private const uint CREATE_NO_WINDOW = 0x08000000;
-    private const uint CREATE_UNICODE_ENVIRONMENT = 0x00000400;
-    private const uint STARTF_USESTDHANDLES = 0x00000100;
-    private const uint HANDLE_FLAG_INHERIT = 0x00000001;
-    private const uint JOB_OBJECT_LIMIT_KILL_ON_JOB_CLOSE = 0x00002000;
-    private const int JobObjectBasicAccountingInformation = 1;
-    private const int JobObjectExtendedLimitInformation = 9;
-    private const uint STILL_ACTIVE = 259;
-    private const int CleanupWaitMilliseconds = 5000;
-
-    [StructLayout(LayoutKind.Sequential)]
-    private struct SECURITY_ATTRIBUTES
-    {
-        public int nLength;
-        public IntPtr lpSecurityDescriptor;
-        [MarshalAs(UnmanagedType.Bool)] public bool bInheritHandle;
-    }
-
-    [StructLayout(LayoutKind.Sequential, CharSet = CharSet.Unicode)]
-    private struct STARTUPINFO
-    {
-        public int cb;
-        public string lpReserved;
-        public string lpDesktop;
-        public string lpTitle;
-        public uint dwX;
-        public uint dwY;
-        public uint dwXSize;
-        public uint dwYSize;
-        public uint dwXCountChars;
-        public uint dwYCountChars;
-        public uint dwFillAttribute;
-        public uint dwFlags;
-        public short wShowWindow;
-        public short cbReserved2;
-        public IntPtr lpReserved2;
-        public IntPtr hStdInput;
-        public IntPtr hStdOutput;
-        public IntPtr hStdError;
-    }
-
-    [StructLayout(LayoutKind.Sequential)]
-    private struct PROCESS_INFORMATION
-    {
-        public IntPtr hProcess;
-        public IntPtr hThread;
-        public uint dwProcessId;
-        public uint dwThreadId;
-    }
-
-    [StructLayout(LayoutKind.Sequential)]
-    private struct JOBOBJECT_BASIC_LIMIT_INFORMATION
-    {
-        public long PerProcessUserTimeLimit;
-        public long PerJobUserTimeLimit;
-        public uint LimitFlags;
-        public UIntPtr MinimumWorkingSetSize;
-        public UIntPtr MaximumWorkingSetSize;
-        public uint ActiveProcessLimit;
-        public UIntPtr Affinity;
-        public uint PriorityClass;
-        public uint SchedulingClass;
-    }
-
-    [StructLayout(LayoutKind.Sequential)]
-    private struct IO_COUNTERS
-    {
-        public ulong ReadOperationCount;
-        public ulong WriteOperationCount;
-        public ulong OtherOperationCount;
-        public ulong ReadTransferCount;
-        public ulong WriteTransferCount;
-        public ulong OtherTransferCount;
-    }
-
-    [StructLayout(LayoutKind.Sequential)]
-    private struct JOBOBJECT_EXTENDED_LIMIT_INFORMATION
-    {
-        public JOBOBJECT_BASIC_LIMIT_INFORMATION BasicLimitInformation;
-        public IO_COUNTERS IoInfo;
-        public UIntPtr ProcessMemoryLimit;
-        public UIntPtr JobMemoryLimit;
-        public UIntPtr PeakProcessMemoryUsed;
-        public UIntPtr PeakJobMemoryUsed;
-    }
-
-    [StructLayout(LayoutKind.Sequential)]
-    private struct JOBOBJECT_BASIC_ACCOUNTING_INFORMATION
-    {
-        public long TotalUserTime;
-        public long TotalKernelTime;
-        public long ThisPeriodTotalUserTime;
-        public long ThisPeriodTotalKernelTime;
-        public uint TotalPageFaultCount;
-        public uint TotalProcesses;
-        public uint ActiveProcesses;
-        public uint TotalTerminatedProcesses;
-    }
-
-    private sealed class CaptureState
-    {
-        public long CombinedBytes;
-        public int Overflow;
-        public long Limit;
-        public IntPtr Job;
-    }
-
-    [DllImport("kernel32.dll", CharSet = CharSet.Unicode, SetLastError = true)]
-    private static extern IntPtr CreateJobObject(IntPtr attributes, string name);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool SetInformationJobObject(
-        IntPtr job,
-        int informationClass,
-        ref JOBOBJECT_EXTENDED_LIMIT_INFORMATION information,
-        uint informationLength);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool QueryInformationJobObject(
-        IntPtr job,
-        int informationClass,
-        out JOBOBJECT_BASIC_ACCOUNTING_INFORMATION information,
-        uint informationLength,
-        IntPtr returnLength);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool AssignProcessToJobObject(IntPtr job, IntPtr process);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool TerminateJobObject(IntPtr job, uint exitCode);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool CreatePipe(
-        out IntPtr readPipe,
-        out IntPtr writePipe,
-        ref SECURITY_ATTRIBUTES attributes,
-        uint size);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool SetHandleInformation(
-        IntPtr handle,
-        uint mask,
-        uint flags);
-
-    [DllImport("kernel32.dll", CharSet = CharSet.Unicode, SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool CreateProcessW(
-        string applicationName,
-        StringBuilder commandLine,
-        IntPtr processAttributes,
-        IntPtr threadAttributes,
-        [MarshalAs(UnmanagedType.Bool)] bool inheritHandles,
-        uint creationFlags,
-        IntPtr environment,
-        string currentDirectory,
-        ref STARTUPINFO startupInfo,
-        out PROCESS_INFORMATION processInformation);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    private static extern uint ResumeThread(IntPtr thread);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool GetExitCodeProcess(IntPtr process, out uint exitCode);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool TerminateProcess(IntPtr process, uint exitCode);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    private static extern uint WaitForSingleObject(IntPtr handle, uint milliseconds);
-
-    [DllImport("kernel32.dll", SetLastError = true)]
-    [return: MarshalAs(UnmanagedType.Bool)]
-    private static extern bool CloseHandle(IntPtr handle);
-}

package/assets/runtime/windows-job-supervisor/windows_job_process_supervisor.ps1

@@ -1,117 +0,0 @@
-Set-StrictMode -Version Latest
-$ErrorActionPreference = 'Stop'
-
-$utf8 = New-Object System.Text.UTF8Encoding($false)
-[Console]::InputEncoding = $utf8
-[Console]::OutputEncoding = $utf8
-
-if ([System.Environment]::OSVersion.Platform -ne [System.PlatformID]::Win32NT) {
-    throw 'formal_process_supervisor_platform_unsupported'
-}
-
-$nativeSources = @(
-    Join-Path $PSScriptRoot 'formal_process_supervisor_native_types.cs'
-    Join-Path $PSScriptRoot 'formal_process_supervisor_native_run.cs'
-    Join-Path $PSScriptRoot 'formal_process_supervisor_native_helpers.cs'
-)
-Add-Type -Path $nativeSources
-
-function Get-ExactProperty {
-    param(
-        [Parameter(Mandatory = $true)] [object] $Object,
-        [Parameter(Mandatory = $true)] [string] $Name
-    )
-    $matches = @($Object.PSObject.Properties | Where-Object { $_.Name -ceq $Name })
-    if ($matches.Count -ne 1) { throw 'formal_process_supervisor_request_shape' }
-    return $matches[0]
-}
-
-while (($line = [Console]::In.ReadLine()) -ne $null) {
-    if ([string]::IsNullOrWhiteSpace($line)) { continue }
-    $request = $null
-    $requestId = $null
-    $requestStage = 'json'
-    try {
-        [FormalProcessSupervisor]::AssertUniqueJsonObjectKeys($line)
-        $request = $line | ConvertFrom-Json
-        if ($null -eq $request -or $request -is [System.Array] -or $request -is [string]) {
-            throw 'formal_process_supervisor_request_shape'
-        }
-        $expected = @('schema_version', 'request_id', 'executable', 'argv', 'cwd', 'stdout_path', 'stderr_path', 'timeout_ms', 'combined_output_limit_bytes', 'environment')
-        $actual = @($request.PSObject.Properties | ForEach-Object { $_.Name } | Sort-Object)
-        $requestStage = 'fields'
-        if (@(Compare-Object ($expected | Sort-Object) $actual -CaseSensitive).Count -ne 0) {
-            throw 'formal_process_supervisor_request_shape'
-        }
-        $requestStage = 'properties'
-        $schemaVersion = (Get-ExactProperty $request 'schema_version').Value
-        $requestId = (Get-ExactProperty $request 'request_id').Value
-        $executable = (Get-ExactProperty $request 'executable').Value
-        $argv = (Get-ExactProperty $request 'argv').Value
-        $cwd = (Get-ExactProperty $request 'cwd').Value
-        $stdoutPath = (Get-ExactProperty $request 'stdout_path').Value
-        $stderrPath = (Get-ExactProperty $request 'stderr_path').Value
-        $timeoutMs = (Get-ExactProperty $request 'timeout_ms').Value
-        $combinedOutputLimit = (Get-ExactProperty $request 'combined_output_limit_bytes').Value
-        $environmentObject = (Get-ExactProperty $request 'environment').Value
-        $requestStage = 'values'
-        if ($schemaVersion -isnot [string] -or $schemaVersion -cne 'formal-process-supervisor-request-v1' -or
-            $requestId -isnot [string] -or $executable -isnot [string] -or $cwd -isnot [string] -or
-            $stdoutPath -isnot [string] -or $stderrPath -isnot [string] -or
-            $argv -isnot [System.Array] -or
-            (($timeoutMs -isnot [int]) -and ($timeoutMs -isnot [long])) -or
-            (($combinedOutputLimit -isnot [int]) -and ($combinedOutputLimit -isnot [long])) -or
-            $null -eq $environmentObject -or $environmentObject -is [System.Array] -or $environmentObject -is [string]) {
-            throw 'formal_process_supervisor_request_shape'
-        }
-        foreach ($argument in $argv) {
-            if ($argument -isnot [string]) { throw 'formal_process_supervisor_request_shape' }
-        }
-        $requestStage = 'environment'
-        $seenEnvironment = @{}
-        $environment = @(
-            $environmentObject.PSObject.Properties |
-                Sort-Object Name |
-                ForEach-Object {
-                    $environmentName = [string]$_.Name
-                    if ($seenEnvironment.ContainsKey($environmentName)) {
-                        throw ('formal_process_supervisor_request_shape:environment_duplicate:{0}' -f $environmentName)
-                    }
-                    if ([string]::IsNullOrEmpty($environmentName) -or
-                        $environmentName.IndexOf([char]61) -ge 0 -or
-                        $environmentName.IndexOf([char]0) -ge 0 -or
-                        $environmentName.IndexOf([char]13) -ge 0 -or
-                        $environmentName.IndexOf([char]10) -ge 0) {
-                        throw ('formal_process_supervisor_request_shape:environment_name:{0}' -f $environmentName)
-                    }
-                    if ($_.Value -isnot [string]) {
-                        throw ('formal_process_supervisor_request_shape:environment_value:{0}:{1}' -f $environmentName, $_.Value.GetType().FullName)
-                    }
-                    $seenEnvironment[$environmentName] = $true
-                    '{0}={1}' -f $environmentName, $_.Value
-                }
-        )
-        $requestStage = 'native_run'
-        $result = [FormalProcessSupervisor]::Run(
-            [string]$requestId,
-            [string]$executable,
-            [string[]]$argv,
-            [string]$cwd,
-            [string]$stdoutPath,
-            [string]$stderrPath,
-            [int]$timeoutMs,
-            [long]$combinedOutputLimit,
-            [string[]]$environment
-        )
-        [Console]::Out.WriteLine(($result | ConvertTo-Json -Compress -Depth 8))
-        [Console]::Out.Flush()
-    }
-    catch {
-        $failure = [ordered]@{
-            RequestId = if ($requestId -is [string]) { [string]$requestId } else { $null }
-            Error = '{0}:{1}' -f $requestStage, [string]$_.Exception.Message
-        }
-        [Console]::Out.WriteLine(($failure | ConvertTo-Json -Compress))
-        [Console]::Out.Flush()
-    }
-}

package/assets/skills/context_development_engineer/SKILL.md

@@ -1,58 +0,0 @@
----
-name: context_development_engineer
-description: Use when the user asks for an architecture or engineering design, technical design/plan, complex implementation design, high-level engineering assessment, 架构方案/工程设计/技术设计/复杂实现方案/系统拆分/工程取舍/架构审计, or when the actual task content materially requires owner/source-of-truth, API/schema/data/state/lifecycle, dependency, complex alternatives, concurrency/recovery, external-integration/shared-abstraction, performance, security, compatibility/migration, implementation tradeoff, or architecture-audit judgment. Do not trigger merely for routine coding, local bug fixes, small refactors, tests, documentation, styling, package/release work, generic requests to implement/build/change code, a generic implementation plan, role-only mentions, or mentions of multi-agent, subagent, or parallel work.
----
-
-# Context Development Engineer
-
-## Scope
-
-Add engineering-design and architecture judgment to the default Workflow Contract. This Skill is not the default implementation workflow, a coding persona, planner, agent allocator or verification authority. Routine implementation continues under root `AGENTS.md`.
-
-Project-specific engineering rules belong in `<harnessRoot>/skills/development_engineer/SKILL.md`; the repo-local Skill is more specific, while durable conclusions still belong in `project_context/**`.
-
-With a valid Long-Task binding, `long-task-workflow` alone owns its lifecycle and Final Gate. This Skill contributes architecture judgment only and creates no second plan, stage, delegation policy/state or acceptance path.
-
-## Progressive reasoning reference
-
-Read [engineering-design-reasoning.md](references/engineering-design-reasoning.md) completely. Apply only the methods triggered by actual uncertainty and risk; this is not a checklist, artifact schema or required sequence. An explicit-owner task without material design uncertainty stays on the lightweight default path.
-
-## Engineering-design workflow
-
-1. Read required core/default and implicated-owner Context. Before `Context Delta`, run the default bounded high-signal Context search; widen only for discovered dependency or semantic ownership.
-2. State the problem, success boundary and non-goals. Separate facts, constraints, assumptions and unknowns, and Source/Context requirements from current-code behavior.
-3. Identify the existing source of truth and extension point, affected owners, dependency direction, public/internal interfaces, state and lifecycle, failure/recovery boundaries, compatibility constraints and project-native verification entries.
-4. Compare the smallest material alternatives. Prefer the existing owner/facade/adapter when it carries the stable concept; introduce an abstraction only for an evidenced change axis or durable boundary with positive net value. When foundational machinery, a mature protocol/security boundary, a dependency/shared abstraction or a nearby extension point makes sourcing material, add the risk-triggered Build / Reuse / Buy judgment below.
-5. Before implementation edits, surface one externally observable, repository-bound `Architecture Deliberation`: selected design, rejected material alternatives, one plausible future-change challenge, touched technical debt and disposition, forbidden shortcuts, checks, and triggered quality attributes or preservation basis.
-6. Decide exactly one `Context Delta: none|required`. Durable ownership, architecture, API/schema/data, state/recovery, dependency, compatibility, verification/deployment or rationale changes are `required` and update the smallest owning Context before code. A task-local design that preserves those facts is `none`.
-7. Implement under the current Goal and Workflow Contract. After current-candidate checks, include Engineering/Architecture Conformance in default Contract Conformance, then run the separate Context drift check. Add no gate or proof ledger.
-
-## Architecture Deliberation content
-
-Risk changes depth, not whether the checkpoint occurs. Name the controlling Context/code path, concrete owner and unique source of truth, extension point, dependency direction and prohibited bypass; API/schema/data inputs/outputs; interface, state and lifecycle boundaries; material failure/recovery/resource-release behavior; and triggered concurrency, security or compatibility boundaries. State the selected design, material alternatives, a realistic future-change landing without duplicate truth or reverse dependency, technical debt disposition or bounded project-owned exception, forbidden shortcuts, and project-owned type/lint/AST/dependency/contract/behavior/benchmark/probe checks.
-
-Always judge correctness/invariants and maintainability/changeability. Activate reliability/resource lifecycle, concurrency/consistency, performance/capacity/cost, security/privacy/safety, compatibility/migration/rollout and operability/observability/testability only when material. A performance claim requires workload, metric, baseline/budget, environment, comparator/tolerance and project-owned measurement; static shape is not runtime proof.
-
-Refresh the deliberation if scope, ownership, dependency direction, selected design, quality applicability or debt disposition materially changes.
-
-### Risk-triggered Build / Reuse / Buy
-
-Record an `allowed solution set`, `prohibited failure modes` and `required rationale/evidence`, not one required library or abstraction. Choices may include the owning service/facade/adapter, standard library, installed dependency, mature compatible external library, small bounded self-implementation or intentional non-abstraction.
-
-Enumerate every materially supported member before selecting one; selection never removes another supported member from the allowed set. Judge the viable set, retain each unselected but legal member as an alternative, and prohibit only a choice which actually exhibits a prohibited failure mode. `block` needs no supported member or missing safety/compatibility evidence; `decision-required` needs a genuine user/product/external choice.
-
-Reject duplicate owner-held rules, extension-point bypass, an unjustified heavy dependency, plainly incomplete reinvention of mature security-sensitive behavior, incompatible license/platform support, forced abstraction over structurally similar but semantically different code and a second source of truth for one stable rule. Do not add a mandatory open-source preference, DRY rule, generic quality score, artifact, stage or Gate. Conformance asks only whether the selected choice is in the allowed set, avoids prohibited failures and has risk-proportional current evidence.
-
-## Boundary routing
-
-Product goals and acceptance meaning belong to `context_product_plan`. Durable main/drilldown/surface information/action/feedback responsibility belongs to `context_surface_contract`. Durable Design Authority and UI Authority Closure belong to `context_uiux_design`. New design-resource generation/handoff belongs to `design-resource-authoring`. Exact non-UI semantic facts remain owned by Source/Context; exact selected UI values remain owned by selected-design closure.
-
-For monorepos, distinguish expandable read scope from intended/supporting workspaces. Existing Context workspace mappings are semantic routing rather than edit authorization or read ACLs. Do not add workspace registries, topology scans or empty Context mirrors.
-
-For capability scope, distinguish reusable system capability, representative sample validation, full-population operation and explicit non-requirement. A sample cannot prove an all-provider/all-interface/all-platform claim; unresolved scope remains decision-required.
-
-## Output
-
-Return a concise engineering design or assessment: selected owner/extension point, boundaries and invariants, alternatives/trade-offs, future-change/debt judgment, implementation surfaces, verification strategy, decision-required gaps and `Context: updated ...` or `Context: no durable fact change`.
-
-Do not create a required `plan.md`, Task Contract, architecture matrix, verdict, evidence ledger, generic analyzer, phase, lifecycle or second Authority/Gate. Do not claim checks or product acceptance that were not run on the current candidate.

package/assets/skills/context_development_engineer/references/engineering-design-reasoning.md

@@ -1,93 +0,0 @@
-# Engineering Design Reasoning
-
-Use this reference only after `context_development_engineer` has been selected for material engineering-design or architecture judgment. It deepens the existing Architecture Deliberation; it does not create a design phase, plan artifact, evidence ledger, second workflow or acceptance carrier. Apply the smallest useful subset below and state when a method is not material.
-
-## 1. Frame what is actually known
-
-Separate four categories before choosing a design:
-
-- **Facts:** user/Source/Context requirements, repository owners and extension points, observed code/test behavior and externally verified dependency facts.
-- **Constraints:** compatibility, platform, policy, budget, rollout, security, data, lifecycle and scope boundaries that a legal solution must preserve.
-- **Assumptions:** plausible but unproved premises currently needed to proceed. Name who can validate them and what changes if they are false.
-- **Unknowns:** missing information that distinguishes alternatives, changes safety or makes an acceptance claim unsupported.
-
-Current code is implementation evidence, not silent product or architecture authority. A genuine product, legal, security, commercial, safety or external choice remains `decision-required`; implementation-equivalent freedom belongs to the current Goal.
-
-## 2. Identify drivers and path dependence
-
-Name the few forces that materially shape the solution: owner/source-of-truth location, dependency direction, data/state boundaries, lifecycle and failure semantics, compatibility commitments, load/threat conditions and verification reachability. Distinguish an enduring invariant from historical path dependence such as an old API, migration window, installed dependency or deployment constraint. Preserve path dependence only while its reason still applies; do not mistake legacy shape for the desired architecture.
-
-For each material driver, point to repository evidence or authoritative external evidence. If current dependency/library behavior matters and may have changed, use current primary documentation rather than memory.
-
-## 3. Build the smallest material alternative set
-
-Enumerate only alternatives that could plausibly change an owner, boundary, lifecycle, dependency, operational risk or future change cost. Include the current extension point or intentional non-abstraction when viable. When sourcing is material, express Build / Reuse / Buy as the existing allowed solution set, prohibited failure modes and required rationale/evidence.
-
-Steelman every material alternative before rejecting it:
-
-- where it fits the requirements well;
-- its cleanest owner and dependency direction;
-- the strongest reason a competent maintainer would select it; and
-- the evidence or condition under which it would become preferable.
-
-Do not manufacture alternatives for a local choice whose owner and semantics are already explicit. Do not relabel an unselected allowed option as a prohibited failure.
-
-## 4. Use counterfactuals and failure paths
-
-Challenge the leading design with at least one realistic adjacent change and one relevant failure:
-
-- If the next client, provider, state, data volume, permission model or workflow variation arrives, which existing extension point absorbs it?
-- If the selected dependency is unavailable, stale, slow, partial or incompatible, which failure is visible and where does recovery live?
-- If the main assumption is false, which decision changes and which parts remain valid?
-- What would make the rejected alternative win?
-
-Trace only triggered retry, timeout, cancellation, idempotency, transaction, concurrency, consistency, degradation, recovery and resource-release semantics. A family that is not material gets a concise preservation basis rather than invented machinery.
-
-## 5. Select risk-triggered methods
-
-Choose methods for the actual uncertainty; never run all of them by default:
-
-| Trigger | Useful method | Minimum output |
-| --- | --- | --- |
-| Unclear owner or dependency boundary | Repository owner/extension-point trace | One source of truth, legal dependency direction and prohibited bypass |
-| API/schema/data/state change | Contract and state-transition analysis | Inputs/outputs/errors, invariants, ownership, compatibility and recovery |
-| Shared mutable state or parallel execution | Interleaving/consistency analysis | Atomicity boundary, ordering, idempotency and failure recovery |
-| External integration or mature protocol | Current primary-source and repository-fit research | Supported allowed set, compatibility/security/maintenance evidence |
-| Material performance/capacity/cost risk | Complexity model plus project-owned measurement | Workload, metric, baseline/budget, environment and comparator/tolerance |
-| Trust, permission or sensitive data boundary | Threat/abuse-path analysis | Assets, actors, trust crossings, prohibited failures and attributable checks |
-| Public or versioned compatibility change | Migration/rollout analysis | Compatibility window, upgrade/rollback path and current-version evidence |
-| High uncertainty that code can cheaply resolve | Minimum architecture experiment | Hypothesis, smallest observable probe, budget and exit condition |
-
-Research or an experiment informs the decision but is not durable authority or product acceptance. Preserve only stable conclusions in their owning Context.
-
-## 6. Design a minimum architecture experiment
-
-Use an experiment only when a material unknown distinguishes legal alternatives and repository inspection or authoritative documentation cannot answer it cheaply. Define:
-
-- the exact question and competing hypotheses;
-- the smallest representative fixture or probe that can falsify the leading assumption;
-- environment, inputs, metric/observation and comparator;
-- time/resource budget and stop condition; and
-- how each possible result changes the design.
-
-Do not turn a spike into production by default. Representative input proves only its declared scope; it cannot establish an all-provider, all-interface, all-platform or full-population claim.
-
-## 7. Project the decision into implementation
-
-Before handoff to the current Goal, make the design concrete enough to implement without inventing a second architecture:
-
-- owning modules, paths and symbols plus the existing extension point;
-- public/internal interfaces, inputs, outputs and explicit error semantics;
-- data and state owner, persistence boundary and invariants;
-- runtime/resource lifecycle, initialization, cleanup, recovery and observability;
-- dependency direction and forbidden shortcuts;
-- compatibility/migration/rollout handling when applicable;
-- the smallest complete implementation surface and any intentional non-goals;
-- project-owned type/lint/AST/dependency/contract/behavior/benchmark/probe checks; and
-- `Context Delta: none|required`, with the smallest durable owner updated before code when required.
-
-## Architecture audit route
-
-For an audit, compare the current implementation against controlling Source/Context and the concrete owner/boundary model above. Report wrong owner, duplicate truth, reversed dependency, extension-point bypass, silent failure, incomplete lifecycle/recovery, unsupported quality claim and new/worsened debt separately. Distinguish observed defects from assumptions and unverified risks. Do not implement repairs unless the request also authorizes change.
-
-The final current-candidate Engineering/Architecture Conformance remains in the existing default Contract Conformance or, when validly active, the sole Long-Task Final Gate. This reference creates neither.

package/assets/skills/context_full_project_export/SKILL.md

@@ -1,70 +0,0 @@
----
-name: context_full_project_export
-description: Use when the user explicitly asks to 导出尽可能详细的项目全量上下文, 全量上下文导出, 项目上下文全量导出, 项目整体上下文, full project context export, export full project context, project context export, project overall context, Source Pack export, source-pack export, code index export, task context export, 当前项目代码实现, 代码级实现导出, or code-level implementation export in a Minimal Context Harness project.
----
-
-# Context Full Project Export
-
-## Package-Managed Boundary
-
-This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_full_project_export` Skill directly.
-
-This Skill creates a temporary export artifact only. It does not author durable Context and does not change `project_context/context.toml`.
-
-## Purpose
-
-When the user needs a full project context export, project overall context export or external LLM handoff, create temporary export artifacts that collect project Context, key agent guidance, architecture/module facts, code navigation and bounded source support for copying into an external tool or one-off discussion.
-
-When the user needs a code-level implementation export, create one temporary Markdown snapshot of current source and engineering configuration files for upload to Web GPT or another external model.
-
-## Workflow
-
-1. Prefer the bounded Source Pack for external LLM / Web GPT planning. It writes at most 5 files total under `tmp/ty-context/context-exports/latest/` and removes old timestamped export rounds:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --source-pack`
-2. Use `--code-index` when implementation navigation is enough and full source bodies are not needed:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code-index`
-3. Use `--task-context <name>` for focused handoff, preferably with a profile or explicit include selectors:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --profile <profile-id>`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --include-context project_context/areas/main.md --include-code 'src/example/**'`
-4. Use legacy `--all` when the user explicitly wants both old temporary artifacts in one command. Do not hand-write tracked export documents:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --all`
-5. Use legacy `--full` when only the project Context bundle is needed:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --full`
-6. Use legacy `--code` when only the full code-level implementation snapshot is needed. It generates one Markdown file by default and is the full fallback when Source Pack bundles are not enough:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code`
-7. Custom output paths are allowed only for legacy single-artifact modes and must stay under the temporary export directory. `--all` and Source Pack modes do not accept `--output`:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --full --output tmp/ty-context/context-exports/my-export.md`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code --output tmp/ty-context/context-exports/my-code-export.md`
-8. Use dry-run mode to inspect planned sources before writing:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --source-pack --check`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code-index --check`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --task-context <name> --check`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --all --check`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --full --check`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context export-context --code --check`
-9. After exporting, report artifact paths, source counts, recommended upload sets and warnings to the user. Do not summarize export contents back into Context.
-
-## Output Boundaries
-
-- Export artifacts must remain temporary export artifacts, not Context.
-- `--source-pack` defaults to `tmp/ty-context/context-exports/latest/`, with `source-pack-manifest.json`, `full-project-context.md`, `code-index.md` and optional `code-bundle-core.md` / `code-bundle-extended.md`.
-- `--source-pack` and `--task-context` are capped at 5 output files. `--max-pack-files` cannot exceed 5.
-- `--code-index` creates a navigation index and manifest without complete source bodies.
-- `--task-context <name>` creates `task-contexts/task-context-<name>.md` plus optional support bundle; profile verification entries are listed, not executed.
-- `--full` defaults to `tmp/ty-context/context-exports/full-project-context-<timestamp>.md`.
-- `--code` defaults to `tmp/ty-context/context-exports/code-level-implementation-<timestamp>/code-level-implementation.md`.
-- `--all` generates both default artifacts with the same timestamp.
-- `--all` does not accept `--output`; custom filenames are supported only for `--full` or `--code`.
-- `--code` creates one Markdown file, not shards or `all.md`.
-- Do not output to `project_context/**`.
-- Do not modify `project_context/context.toml`.
-- Do not register export artifacts as `[[context]]`, `implementation-index` or any Context graph node.
-- Do not write tracked docs; if the user asks for an ordinary docs path, redirect to `tmp/ty-context/context-exports/**`.
-- Export contents may include redaction warnings; do not bypass secret/token/cookie/password/api_key/credential/bearer/authorization filtering. Use `--redaction-strict` when the user wants the command to fail if any redaction occurred.
-- Profiles under `<harnessRoot>/config.yaml` are export selectors only. They must not become durable Context facts or execute verification commands.
-
-## Handoff
-
-- Report `Export: generated <path>` or `Export: check completed; no files written`.
-- If the CLI rejects an output path, explain that this prevents temporary exports from polluting durable fact sources and suggest `tmp/ty-context/context-exports/<name>.md`.
-- Context drift check should be `Context: no durable project facts changed` unless the task also changes Harness rules.

package/assets/skills/context_harness_upgrade/SKILL.md

@@ -1,60 +0,0 @@
----
-name: context_harness_upgrade
-description: Use when the user asks to upgrade Tiny Context, update Tiny Context, use the Tiny Context upgrade skill to upgrade this project, upgrade project-tiny-context-harness, run ty-context upgrade, run make ty-context-upgrade, Project Tiny Context Harness upgrade, 用 Tiny Context upgrade skill 升级这个项目, 升级 tiny context, 升级tiny context, or 更新 project-tiny-context-harness in a Minimal Context Harness project.
----
-
-# Context Harness Upgrade
-
-## Package-Managed Boundary
-
-This Skill is generated by `ty-context sync` and owned by the Harness package. Do not edit the generated `context_harness_upgrade` Skill directly.
-
-This Skill handles Harness package upgrade and migration orchestration only. It does not author product facts, refactor business code, replace project tests or prove application quality.
-
-## Purpose
-
-When the user asks to upgrade Tiny Context / Project Tiny Context Harness in an existing project, run the canonical `upgrade` path, handle only migration-scoped follow-up, and leave durable project semantics to the project Context and user-owned code. A `sync-only` release means no new migration is expected; it does not change the default upgrade entry for explicit upgrade requests.
-
-## Workflow
-
-1. Read the project routing and Context entry points before changing files:
-   - `AGENTS.md`
-   - `project_context/global.md`
-   - `project_context/architecture.md`
-   - `project_context/context.toml`
-2. Inspect the working tree with `git status --short`. Do not revert unrelated user changes.
-3. Prefer project wrappers when present:
-   - `make ty-context-sync`
-   - `make ty-context-upgrade`
-   - `make ty-context-doctor`
-   - `make validate-context`
-4. If no wrapper exists, use the package CLI explicitly:
-   - `npx --yes --package project-tiny-context-harness@latest ty-context sync`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context upgrade --check`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context upgrade`
-   - `npx --yes --package project-tiny-context-harness@latest ty-context doctor`
-5. Run `upgrade --check` when useful, then run `upgrade`. This remains the default after package updates and for explicit upgrade requests because it plans migrations, applies safe migrations, refreshes managed assets and runs diagnostics.
-6. Do not run standalone `sync` before `upgrade` for explicit upgrade requests. A direct `sync` is only a shortcut for releases explicitly marked `sync-only` when the user asks for managed-asset refresh instead of upgrade diagnostics.
-7. Do not run standalone `sync` after a successful `upgrade` unless the project wrapper did not run sync or the user explicitly asks for another managed-asset refresh.
-8. If `upgrade --check` or `upgrade` reports only `safe_pending` items and the command succeeds, do not invent additional manual cleanup.
-9. If the report includes `manual_required` or `blocked`, handle only the listed migration scope. Use `project_context/context.toml`, role placement scan and the existing area graph to decide placement. Do not guess product or business semantics.
-10. If the report includes `blocked`, treat it as a write preflight failure: resolve the blocked migration scope and rerun `upgrade` before expecting safe migrations or managed asset sync to have been applied.
-11. Run diagnostics after migration-scoped follow-up:
-   - `make ty-context-doctor` or the CLI `doctor`
-   - `make validate-context`
-12. Report commands run, migration status, diagnostics, files changed and any remaining manual items. Use `Context: no durable project facts changed` unless the upgrade exposed or required a real long-term project fact change.
-
-## Manual Handling Rules
-
-- `manual_required` means the Harness detected a migration-scoped item but cannot safely choose the project meaning. Fix it only when the existing Context or file structure proves the intended placement.
-- `blocked` means the safe target already exists or another conflict prevents a mechanical write. Do not overwrite. Compare source and target, preserve user content and ask for direction if the conflict cannot be resolved from project facts.
-- Deprecated override Skills under `ty-context-managed/override_skills/**` should be migrated to standalone project-local Skills only when their content is still relevant. Do not merge them into package-managed default Skills.
-- Ambiguous Context roles should not be guessed from filenames like `api.md`, `notes.md` or `main.md` alone. Register a role only when the manifest, path convention or durable content makes it clear.
-- If `upgrade` creates default `project_context/areas/main.md` or `project_context/areas/main/verification.md` but `project_context/context.toml` already declares real project areas and does not register `main`, remove those generated defaults instead of preserving them as durable project facts. If `main` is registered or contains user-authored facts, do not delete it automatically.
-
-## Boundaries
-
-- Do not restore legacy stage workflow, sprint documents or phase gates.
-- Do not modify application code, product behavior, deployment settings or tests unless the user explicitly asks or a migration report points to a Harness-owned file in that scope.
-- Do not write one-off command output, release logs, diagnostics or temporary migration notes into `project_context/**`.
-- Do not edit package-managed generated surfaces directly in a consumer project unless the change is part of a migration conflict that cannot be resolved another way. Prefer rerunning `upgrade` / `sync` from the package source.