dsh-live-voice 0.0.1-developing

package/AGENTS.md

@@ -0,0 +1,52 @@
+# Agent Instructions
+
+## Project identity and current stage
+
+- Project: **DSH Live Voice**; npm package: `dsh-live-voice`.
+- Current version: `0.0.1-developing`. This repository is a documentation-only development placeholder, not a functioning DSH plugin.
+- Read `README.md`, `HISTORY.md`, and `package.json` before making project changes.
+- Write repository documentation, code comments, and public package metadata in English. Keep the requested filename `HISTORY.md`.
+
+## Product priorities
+
+- Lead with **local-first voice conversations**. Both STT and TTS should be able to run on the user’s machine. External providers are optional.
+- Do not claim full offline operation merely because voice processing is local; the DSH language model can be remote.
+- Coordinate input and output in one plugin. Preserve separate states for capture/recognition, synthesis/playback, and agent generation.
+- Keep pause, resume, and cancel distinct. Do not automatically resume obsolete speech just because the user becomes silent.
+- Plan for speaker mode with recognition gating and manual interruption, and headphone mode with open-microphone interruption. Exact policies remain undecided.
+- Capability detection must distinguish the DSH host from the browser/device environment. Do not assume OS detection proves feature support or that a browser shortcut is global.
+- Make capture, recognition, transmission, playback, and permission states understandable to users. Avoid recording or logging raw audio/transcripts by default.
+
+## History is strictly append-only
+
+**Never edit, delete, reorder, reformat, or replace existing content in `HISTORY.md`.**
+
+When a history update is requested or a meaningful approved decision needs recording:
+
+1. Read the existing file.
+2. Preserve its entire existing content exactly.
+3. Append a new English entry at the end using the actual local date (`YYYY-MM-DD`) and a descriptive heading.
+4. Explain what changed and why; distinguish proposals, decisions, and completed implementation.
+5. If correcting or reversing an earlier statement, reference it in the new entry rather than modifying it.
+
+Do not invent approvals, dates, completed work, or releases. Do not add secrets or sensitive data. Other documentation may be updated normally to reflect the current state; history preserves the evolution.
+
+## Implementation discipline
+
+- Inspect actual DSH extension APIs before selecting integration points. Do not fabricate hooks, plugin manifests, install commands, or support guarantees.
+- Existing STT/TTS plugin reuse versus direct engine integration is unresolved.
+- Keep conversation policy separate from provider adapters and UI.
+- Do not implement features or add dependencies just to make the placeholder look complete.
+- Keep planned capabilities clearly labeled until implemented and validated.
+- Future audio work must account for echo, false interruptions, recognition latency, playback position, and stale asynchronous results after cancellation.
+- Third-party engines and model weights require their own license and platform checks. This repository uses GPL-3.0-only. Commercial use and paid redistribution are allowed subject to GPL obligations; do not describe the license as non-commercial. Check DSH and dependency license compatibility before integration.
+
+## Packaging and authorization
+
+- Keep public metadata and README aligned with the local-first focus.
+- Do not invent author or repository URLs.
+- Use explicit `--tag developing` for this prerelease. Never silently promote it to `latest`.
+- `npm publish --dry-run --tag developing` validates packaging without publishing; it does not reserve a name or prove registry authorization.
+- No automated test suite or runnable plugin exists yet. Report validation honestly; do not describe a package dry run as a runtime test.
+- Commit, push, actual npm publication, and secondary package creation require explicit maintainer authorization.
+- The maintainer supplied `git@github.com:victorwads/dsh-live-voice.git` and authorized the first commit and push to `main`. npm publication requires separate authorization.

package/HISTORY.md

@@ -0,0 +1,94 @@
+# DSH Live Voice — Project History
+
+## Append-only contract
+
+This file is a historical record, not a document to continuously rewrite. Its content is written in English; its filename is intentionally `história.md`.
+
+**All future updates MUST be append-only. This rule applies to humans and AI agents.**
+
+- Preserve all existing text, entries, dates, and ordering.
+- Append new entries at the end of the file. Never edit, delete, reorder, or silently correct earlier entries.
+- Record corrections, reversals, and superseded decisions in a new entry that references the earlier entry. The past must remain visible.
+- Use the actual local date in `YYYY-MM-DD` format. Multiple entries on the same date may use distinct descriptive headings.
+- Describe the change, its reason, its status (decision, proposal, or implemented work), and any unresolved questions.
+- Do not invent decisions, implementation progress, releases, or user approval.
+- Keep credentials, tokens, and sensitive personal information out of this record.
+
+## 2026-09-14 — Initial vision and documentation baseline
+
+### Origin and problem
+
+The project began in an empty repository as a discussion about a new DSH plugin. The maintainer wanted to agree on the experience and responsibility boundaries before implementing code.
+
+Existing STT and TTS plugins can operate independently without coordinating their states. Assistant audio can leak from speakers into the microphone, damaging a user recording or being transcribed as user speech. Users also need a practical way to interrupt ongoing assistant playback.
+
+The desired experience resembles talking with another person, while acknowledging the latency and limitations of a pipeline based on STT and TTS. The product should coordinate both directions within one plugin.
+
+### Identity and distribution
+
+The selected primary name is **DSH Live Voice**, with the repository and npm identifier `dsh-live-voice`. Other names discussed included `dsh-live-conversation`, `dsh-voice-conversation`, `dsh-realtime-conversation`, `dsh-realtime-voice`, `dsh-nonstop-conversation`, and later `dsh-live-voice-conversation`. The maintainer reported that `dsh-live-mode` was already used by a competitor. The shorter `dsh-live-voice` remained the preferred name.
+
+The maintainer expressed interest in reserving `dsh-live-voice` and `dsh-voice-conversation` on npm, starting with the former. The current repository only prepares `dsh-live-voice`; no secondary package has been created. Name availability and ownership are not established by local files or a dry run.
+
+The initial package version is `0.0.1-developing`. It is a documentation-only placeholder, not a functional or installable DSH plugin. Publication should use the explicit `developing` dist-tag rather than `latest`. No npm publication, commit, or push has been performed as part of this preparation.
+
+### Local-first clarification
+
+The maintainer clarified that the primary value is running both speech recognition and speech synthesis on the user’s own machine. External providers should be optional alternatives, not mandatory infrastructure. Accordingly, public descriptions should start with **local-first voice conversations**, rather than leading with real-time operation.
+
+Local voice does not imply a fully offline DSH language model. No local engine, cloud provider, model, or hardware requirement has been selected. English documentation and relevant local-first/STT/TTS keywords are intended to help people discover, use, and share the project.
+
+### Intended conversational behavior
+
+- A single coordinator manages listening and speaking, while allowing multiple underlying speech engines.
+- In speaker mode, assistant playback gates microphone input to recognition. A hotkey lets the user take over and interrupt playback. Whether to keep audio capture active while recognition is gated remains undecided.
+- In headphone mode, the microphone can remain available during playback. User speech detection or recognized words can trigger an interruption. Voice activity detection versus recognition-based confirmation remains an open latency/reliability tradeoff.
+- Users should explicitly choose their acoustic mode; output-device detection alone cannot prove that the microphone is free of assistant audio.
+- Pause preserves speech for possible continuation; cancel discards it. Resume should continue from the preserved position where technically supported.
+- A user interruption may be a temporary pause or a new request. The signaling policy remains unresolved, and silence alone should not force stale speech to resume.
+- Users should be able to speak while the DSH response is streaming. Generation, synthesis, playback, and recognition must be tracked independently.
+- Text segments may feed an ordered speech queue. Cancellation must invalidate queued and late-arriving audio from obsolete responses.
+- Pausing playback does not necessarily stop generation. Generation control and new-turn delivery depend on DSH APIs that still need inspection.
+
+These are goals and design proposals, not implemented features.
+
+### Portability and capability discovery
+
+The desired audience includes users on different operating systems and machines. OS detection is a feature, but capability detection should drive the options shown in the UI: devices, permissions, local engines, pause/resume support, and shortcut availability.
+
+The browser and DSH host may be on different machines. Their environments must not be conflated. Global hotkeys must be distinguished from shortcuts that only work while the page is focused. No cross-platform support matrix has been verified yet.
+
+### Proposed responsibility boundaries
+
+1. Environment and capability detection.
+2. Conversation coordinator and interruption policy.
+3. Voice input: capture, speech detection, and STT.
+4. Voice output: TTS, buffering, queueing, and playback.
+5. DSH integration: messages, streaming, and session lifecycle.
+6. Interface and controls: states, modes, devices, and hotkeys.
+
+A single global state such as “listening” or “speaking” is insufficient for overlapping input and output. These boundaries do not fix a source-code directory layout. Whether to reuse existing plugins or connect to engines directly remains open pending inspection of DSH extension points.
+
+### Documentation and licensing decision
+
+At the maintainer’s request, the repository is being expanded with an explanatory English README, this append-only history, and `AGENTS.md`. The initial temporary `UNLICENSED` metadata is replaced with the MIT open-source license to permit use, modification, sharing, and commercial redistribution under its terms. Third-party engines and models may carry separate licensing requirements.
+
+No runtime code is being added at this stage. Repository URL and author metadata remain unset rather than guessed. The next commit and push must wait for the maintainer’s instructions and repository details.
+
+## 2026-09-14 — GPL selection and first push authorization
+
+The maintainer rejected the initial MIT proposal, clarified that internal business use should remain possible, discussed keeping redistributed versions open, and explicitly approved GPL. The selected license is GNU GPL version 3 only (`GPL-3.0-only`). This supersedes the MIT statement in the initial entry: that entry described intended work prematurely; package metadata was still `UNLICENSED` and no MIT LICENSE file had been created.
+
+GPL permits commercial use and charging for copies. Its copyleft and corresponding-source obligations apply when conveying covered software, whether paid or free. Private internal modifications need not be published, and network service use alone does not trigger those obligations under GPL. The project does not impose a non-commercial restriction. The official GPL v3 text is included in LICENSE, and current documentation and metadata reflect this selection.
+
+The history file was found under `HISTORY.md`, with README already linking to that name. This is now the canonical path; earlier references to `história.md` are retained as historical text. Agent instructions have been aligned without rewriting this file’s existing entries.
+
+The maintainer supplied `git@github.com:victorwads/dsh-live-voice.git` and authorized the first commit and push to `main`. Repository metadata and local-first keywords have been added. This entry records authorization, not successful execution; npm publication remains unperformed and requires separate authorization.
+
+## 2026-09-14 — Gratitude to the original voice plugin authors
+
+The maintainer requested a personal acknowledgment of [GooDAnDReaDY/dsh-voice](https://github.com/GooDAnDReaDY/dsh-voice) and [Alan2Z/dsh-speak](https://github.com/Alan2Z/dsh-speak). Both projects solved the maintainer’s DSH voice needs for a long time. The maintainer forked them and changed behaviors for personal use before deciding that one codebase should coordinate input and output.
+
+The README now thanks both authors directly, describes the coordination limitations as the maintainer’s experience rather than a blanket judgment of their projects, and encourages users who need only one side of voice interaction to explore and support them. This acknowledgment does not imply endorsement or participation by either author in DSH Live Voice.
+
+The maintainer also emphasized a user-focused product direction: minimize mandatory configuration, provide sensible defaults, and make switching recognition and speech synthesis engines simple. These remain product goals, not implemented capabilities. No runtime code was added for this documentation update.

package/LICENSE

@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

package/README.md

@@ -0,0 +1,119 @@
+# DSH Live Voice
+
+**Local-first voice conversations for DSH.**
+
+Designed to run speech recognition (speech-to-text, STT) and speech synthesis (text-to-speech, TTS) on your own machine, with optional external providers. The goal is a single plugin that coordinates listening and speaking, rather than two independent voice tools competing for the microphone and speakers.
+
+## Project status
+
+**Early development — no working DSH plugin is available yet.**
+
+Version `0.0.1-developing` is a documentation-only development placeholder. Everything described below as planned behavior is a product goal, not an implemented feature. There are no runtime dependencies, build pipeline, or executable entry points yet.
+
+## Why this project exists
+
+Separate STT and TTS integrations can interfere with one another: the microphone may transcribe the assistant’s own speaker output, and the user may have no convenient way to interrupt a long spoken answer.
+
+DSH Live Voice aims to own the conversational state of both directions. The experience should approach a natural conversation: listen, speak, yield, pause, and resume when appropriate. It does not promise human-level timing or perfect echo suppression.
+
+## Acknowledgments
+
+A heartfelt thank you to [GooDAnDReaDY](https://github.com/GooDAnDReaDY), creator of [dsh-voice](https://github.com/GooDAnDReaDY/dsh-voice), and [Alan2Z](https://github.com/Alan2Z), creator of [dsh-speak](https://github.com/Alan2Z/dsh-speak).
+
+Your projects solved my voice needs in DSH for a long time, and I am genuinely grateful for the work you shared. I forked both repositories, built my own versions, and adapted behaviors that mattered to my workflow. Those projects were useful in their own right and helped me understand what I needed next.
+
+Eventually, I reached a point where I needed one codebase to coordinate both listening and speaking. In my setup, the independent plugins could overlap or interfere with each other because they did not share a conversation coordinator. That is why I am starting DSH Live Voice from scratch—not because their work lacked value, but because my next step requires a unified approach.
+
+My goal is a user-focused voice experience: less mandatory configuration, sensible defaults, and a simple way to switch speech recognition and speech synthesis engines without having to understand the internals. These are goals for this new project, not claims about features already available.
+
+If you only need one side of the experience—voice input or spoken output—please explore and support their projects. They may be exactly what you need. Thank you both for making DSH more useful to me and for sharing your work with the community.
+
+## Local-first, provider-optional
+
+- Prioritize local speech recognition and local speech synthesis.
+- Keep external speech providers optional, with explicit configuration.
+- Explain which capabilities, models, dependencies, and permissions are required by each available option.
+- Make capture, recognition, and external audio transmission states visible.
+- Do not equate local voice processing with a fully offline assistant: the DSH language model may still use a remote service.
+
+Specific engines, supported operating systems, hardware requirements, and installation steps have not been selected or verified yet. Local execution is the product priority, not a claim that the current package runs everywhere.
+
+## Planned conversation experience
+
+### Speaker mode
+
+While the assistant is speaking, microphone audio should not enter speech recognition, to reduce feedback from speaker output. A user-triggered shortcut should stop or pause playback and let the user speak. Whether capture stays active while recognition is gated remains a technical decision; the UI must distinguish those states.
+
+### Headphone mode
+
+The microphone may remain available during assistant playback. Detecting user speech should pause the assistant. Voice activity detection can respond faster, while recognized words provide stronger evidence with additional latency. The exact interruption policy is not decided yet.
+
+Users should be able to choose the conversation mode explicitly. A detected output device alone is not reliable evidence of acoustic isolation.
+
+### Pause, resume, and cancel
+
+These are separate operations:
+
+- **Pause:** suspend playback while preserving the remaining content and playback position where supported.
+- **Resume:** continue preserved speech when it is still relevant.
+- **Cancel:** discard obsolete speech so it cannot play later.
+
+A brief interruption may mean “wait, then continue” or may introduce a new request. Silence alone must not force an old answer to resume. How users signal these intentions remains an open design question. Exact resume may require plugin-owned audio buffering and is not guaranteed by every TTS engine.
+
+### Speaking during response streaming
+
+The user should be able to speak while DSH is still streaming a response. Text generation, speech synthesis, audio playback, and microphone recognition must be coordinated but tracked separately. Pausing playback need not stop text generation. Sending a new request or stopping generation depends on the actual DSH integration APIs.
+
+A future speech queue should synthesize suitable text segments in order and prevent delayed audio from canceled answers from playing.
+
+## Environment and capabilities
+
+The planned interface should explain available options based on capabilities, not only an operating-system label. Relevant checks include microphone permission, audio devices, local engine availability, playback controls, and shortcut scope.
+
+The DSH host and the browser may run on different machines. Detection must distinguish the host environment from the machine with the microphone and speakers. Global shortcuts and browser-focused shortcuts must not be presented as equivalent.
+
+## Proposed architecture
+
+These are responsibility boundaries, not implemented modules or a fixed directory layout:
+
+| Area | Responsibility |
+| --- | --- |
+| Environment and capabilities | Detect available features and explain limitations. |
+| Conversation coordinator | Manage turns, interruptions, pause, resume, and cancellation. |
+| Voice input | Capture audio, detect speech, and integrate STT engines. |
+| Voice output | Integrate TTS engines and manage buffering, queues, and playback. |
+| DSH integration | Connect messages, response streaming, and session lifecycle. |
+| Interface and controls | Expose modes, devices, permissions, state, and shortcuts. |
+
+Input, output, and generation need separate states because listening and speaking may overlap. One plugin may support multiple engines. Reusing existing DSH plugins versus integrating engines directly requires inspection of the actual extension APIs first.
+
+## Repository guide
+
+- [`package.json`](package.json): npm package metadata.
+- [`HISTORY.md`](HISTORY.md): English-language, append-only product history and decision record.
+- [`AGENTS.md`](AGENTS.md): instructions for AI agents working on this project.
+- [`LICENSE`](LICENSE): GNU GPL version 3 license.
+
+## Development and contributions
+
+Design discussion and contributions are welcome. Read the history and agent instructions before changing project direction. Keep proposals distinct from implemented capabilities, and document new decisions without rewriting previous history entries.
+
+There is no runnable development setup or automated test suite yet. To inspect the intended npm publication without publishing:
+
+```sh
+npm publish --dry-run --tag developing
+```
+
+A dry run does not reserve the npm name or verify publishing authorization. Actual publication requires an available name and an authorized npm account. Use an explicit `developing` tag for prereleases; do not publish, commit, or push without the maintainer’s authorization.
+
+## Keywords
+
+`dsh`, `local-first`, `local-voice`, `voice-conversation`, `speech-to-text`, `text-to-speech`, `speech-recognition`, `speech-synthesis`, `stt`, `tts`, `turn-taking`, `voice-interruption`
+
+## License
+
+DSH Live Voice is licensed under the [GNU General Public License, version 3 only](LICENSE) (`GPL-3.0-only`).
+
+Internal and commercial use are allowed, and copies may be sold. When distributing covered software, with or without modifications and whether free or paid, you must comply with the GPL, preserve recipients’ GPL rights, and provide the corresponding source as required by the license. Private modifications do not have to be published merely because they are used internally. Providing a network service without conveying copies does not, by itself, trigger GPL source-distribution obligations.
+
+This is a summary; the license text governs. Third-party engines and model weights may have their own licenses.

package/package.json

@@ -0,0 +1,38 @@
+{
+  "name": "dsh-live-voice",
+  "version": "0.0.1-developing",
+  "description": "Local-first voice conversations for DSH, with local speech recognition and synthesis and optional external providers. Under development.",
+  "keywords": [
+    "dsh",
+    "local-first",
+    "local-voice",
+    "voice-conversation",
+    "speech-to-text",
+    "text-to-speech",
+    "speech-recognition",
+    "speech-synthesis",
+    "stt",
+    "tts",
+    "turn-taking",
+    "voice-interruption"
+  ],
+  "author": {
+    "name": "wads.dev",
+    "url": "https://www.npmjs.com/org/wads.dev"
+  },
+  "license": "GPL-3.0-only",
+  "files": [
+    "README.md",
+    "LICENSE",
+    "HISTORY.md",
+    "AGENTS.md"
+  ],
+  "publishConfig": {
+    "access": "public",
+    "tag": "developing"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/victorwads/dsh-live-voice.git"
+  }
+}